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

# OpenTelemetry Metrics

## Description

You can send your metrics to a Mezmo Pipeline via any OTLP compliant sender.

> Mezmo currently requires that you use the HTTP transport for your payload, not the standard gRPC transport mechanism, to send in data via OTLP

## Configuration

The OTLP Metrics 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 OTLP Metrics source. When you [add the source to your Pipeline](https://docs.mezmo.com/2.8/telemetry-pipelines/set-up-pipeline-sources), click on it and select Edit config. In the configuration settings, you will see the URL for the endpoint, and an option to generate a token.

### Configuration Options

| Option           | Description                                       |
| ---------------- | ------------------------------------------------- |
| `url / endpoint` | unique URL for your OTLP source                   |
| `token`          | token used for authorization for your OTLP source |

### OpenTelemetry Collector Configuration

To configure an OTel collector to export to Mezmo, you can add the following to your exporters section of your OTel Collector config file:

```yaml
exporters:
  otlphttp/mezmo-metrics:
    endpoint: "https://pipeline.mezmo.com/v1/<YOUR ROUTE ID>"
    headers:
      Authorization: "<YOUR_PIPELINE_INGEST_KEY>"
```

> The endpoint in the `exporters` configuration must exactly  match the URL provided by the OpenTelemetry Metrics. You don't need to specify the  `/v1/metrics` path, which will otherwise by ignored by the Source.