Hosted Prometheus Endpoint
This page describes how to use WarpStream's hosted prometheus endpoint for collecting control plane metrics.
Overview
Almost all WarpStream metrics are exposed directly in the Agents. However, exposing some control plane metrics in the WarpStream Agents can be problematic, mostly due to cardinality.
For example, consumer group lag metrics are most useful when they're tagged by partition, but emitting consumer group metrics tagged by partition in the Agents would make the time series cardinality very high: O(m * n) where m is the number of partitions and n is the number of the Agents.
As a result, WarpStream offers a hosted Prometheus endpoint that exposes a subset of WarpStream's control plane metrics. This endpoint is authenticated and can be scraped by your monitoring system to collect some control plane metrics without incurring the additional cardinality of the Agent host / pod names.
Available Metrics
The hosted Prometheus endpoint only exposes a small subset of the metrics available in WarpStream. The vast majority of WarpStream's metrics are best obtained by scraping the Agent's Prometheus endpoint directly. However, a small subset of WarpStream's metrics are so high cardinality that scraping them from our hosted Prometheus endpoint may be more effective.
The metrics currently exposed by the hosted Prometheus endpoint are:
warpstream_consumer_group_state
warpstream_consumer_group_generation_id
warpstream_consumer_group_num_members
warpstream_consumer_group_num_topics
warpstream_consumer_group_num_partitions
warpstream_consumer_group_max_offset
warpstream_consumer_group_lag
warpstream_consumer_group_estimated_lag_very_coarse_do_not_use_to_measure_e2e_seconds
Sample Prometheus Scraping Configuration
An API Key can be obtained from the "API Keys" tab in the WarpStream console. For more details, see our API Keys reference documentation.
Last updated
Was this helpful?