-
Notifications
You must be signed in to change notification settings - Fork 136
fix: Update metrics catalog #1673
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview will be available once build job completes!
|
| | **Metric** | **Display Name** | **Dimensions** | **Type** | **Description** | **Roll-up per** | | ||
| |----------------------------------------|------------------|-----------------------------|-------|-----------------------------------------------------------------------------------------------------------------------------|---------------| | ||
| | system.cpu| CPU utilization | | count | System CPU Utilization. | deployment | | ||
| | system.cpu| CPU utilization | | average | System CPU Utilization. | deployment | |
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.
Maybe where we talk about manual scaling, we should mention they should think about alerting on this metric.
russokj
left a 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.
Looks good. Just a minor suggestion.
|
LGTM! Let's wait for LIFTR to deploy the new metric specification before we update the docs. |
ADubhlaoich
left a 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.
LGTM!
Proposed changes
Change Type to average for system.cpu Metric for nginx azure in metrics-catalog.
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩