Skip to content

Prometheus Monitoring

DRP exposes Prometheus style metrics by a built-in HTTP endpoint, enabling integration with standard monitoring infrastructure.

Metrics Endpoint Architecture

DRP exports metrics on port 8080 by default. For example the metrics endpoint is available at:

Text Only
http://<drp-server-ip>:8080/metrics

This endpoint serves metrics in the standard Prometheus exposition format, making it compatible with Prometheus scrapers and other monitoring tools that support this format.

Security Considerations

The metrics endpoint binds to all interfaces (0.0.0.0) by default, which means:

  • Metrics may be accessible to other hosts on the network
  • Network-level controls like firewalls or security groups should be used to restrict access

Prometheus Scrape Configuration

To configure Prometheus to scrape DRP metrics, add a job to your prometheus.yml:

YAML
scrape_configs:
  - job_name: 'drp'
    static_configs:
      - targets: ['<drp-server-ip>:8080']
    metrics_path: /metrics

Configuring the Metrics Port

The metrics port can be configured via the DRP startup options. Use the --metrics-port flag or set the RS_METRICS_PORT environment variable to change from the default port 8080.

Available Metrics

DRP exposes a growing number of metrics for operations including:

  • consensus_* - HA cluster state (leadership, elections, node count)
  • drp_api_* - API requests
  • drp_dhcpv4_* - DHCP requests/replies
  • drp_static_* - Static file server requests
  • drp_tftp_* - TFTP boot file transfers