- 
                Notifications
    
You must be signed in to change notification settings  - Fork 808
 
Add Gauge for total_fields setting on a index #411
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
Add Gauge for total_fields setting on a index #411
Conversation
9e9be05    to
    16be4a2      
    Compare
  
    Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
16be4a2    to
    55aaa2e      
    Compare
  
    | 
           @SuperQ I've rebased this to remove my previous build fixes  | 
    
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.
A couple of minor nits. Plus I think there are some metrics missing from the README update.
Signed-off-by: Mike Roest <[email protected]>
fe2f024    to
    6b1d613      
    Compare
  
    Signed-off-by: Mike Roest <[email protected]>
| 
           @SuperQ I've update the metric names for the 2 new metrics in this PR (and update the README with the new metric). Running the promtool There's a significant number of metrics that are failing the validations. So like you said a separate PR that can be merged with the breaking changes to metric names probably makes the most sense (probably makes sense to make an issue i suppose?)  | 
    
| 
           Yes, a separate PR for fixing the naming issues would make the most sense.  | 
    
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.
One more naming issue.
Signed-off-by: Mike Roest <[email protected]>
| 
           👍  | 
    
| 
           when this change will be released?  | 
    
Signed-off-by: Mike Roest <[email protected]>
Signed-off-by: Mike Roest <[email protected]>
056f929    to
    6d9663a      
    Compare
  
    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.
LGTM, Thanks for all the work.
Signed-off-by: Joe Adams <[email protected]>
* prometheus-community#257: Add gauge for total fields mapped in an index Signed-off-by: Mike Roest <[email protected]> Co-authored-by: Marco Sohns <[email protected]> Co-authored-by: Jeff Nadler <[email protected]> Signed-off-by: Toomas Ormisson <[email protected]>
This was introduced in prometheus-community#411, and is in the 1.2.0 release. Signed-off-by: Mandar Gokhale <[email protected]> Signed-off-by: Toomas Ormisson <[email protected]>
* prometheus-community#257: Add gauge for total fields mapped in an index Signed-off-by: Mike Roest <[email protected]> Co-authored-by: Marco Sohns <[email protected]> Co-authored-by: Jeff Nadler <[email protected]>
This was introduced in prometheus-community#411, and is in the 1.2.0 release. Signed-off-by: Mandar Gokhale <[email protected]>
Includes #386 changes as well