Skip to main content

​
Mezmo Exporter

Status Available in: contrib Maintainers: @dashpole, @billmeyer, @gjanco Source: opentelemetry-collector-contrib

​
Supported Telemetry

Logs

​
Overview

This exporter supports sending OpenTelemetry log data to Mezmo. Note: Mezmo logs ingestion requires a hostname field to be present. When logs are sent via this exporter, and hostname metadata is not added, the Mezmo ingestion API will set hostname=otel. To provide the hostname information, we recommend adding a Resource Detection Processor to the collector configuration. Doing so will cause this exporter to automatically add the hostname metadata to the outgoing log data whenever it is available. See the below example configuration for a basic configuration that adds hostname detection support.
  • ingest_url (optional): Specifies the URL to send ingested logs to. If not specified, will default to https://logs.mezmo.com/otel/ingest/rest.
  • ingest_key (required): Ingestion key used to send log data to Mezmo. See Ingestion Keys for more details.

​
Example:

​
Simple Log Data

receivers:
  otlp:
    protocols:
      grpc:
        endpoint: ":4317"

processors:
  resourcedetection:
    detectors:
      - system
    system:
      hostname_sources:
        - os

exporters:
  mezmo:
    ingest_url: "https://logs.mezmo.com/otel/ingest/rest"
    ingest_key: "00000000000000000000000000000000"

service:
  pipelines:
    logs:
      receivers: [ otlp ]
      processors: [ resourcedetection ]
      exporters: [ mezmo ]

​
Configuration

​
Example Configuration

mezmo:
  ingest_key: "00000000000000000000000000000000"
mezmo/allsettings:
  ingest_url: "https://alternate.mezmo.com/otel/ingest/rest"
  ingest_key: "1234509876"
  retry_on_failure:
    enabled: false
    initial_interval: 99s
    max_interval: 199s
    max_elapsed_time: 299m
  sending_queue:
    enabled: false
    num_consumers: 7
    queue_size: 17
Last generated: 2026-04-13