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
Adding docs for prometheus. #507
Conversation
docs/troubleshooting.md
Outdated
| 1. asb_sandbox - Keeps track of the active sandboxes | ||
| 2. asb_specs_loaded - will keep track of the number of specs currently loaded, will be reset on bootstrap. Labels can be used to determine the registry that has X number loaded. | ||
| 3. asb_spec_reset - will keep track of how many times the specs have been reset. | ||
| 4. asb_provision_jobs - will keep track of how many jobs are currently in the provision buffer? |
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.
Why the question mark?
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 w/ one optional change.
| @@ -188,3 +188,27 @@ Redeploy the broker using origin clients `rollout latest` command. | |||
| $ oc rollout latest asb | |||
| deploymentconfig "asb" rolled out | |||
| ``` | |||
|
|
|||
| ### Metrics | |||
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.
👍 Excellent place for this!
docs/troubleshooting.md
Outdated
|
|
||
| ### Metrics | ||
|
|
||
| The broker will expose [Prometheus](https://prometheus.io/) style metrics that you can use to troubleshoot the broker if none of the steps above work. You can access the published metrics by calling: |
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.
Optional:
The broker exposes Prometheus style metrics for monitoring and troubleshooting purposes. You can access these metrics via the /metrics endpoint by calling:
Reason: It's infinitely useful by itself (as demonstrated already) and isn't conditional on the rest of the troubleshooting steps.
docs/troubleshooting.md
Outdated
| 3. asb_spec_reset - will keep track of how many times the specs have been reset. | ||
| 4. asb_provision_jobs - will keep track of how many jobs are currently in the provision buffer | ||
| 5. asb_deprovision_jobs - will keep track of how many jobs are currently in the deprovision buffer | ||
| 6. asb_update_jobs - will keep track of how many jobs are currently in the update buffer? |
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.
buffer? Drop off the question mark and add periods to all these.
docs/troubleshooting.md
Outdated
| 4. asb_provision_jobs - will keep track of how many jobs are currently in the provision buffer | ||
| 5. asb_deprovision_jobs - will keep track of how many jobs are currently in the deprovision buffer | ||
| 6. asb_update_jobs - will keep track of how many jobs are currently in the update buffer? | ||
| 5. asb_actions_requested - keeps track of the number of actions requested correctly (broken down by action = bind,unbind,update,provision,deprovision) |
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.
requested correctly I think I know what you mean by this, but can you say this another way?
I view this metric as: The total number of successful bind, unbind, update, provision, and deprovision requests. Each are labeled and can be filtered in a dashboard.
Describe what this PR does and why we need it:
Adding documentation for using the metrics endpoint
NOTE: does the troubleshooting doc make sense?
Changes proposed in this pull request