Skip to main content

Description

You can export your telemetry data directly to Mezmo with the OpenTelemetry Exporter. If you are already using OpenTelemetry Collector, you can start sending log data by adding the Mezmo Exporter to your existing Pipelines. If you are new to OTEL, you can use this quick start example to get you up and running.

Example OpenTelemetry Exporter Setup

  1. Download the appropriate OTEL collector for your environment from the OpenTelemetry website.
  2. Create a new pipeline in Mezmo.
  3. Add an OpenTelemetry Source node.
  4. Create a configuration file config.yaml with these contents:
  1. Set your Mezmo ingestion key in the environment (referenced as ${env:MEZMO_INGESTION_KEY} in the config above):
  1. Start the Collector with this command: ./otelcol-contrib --config /path/to/config.yaml
  2. The Collector will start sending logs, metrics and traces to your Pipeline.
For complete information on setting up and configuring the OpenTelemetry Collector, visit https://opentelemetry.io/docs/collector/configuration

Large trace batches

The Collector’s OTLP gRPC receiver refuses any request over 4 MiB unless you set max_recv_msg_size_mib. LLM and agent spans often carry prompt and response text, so a full 512-span batch can pass that limit. The SDK retries a refused batch, then drops it, and the only sign is an export error in your app’s own log. Either raise the limit on the receiver, as both configs on this page do:
Or send smaller batches from the SDK with OTEL_BSP_MAX_EXPORT_BATCH_SIZE=256.

How OTel logs land in Log Analysis

OTel log records sent to https://logs.mezmo.com/otel become Log Analysis lines. Search for them with these fields. Resource attributes go under _meta. In search, each dot in the name becomes an underscore: A search for the OTel name, or a guess such as namespace:, finds nothing. Use the _meta field. Host, app and file come from these attributes, first one set wins: Record fields: level is the record’s severity text. trace_id and span_id come from the record. Record attributes land at the top level under their own names. A name that clashes with a system field, such as level or _host, moves under _label. Any other name that starts with _ gets a second _. Example searches:

Installing the Collector via a Helm Chart

You can install the OpenTelemetry collector directly in a Kubernetes cluster using a Helm chart. If you don’t have the OpenTelemetry repo added to your Helm list, you must add it first.
Update your repos once you’ve added the OpenTelemetry repo.
Next, create a namespace to run this:
Now create a secret to store your ingestion key:
Now create a values.yaml file. This example file will give you an OTLP source within your cluster and export your telemetry to mezmo:
Then you can install the chart to deploy the Collector: