Skip to content

OTLP traces and metrics ingest #3

Description

@inerc

v2 ingests OTLP logs today (gRPC :4317). This issue tracks accepting
traces and metrics on the same endpoint.

Scope

  • Traces: spans as first-class input for the topology extractor —
    parent/child spans become edges directly (today traces only refine the
    log-derived map via trace_id correlation); span events land as log
    entries.
  • Metrics: minimal viable mapping to be defined — likely per-service
    rate/error/duration series feeding the map and service cards, not a
    general-purpose TSDB.
  • Same auth model as the rest of ingest.

Non-goals

Dashboards, PromQL, a metrics explorer UI — LogDoc is not an APM.
Traces and metrics serve the map and the logs, not the other way around.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestroadmapPlanned work, prioritized by demand

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions