Back to docsRecipe

Prometheus primer

Wire Meridian telemetry into Prometheus for real‑time metrics, alerting rules, and Grafana dashboards — no agent overhead.

Why Prometheus

Prometheus scrapes HTTP endpoints on a pull model. Meridian exposes a /metrics route with counters, histograms, and gauges for every protected session. No push gateway, no sidecar — just a scrape config.

Scrape config

scrape_configs:
  - job_name: 'meridian'
    scheme: https
    metrics_path: '/metrics'
    bearer_token_file: /etc/prometheus/meridian.token
    static_configs:
      - targets: ['api.getnimbus.net']

Generate a long‑lived token in Dashboard → Settings → API keys.

Key metrics

meridian_sessions_active — gauge, current live sessions
meridian_license_validations_total — counter, lifetime checks
meridian_hwid_mismatches_total — counter, fingerprint drift
meridian_request_duration_seconds — histogram, p50/p95/p99

Alerting rules

groups:
  - name: meridian
    rules:
      - alert: HighHWIDMismatch
        expr: rate(meridian_hwid_mismatches_total[5m]) > 0.05
        for: 10m
        labels:
          severity: warning
        annotations:
          summary: "Elevated HWID drift detected"

Grafana quick‑start

Import dashboard ID 21480 from grafana.com/dashboards. The panel queries target themeridian_ prefix. Set the Prometheus data source and you'll have session counts, validation rates, and latency heatmaps in under two minutes.

← All recipes