Log IngestionCopy Anchor Link

Owlpane ingests structured and unstructured logs via OTLP/HTTP (/v1/logs), the Owlpane language SDKs, and host/Kubernetes log collectors.

EndpointCopy Anchor Link

Authenticate with Authorization: Bearer owl_ing_…. See the OTLP ingest reference.

Recommended AttributesCopy Anchor Link

• service.name — Logical service identifier (e.g. payments-api).
• deployment.environment — Environment tag (production, staging, dev).
• severity_text / severity_number — Log level (INFO, WARN, ERROR).
• trace_id and span_id — Correlates log lines directly with distributed traces.

curl example (OTLP/HTTP JSON)Copy Anchor Link

curl -sS -X POST "https://ingest.owlpane.com/v1/logs" \
  -H "Authorization: Bearer $OWLPANE_INGEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resourceLogs":[{"resource":{"attributes":[{"key":"service.name","value":{"stringValue":"payments-api"}}]},"scopeLogs":[{"scope":{"name":"manual"},"logRecords":[{"severityNumber":9,"severityText":"INFO","body":{"stringValue":"payment captured"}}]}]}]}'

OpenTelemetry Collector exporterCopy Anchor Link

exporters:
  otlphttp/owlpane:
    endpoint: ${env:OTEL_EXPORTER_OTLP_ENDPOINT}
    headers:
      Authorization: "Bearer ${env:OWLPANE_INGEST_KEY}"

Verify it arrivedCopy Anchor Link

Open Observability → Logs (/observability/logs) and filter by service.name. New lines appear within a few seconds.

TroubleshootingCopy Anchor Link