-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fix/prometheus metadata sorting #12112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Sinscerly
wants to merge
2
commits into
apache:main
Choose a base branch
from
cyso:fix/prometheus-metadata-sorting
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+103
−26
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Sinscerly - I have a question around the metrics using tags in which you have modified the help text - if not mistaken the text won't be updated as the modification will happen after invoking
item.toMetricsString()so at this line the previous help text will be displayed, is this correct?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @nvazquez,
The HELP and TYPE only have to be added before each group of metrics. Only once for
cloudstack_domain_resource_count, regardless of how many items with different tags share that metric name.Does this clarify your question?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Sinscerly sorry for the delay. My concern was only for the metrics that override the
helpfield on theitem.toMetricsString()call.For example:
On the metrics iteration, when creating the metrics string for
ItemHostCputhe string will always start with the default HELP text (Host CPU usage in MHz) despite having tags or not - I see in case the metric contains tags it should displayHost CPU usage in MHz grouped by host tags. Please correct me if I'm wrongAdditionally, I think this if block
if (!item.name.equals(currentMetricName))can be removedUh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @nvazquez,
Well the item
ItemHostCpureturns two different metrics:cloudstack_host_cpu_usage_mhz_totalandcloudstack_host_cpu_usage_mhz_total_by_tag. I just made sure the correct help line is outputted for that metric.In the end all metrics are sorted and each unique help line is added. so this will give:
So it seemed logical for me to also change that. Although I'm doubting it will work, as the
toMetricsStringis called after adding in the HELP and TYPE I see. Although this would require some bigger rework of adding metrics I think, split it up in separate items.Removing the
if (!item.name.equals(currentMetricName))will cause harm as you only want it once for every unique metric name. As you want:And not the HELP and TYPE for every single metric item:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Sinscerly please ignore my second comment then :)
About the first one, do you think that can be addressed on a separate PR, leaving this PR as it is now?