Prometheus

Fluxtail converts accepted Prometheus samples into log events. It does not scrape targets or provide native metric-series storage.

Prerequisites

Create the matching Prometheus text or prometheus_remote_write receiver, create a token bound to it with ingest:write, and copy the exact receiver URL.

Prometheus text

Use the exact Prometheus text receiver URL:

export FLUXTAIL_RECEIVER_URL='https://ingest.fluxtail.io/v1/receivers/RECEIVER_ID/prometheus/metrics'
export FLUXTAIL_TOKEN='ftl_RECEIVER_BOUND_TOKEN'

curl --fail-with-body -X POST "$FLUXTAIL_RECEIVER_URL" \
  -H "Authorization: Bearer $FLUXTAIL_TOKEN" \
  -H 'Content-Type: text/plain; version=0.0.4' \
  --data-binary $'http_requests_total{service="checkout"} 12\n'

Success is HTTP 202.

Prometheus remote_write

Create a prometheus_remote_write receiver and use its exact URL:

https://ingest.fluxtail.io/v1/receivers/RECEIVER_ID/prometheus/api/v1/write

Fluxtail accepts remote_write v1 with Snappy block-compressed protobuf. Snappy framed payloads and remote_write 2.0 are not accepted. Put the token in a credentials file instead of the Prometheus YAML:

remote_write:
  - url: "${FLUXTAIL_REMOTE_WRITE_URL}"
    authorization:
      credentials_file: /etc/prometheus/fluxtail-token

Success is HTTP 204.

Verify

Open Live Tail for the configured stream and filter by the metric name. Each sample appears as a log event.

Troubleshooting

• Do not append /metrics or /api/v1/write to an exact URL copied from Fluxtail.
• Confirm the token is bound to the matching receiver.
• Text requests need a Prometheus text or OpenMetrics content type.
• remote_write must use v1 block compression.

Next steps

Use search and filters to check labels on converted samples. For sender compatibility details, see Prometheus’s official remote write 1.0 specification.