> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://mezmo.ferndocs.com/prometheus-remote-write-source/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://mezmo.ferndocs.com/_mcp/server.

# Prometheus Remote Write

## Description

You can send your metrics to a Mezmo Pipeline to be received as Prometheus Remote Write data.

## Configuration

The Mezmo Prometheus Remote Write source provides a unique endpoint URL that uses **Bearer Token** authentication. You can obtain the unique endpoint and Bearer Token from the Mezmo pipeline app when you create a new Prometheus Remote Write source.

### Configuration Options

| Option        | Description                                             |
| ------------- | ------------------------------------------------------- |
| url           | unique URL for your remote\_write source                |
| bearer\_token | token used in sending data to your remote\_write source |

### Prometheus Configuration File

To configure a Prometheus instance add a section like this to its configuration file:

```yaml
     - url: https://pipeline.mezmo.com/v1/<YOUR ROUTE ID>
       bearer_token: <YOUR_PIPELINE_INGEST_KEY>
```

### Kubernetes Operator

If you are running Prometheus within Kubernetes using the Kubernetes operator you can configure the instance with these commands, templating in the Bearer Token, the endpoint provided by the Mezmo Web App, and the Prometheus crd name:

```bash
kubectl -n monitoring create secret generic mz-prom-rw-token --from-literal=value=<TOKEN FROM APP>
```

```bash
cat <<'EOF' | kubectl patch prometheus -n <PROMETHEUS NAMESPACE> <YOUR PROMETHEUS CRD INSTANCE> -f -
spec:
  remoteWrite:
  - authorization:
      credentials:
        key: value
        name: mz-prom-rw-token
    url: <ENDPOINT FROM APP>
EOF
```