coverage: emit zero for missing metrics from coverage show output#33
Merged
rjarry merged 1 commit intoopenstack-k8s-operators:mainfrom Jan 29, 2026
Merged
Conversation
426d8e0 to
81d3440
Compare
rjarry
requested changes
Jan 28, 2026
81d3440 to
61a14c7
Compare
The ovs-appctl coverage/show command only reports counters that have non-zero values. This causes the exporter to not emit metrics that have not incremented yet, making it difficult to set up alerts for error conditions before they occur. Iterate over all defined metrics and emit 0 for any not present in the OVS output. In test comparison logic handle the exporter now reporting more fields than what OVS returns. Signed-off-by: Abhiram R N <abhiramrn@gmail.com>
61a14c7 to
bcb415f
Compare
rjarry
approved these changes
Jan 29, 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
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.
The ovs-appctl coverage/show command only reports counters that have non-zero values. This causes the exporter to not emit metrics that have not incremented yet, making it difficult to set up alerts for error conditions before they occur.
Iterate over all defined metrics and emit 0 for any not present in the OVS output.
In test comparison logic handle the exporter now reporting more fields than what OVS returns.