Time series

Scrape ProbeHarbor into Influx

Scrape Pro Prometheus metrics into InfluxDB, VictoriaMetrics, or any Telegraf output — same /api/v1/metrics contract as Grafana.

Download Telegraf config Start free / Pro HTTP APIAll integrations

How it works

Pro API keys expose Prometheus text at GET /api/v1/metrics. Telegraf’s inputs.prometheus scrapes that endpoint and writes to InfluxDB 2.x, VictoriaMetrics, or any Telegraf output. No new ProbeHarbor API — same contract as Grafana.

Quick start

  1. Create a Pro API key under Dashboard → Share.
  2. Download telegraf/probeharbor.conf and set PROBEHARBOR_API_KEY, INFLUX_TOKEN, INFLUX_ORG, INFLUX_BUCKET.
  3. telegraf --config probeharbor.conf — confirm probeharbor_sensor_value points land in the bucket.
curl -sH "Authorization: Bearer $PROBEHARBOR_API_KEY" \
  https://probeharbor.dev/api/v1/metrics | head

Metric shape

Single gauge probeharbor_sensor_value with labels device, key, kind (temperature, humidity, flood, …). Numeric readings only — booleans stay on share JSON / HACS / Matter.

Self-hosted: replace the host in the Telegraf URL. VictoriaMetrics users can swap the output for Prometheus remote write (commented example in the config).

Grafana still works

Prefer dashboards over long-term TSDB? Import probeharbor-dashboard.json against a Prometheus data source pointing at the same metrics URL.

Influx FAQ

Telegraf scrape, Pro keys, and VictoriaMetrics.

Do I need a new ProbeHarbor API for Influx?

No. Telegraf scrapes the existing Pro Prometheus endpoint GET /api/v1/metrics. Sample config: probeharbor.dev/telegraf/probeharbor.conf. Guide: probeharbor.dev/integrations/influx.

Does this replace Grafana?

No. Use Grafana for dashboards against Prometheus; use Influx/VictoriaMetrics when you want a long-term TSDB or existing Influx stack. Same metric name: probeharbor_sensor_value.

What about boolean leak/door sensors?

Prometheus metrics are numeric only. For booleans use share JSON, HACS, or the Matter bridge.