fix(go.d/proxysql): correct backend status metric mapping #21524
+21
−22
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
This fixes how the ProxySQL go.d collector derives per-backend
status_*metrics fromstats_mysql_connection_pool.ProxySQL returns status as a string (e.g.
ONLINE,SHUNNED,OFFLINE_SOFT,OFFLINE_HARD), but the collector was comparing it to numeric codes ("1".."4"), causing all status metrics to be reported as 0.Update the collector to set
backend_*_status_<STATE>based onvalue == <STATE>for the known states.Test Plan
Additional Information
For users: How does this change affect me?
Summary by cubic
Fixes ProxySQL backend status mapping in the go.d collector. Status metrics now match the string states returned by ProxySQL, fixing the 0-only values.
Written for commit f9f5aa6. Summary will update on new commits.