Configuration

TelemetryLane can be configured via a YAML configuration file, environment variables, or programmatically. The configuration file is the recommended approach for production deployments.

Configuration File

By default, TelemetryLane looks for telemetrylane.yaml in the current working directory. You can specify a custom path:

a, err := agent.Init(agent.Config{
    ConfigPath: "/etc/telemetrylane/config.yaml",
})

Full Configuration Example

# TelemetryLane Configuration
# See https://telemetrylane.com/docs/configuration.html

service:
  name: "api-gateway"
  environment: "production"
  version: "1.4.2"

pipeline:
  buffer_size: 4096
  flush_interval: "5s"
  batch_size: 512

collectors:
  traces:
    enabled: true
    sample_rate: 0.1
  logs:
    enabled: true
    min_level: "info"
  metrics:
    enabled: true
    aggregation_interval: "10s"

exporters:
  otlp:
    endpoint: "https://otel-collector.internal:4317"
    protocol: "grpc"
    compression: "gzip"
    headers:
      authorization: "Bearer ${OTLP_TOKEN}"

  # Alternative: Jaeger exporter
  # jaeger:
  #   endpoint: "http://jaeger:14268/api/traces"
  #   protocol: "thrift-http"

  # Alternative: Zipkin exporter
  # zipkin:
  #   endpoint: "http://zipkin:9411/api/v2/spans"

routing:
  - name: "all-to-otlp"
    match: "*"
    target: "otlp"

logging:
  level: "info"
  format: "json"

Exporter Configuration

OTLP

Jaeger

Zipkin

Environment Variables

All configuration options can be overridden with environment variables. The format is TELEMETRYLANE_ followed by the uppercased key path with underscores.