Skip to content

Comments

feat: add OTLP endpoint configuration and trace query support#53

Open
chtushar wants to merge 2 commits intomainfrom
chtushar/otlp-config
Open

feat: add OTLP endpoint configuration and trace query support#53
chtushar wants to merge 2 commits intomainfrom
chtushar/otlp-config

Conversation

@chtushar
Copy link
Contributor

Summary

  • Added OtlpConfig type to allow configuring external OTLP endpoints (Tempo, Jaeger, SigNoz, etc.)
  • Implemented createOtlpQueryClient service that queries traces from Tempo-compatible HTTP APIs
  • Modified traces handler to read from OTLP endpoint when configured, falling back to PostgreSQL otherwise
  • No breaking changes — existing PostgreSQL flow unchanged when OTLP not configured

Changes

  • packages/core/src/schemas/config.ts: New otlpConfigSchema with endpoint, headers, protocol validation
  • packages/core/src/types/index.ts: Export OtlpConfig type
  • packages/app/src/server/services/otlpQueryClient.ts: New Tempo query client (listTraces, getTraceWithSpans, getTraceStats)
  • packages/app/src/server/handlers/traces/index.ts: Query routing based on llmopsConfig.otlp

When an OTLP endpoint is configured, trace data is queried from external collectors
(Tempo, Jaeger, etc.) instead of PostgreSQL. Adds OtlpConfig type with endpoint,
headers, and protocol (http/protobuf or http/json) options. Implements Tempo-compatible
query client for listTraces, getTraceWithSpans, and getTraceStats operations.
No changes to existing PostgreSQL flow when OTLP is not configured.
@chtushar chtushar marked this pull request as ready for review February 22, 2026 11:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant