fix(inputs.mysql): Parse boolean values in metric v1 correctly #15063
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
The current code for metric version 1 parses everything as an integer for global status queries. This leads to zero values for boolean values such as "ON" or "true" which are in turn perceived as "wrong" on the database side.
This PR fixes parsing of boolean values and emits a (single-time) warning for other values which might contain strings, floats etc resulting in zero values. The PR does not change the behavior for those other values to prevent changes of field-types for the metric output.
Checklist
Related issues
resolves #6417