Skip to main content
Supported data types: Logs • Metrics • Traces
Recommended approach for comprehensive coverage and lowest operational overhead.
If your stack supports OTel, use this for Collector-level ingestion.
Still configure API access for your observability vendor for Phoebe to access additional context.
OpenTelemetry works with any system that already uses an OTel Collector/Agent. Add Phoebe as an additional exporter so you keep your existing destinations and send a copy to Phoebe. Add a Phoebe OTLP/HTTP exporter and reference it in your pipelines. Using environment variables for the key is strongly encouraged.
# --- opentelemetry-collector.yaml ---

exporters:
  # Your existing exporters (keep as-is)
  otlp/primary:
    endpoint: your-existing-endpoint

  # Phoebe exporter (OTLP over HTTP)
  otlphttp/phoebe:
    endpoint: https://ingest.phoebe.ai/otel
    headers:
      X-API-Key: ${PHOEBE_INGEST_KEY}
    compression: gzip
    timeout: 10s
    sending_queue:
      enabled: true
      num_consumers: 4
      queue_size: 1024
    retry_on_failure:
      enabled: true
      initial_interval: 5s
      max_interval: 30s
      max_elapsed_time: 5m

service:
  pipelines:
    logs:
      receivers: [your-existing-receivers]
      exporters: [otlp/primary, otlphttp/phoebe]
    metrics:
      receivers: [your-existing-receivers]
      exporters: [otlp/primary, otlphttp/phoebe]
    traces:
      receivers: [your-existing-receivers]
      exporters: [otlp/primary, otlphttp/phoebe]
Set ${PHOEBE_INGEST_KEY} securely via environment variables or your secrets manager. Avoid hard-coding secrets into config files.
Important: Add the Phoebe exporter in addition to your current exporters for each pipeline so data keeps flowing to existing systems.

Verify

  1. Restart/reload your Collector
  2. Check Collector logs for export activity or errors:
# Example for a containerized Collector
docker logs <collector-container> | grep -i "otlphttp/phoebe"
  1. Generate test telemetry (e.g., a sample trace or log event) and review for errors in the Collector logs. Contact support to confirm the records are visible.