rsionThis This section describes the Prometheus forwarding agent. The Prometheus agent is available for both real-time and batch workflow configurations. This agent lets you publish metrics in a format that can be scraped by a Prometheus instance. The metrics can then be visualized using Grafana. Follow the official Grafana documentation here: https://grafana.com/docs/grafana/latest/. To configure Prometheus, see https://prometheus.io/docs/introduction/overview/.
...
The Prometheus forwarding agent stores metrics in a cache. The cached metrics are published in an endpoint which that is scraped by Prometheus.
...
The cache is shared by all workflows running in the Execution Context so its size has to be set accordingly, that is, to the expected metric flow throughput. Each Prometheus scrape empties the cache so the cache size should be set to minimum
<number_of_metrics_expected_per_second> * <prometheus_scrape_interval>.
...
All metrics created with the use of a
Measurement
UDR are exposed as aGAUGE
type. See 9.78.5 System Insight UDR Types for more informationEach value stored inside the
fields
field of theMeasurement
UDR are is reported as a separate metric.The
CATEGORY
field is not used. If it is still needed it has to be assigned toNAME
fields of thePrometheus
UDR. See Prometheus UDR Type for more information.If the
System Insight
UDR fieldfields
contains many measurements, each is reported as a separate metric.
Scroll ignore | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
The section contains the following subsections: |
...