Difference between revisions of "Draft: UCS/Current/UCSPEGuide/Metrics"
From Genesys Documentation
(Copied manual) |
m |
||
| Line 10: | Line 10: | ||
Describe metrics (compatible with Prometheus endpoints) that customers can use to create their own monitoring dashboard in a tool like Grafana. | Describe metrics (compatible with Prometheus endpoints) that customers can use to create their own monitoring dashboard in a tool like Grafana. | ||
| − | Make to identify any metrics that are important to monitor for alarming purposes, and include sample thresholds the customer should alarm on.</div> | + | Make to identify any metrics that are important to monitor for alarming purposes, and include sample thresholds the customer should alarm on.</div>UCS-X provides internal monitoring metrics through a Prometheus endpoint on port 10052. |
| + | <br /> | ||
|Status=No | |Status=No | ||
}} | }} | ||
|PEPageType=21ecf3f4-ef12-4276-8872-1e0e3af9561e | |PEPageType=21ecf3f4-ef12-4276-8872-1e0e3af9561e | ||
}} | }} | ||
Revision as of 06:16, June 17, 2021
This is a draft page; the published version of this page can be found at UCS/Current/UCSPEGuide/Metrics.
Learn which metrics you should monitor for <service_name> and when to sound the alarm.
Include a link to the "suite-level" documentation for monitoring:
UCS-X provides internal monitoring metrics through a Prometheus endpoint on port 10052.
#mintydocs_link must be called from a MintyDocs-enabled page (Draft:UCS/Current/UCSPEGuide/Metrics).
Describe metrics (compatible with Prometheus endpoints) that customers can use to create their own monitoring dashboard in a tool like Grafana.
Make to identify any metrics that are important to monitor for alarming purposes, and include sample thresholds the customer should alarm on.