...
You can configure a maximum number of metrics stored until Prometheus scrapes them. When you scrape a metric it is automatically deleted. You can also set an expiration time for a metric.
| Note |
|---|
NoteCurrently, the cache is under development. There is a known issue about dropping metrics even when the cache is not full. See more in the Endpoint section. |
Endpoint
Each Execution Context exposes an endpoint that can be scraped by a Prometheus instance at:
...
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>.
| Note |
|---|
NoteMetrics stored in the cache are read-only-once. Manual querying of the endpoint will result in data missing in Prometheus. |
...