-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Prometheus exporter enhancement #4438
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
Merged
DaanHoogland
merged 17 commits into
apache:main
from
soreana:prometheus-exporter-enhancement
Sep 30, 2022
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
1984b8a
Export count of total/up/down hosts by tags
d75b66f
Export count of vms by state and host tag.
1b24280
Add host tags to host cpu/cores/memory usage in Prometheus exporter
ab04936
Cloudstack Prometheus exporter: Add allocated capacity group by host …
230d3d7
Show count of Active domains on grafana.
1687b28
Show count of Active accounts and vms by size on grafana
6a6e18b
Fixed HostTagsDao import issue and removed unnecessary fields.
7a897d3
Change variable names with regards to DaanHoogland comments.
d41b99c
Moved to commons.lang3 as a default string lib.
cbd780d
Fixed spaces.
fed9b6a
Updated pr to address @GutoVeronezi change requests.
633ebac
Fixed camel case issue.
bfd8926
Removed redundant lines of the Prometheus outputs.
76fbc2a
Use prepared statement to query database for a number of VM who use a…
0bcc6bc
Rename gethostTags to getHostTags.
51571e4
Remove unwanted files.
6aab64b
Extract repeated codes to new methods.
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
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
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
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
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
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
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
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.
@soreana all your changes LGTM, I've one question - do you see this change in LIST_ALLOCATED_CAPACITY_GROUP_BY_CAPACITY_AND_ZONE causing any potential regression in the users of
findCapacityBy()method, and should we do any kind of testing for this cc @nvazquez.However, I do see use of
WHERE_STATE_IS_NOT_DESTRUCTIVEwhich you append to the sql string, but whether it has impact on the overall sql query?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.
ping @soreana cc @ravening we're waiting for your confirmation and then we can merge your PR. Any update/comment ?
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.
@rohityadavcloud Sorry I was away and missed this comment. What do you mean by regression?
I guess that you mean the findCapacityBy() returns different values for different cases in a new version, but it returns the same in an old version. Am I correctly understanding your comment?
Uh 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 @soreana yes, my concern is there are code changes in
findCapacityBy()method and my concern is if that could cause regression to consumers of this method (outside of your use-case)? Could you check if my concerns are valid, if not I'm happy to conclude the review the merge the PR.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 @soreana could you confirm if my concerns are valid, or we can go ahead and merge the PR?
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.
cc @DaanHoogland
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.
@soreana I don´t see any ansswer yet. Can you explain the method, how it is changed and how this impacts other uses please?
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.
@DaanHoogland @rohityadavcloud Sorry for late respond, I've lost track of this issue. No it doesn't change affect the
findCapacityBy()return value. Thewhereclause appended to the SQL query later in the code.https://github.com/apache/cloudstack/pull/4438/files#diff-dfeaef8c3e4c5eb658e6d479055c7ffdc407a9e959de834b76e881e7b140faf5R474