Skip to content

Centralized Observability: OTLP Log Exporting #28

Description

@taitelee

Problem

Stdout logs are lost if a container restarts or if the host disk rotates logs. To properly analyze system behavior, logs should be treated as a first-class telemetry signal, just like traces.

Proposed Solution

  • Add support for an OTLP log exporter (using a library like slogotel).
  • Configure the application to fan-out logs: stdout for local development and OTLP for the SigNoz Collector in production.
  • For local development, use slog-multi to provide a "pretty-print" (non-JSON) format for humans while maintaining JSON for machines.

Alternatives Considered

None

Additional Context

None

Activity

  1. closed this as completedby moving to Done in WaveHouse Task Boardon Apr 14, 2026
  2. changed the title [-][feature] Centralized Observability: OTLP Log Exporting[/-] [+][feature] [Observability] Centralized Observability: OTLP Log Exporting[/+] on Apr 14, 2026
  3. self-assigned this
    on Apr 20, 2026
  4. added theissue type on Apr 20, 2026
  5. changed the title [-][feature] [Observability] Centralized Observability: OTLP Log Exporting[/-] [+]Centralized Observability: OTLP Log Exporting[/+] on Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/observabilityMetrics, logs, traces, health, profilingenhancementNew feature or request

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions