Send metrics to any Prometheus remote write endpoint

No integration for your vendor?

Our metrics integrations have always been vendor-shaped: Datadog, Dynatrace, New Relic, CloudWatch, Grafana Cloud. Handy if you use one of them. No help at all otherwise, whether you run your own Mimir cluster or pay a metrics vendor we have not built for. Until now, the answer was to scrape the Prometheus endpoint yourself or to file a request and wait.

The Prometheus Remote Write integration removes the waiting. You provide the endpoint and the credentials it expects, and the OpenTelemetry Collector on each broker node pushes metrics to it.

Any endpoint, four ways to authenticate

The endpoint is the full https URL of your receiver, path included, because that path differs between receivers:

https://mimir.example.com/api/v1/push
https://thanos.example.com/api/v1/receive
https://vm.example.com/api/v1/write

Authentication comes in four shapes, which between them cover the field:

• Basic auth for a username and a password or token
• Headers for bearer tokens and API keys, one key: value pair per line
• OAuth2 for client credentials, where we fetch an access token and refresh it before it expires
• None for receivers that carry their token in the endpoint query string

Some receivers require an additional header alongside the credentials, such as a tenant header. That is why headers are accepted in every authentication mode, not only when you pick header authentication.

Does your receiver expect another authentication method? Write to support@cloudamqp.com and let us know what it needs.

Prometheus format, all the way through

CloudAMQP already exposes broker and server metrics in Prometheus format, and remote write carries them without translation. Nothing gets remapped into a vendor-specific metric model on the way. The metric names and labels in our documentation are exactly what you query at the other end, so dashboards you already wrote keep working.

Every series carries an instance label with the node name and a cluster label with the cluster name. Add your own labels as custom tags when you configure the integration, for example env=production . The metrics filter takes a list of metric names. Send only the series your dashboards and alerts use, instead of paying to store all of them.

Setting it up

1. Copy the remote write URL from your receiver, including the path.
2. Pick an authentication mode and fill in what it needs: a username and password, or headers.
3. Add any extra headers your receiver expects.
4. Paste it all into the Integrations tab for your instance in the CloudAMQP console, then save. You can also enable the integration with the Instance API or Terraform.

Summary

Prometheus Remote Write turns every remote write receiver into a CloudAMQP metrics destination. You get server and broker metrics in native Prometheus format, labeled per node and per cluster. Authenticate with basic auth, headers, OAuth2, or a token in the URL. Headers ride along in all four modes, which is what makes tenancy work. Setup takes an endpoint and whatever credentials your receiver expects.

The Prometheus Remote Write documentation lists the default metrics and their labels, or browse all CloudAMQP integrations.