Omlet Docs
  • Intake and Authorization via OTLP
  • Datadog to OTel (Omlet SaaS)
  • Bare-Metal
  • Kubernetes
  • Languages
  • "Serverless"
  • Integrations
  • Use OTel for Volume Control
  • Datadog Agent(s) to OTel
  • Splunk Universal Forwarder to OTel
  • Log / Trace AI Agent (Skillet)
Powered by GitBook
On this page
  • Via Collector YAML
  • Environment Variables

Intake and Authorization via OTLP

The first step in sending data is understanding how to send via OTLP. Getting data into Omlet is as easy as setting an intake endpoint with an authorization header

Via Collector YAML

exporters:
  otlphttp/omlet:
    endpoint: "{INTAKE}"
    headers:
      Authorization: "Bearer {AUTH_TOKEN}"
service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlphttp/omlet]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlphttp/omlet]
    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlphttp/omlet]

The above example highlights creating an otlphttp exporter with an intake and authorization header.

Environment Variables

export OTEL_EXPORTER_OTLP_ENDPOINT="{INTAKE}"
export OTEL_EXPORTER_OTLP_HEADERS="Authorization=Bearer {AUTH_TOKEN}"
export OTEL_SERVICE_NAME="service_name"

The above example uses environment variables to set an intake and authorization header. This convention is very relevant for tracing (APM).

NextDatadog to OTel (Omlet SaaS)

Last updated 4 months ago

Page cover image