Prometheus Integration
Prometheus Endpoints for Long-Term Reporting and Alerting
kPow's Prometheus egress endpoints follow the OpenMetrics standard.
This allows you to integrate kPow to your favourite observability tools such as Prometheus, New Relic or Grafana for long-term reporting dashboards and alerting.

Configuration

Prometheus Endpoints are not secure, do not configure if kPow is publicly accessible.
To enable Prometheus endpoints set the following environment variable.
1
PROMETHEUS_EGRESS=true
Copied!

Getting Started

Endpoints

kPow provides Prometheus endpoints for all metrics, offsets, and streams.
kPow logs the path to each Prometheus endpoint on startup
1
* GET /metrics/v1 - all metrics
2
* GET /offsets/v1 - all topic offsets
3
* GET /offsets/v1/topic/[topic-name] - all topic offsets for specific topic, all clusters
4
* GET /metrics/v1/cluster/v-EEfIOXRqCDS6JpK0X0Pw - metrics for cluster Trade Book (Staging)
5
* GET /offsets/v1/cluster/v-EEfIOXRqCDS6JpK0X0Pw - offsets for cluster Trade Book (Staging)
6
* GET /metrics/v1/cluster/lkc-lo0o9 - metrics for cluster Outbound Payments (Staging)
7
* GET /offsets/v1/cluster/lkc-lo0o9 - offsets for cluster Outbound Payments (Staging)
8
* GET /metrics/v1/schema/a2f06a916672d71d675f - metrics for schema registry
Copied!

Sample Scraper Configuration

Sample Prometheus scraper configuration that we use to test kPow:
1
scrape_configs:
2
- job_name: 'operatr'
3
metrics_path: '/metrics/v1'
4
static_configs:
5
- targets: ['host.docker.internal:3000']
6
- job_name: 'operatr_streams'
7
metrics_path: '/streams/v1'
8
static_configs:
9
- targets: ['host.docker.internal:3000']
10
- job_name: 'operatr_offsets'
11
metrics_path: '/offsets/v1'
12
static_configs:
13
- targets: ['host.docker.internal:3000']
Copied!