Skip to main content
Gateway exposes metrics in the Prometheus format that you can scrape and send to your external log management system. The metrics endpoint is <gateway_host>:<gateway_port>/metrics of your deployed Gateway instance. For example: localhost:8888/metrics.
If GATEWAY_SECURED_METRICS is enabled (which is the default), you’ll have to use the credentials specified in GATEWAY_ADMIN_API_USERS to access the metrics.

​
Prometheus metric suffixes

When metrics are exported to Prometheus, suffixes are automatically appended based on the metric type:
  • Counter: _total suffix (e.g., gateway_bytes_exchanged_total)
  • Timer (summary): _seconds_count, _seconds_sum and _seconds_max suffixes (e.g., gateway_apiKeys_latency_request_response_seconds_count)
  • Timer (histogram): same as summary, plus _seconds_bucket with a le label for histogram buckets (e.g., gateway_latency_request_response_seconds_bucket). Only gateway_latency_request_response is exported as a histogram.
  • Gauge: no suffix (e.g., gateway_active_connections_vcluster)
The table below lists the Prometheus metric names as they appear when scraped. Dots (.) in the underlying metric name are converted to underscores (_).
The gateway_topic_log_end_offset and gateway_topic_current_offset metrics are currently only populated for topics using topic concentration. For non-concentrated topics, use standard Kafka consumer lag monitoring.