[DBAAS-8750] | Whitelist mysql_up in dbaas metrics for Advanced MySQL data-plane alerting - #358
Merged
agarg291 merged 1 commit intoJul 3, 2026
Conversation
agarg291
approved these changes
Jul 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
mysql_uptodbaasWhitelistso the mysqld_exporter up gauge is forwarded when do-agent scrapes--dbaas-metrics-path.Why
mysql_upis the MySQL equivalent of the already-whitelistedpg_up(1= MySQL reachable,0= not). The exporter emits it, but do-agent currently drops it before metrics reach Insights/metis.Needed for Advanced MySQL data-plane paging alerts (same pattern as Advanced PG
pg_up).Test plan
go test ./cmd/do-agent/... ./pkg/collector/...