Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

jaeger

jaeger: A distributed tracing system for collecting, storing, and querying application traces.

What problem it solves

Distributed applications need a way to collect, store, and inspect traces across their components. The project addresses this with an all-in-one distribution, an OTLP ingestion path, and separate collector, query, UI, and storage components.

Key features

  • All-in-one deployment — The Docker distribution combines the UI, collector, query service, and in-memory storage so traces can be explored from a single local deployment.

    Source: README

  • OTLP trace ingestion — The collector accepts traces through OTLP over gRPC or HTTP, allowing applications to send trace data using standard OpenTelemetry interfaces.

    Source: README

  • Separated query and storage services — The architecture separates collection, storage, querying, and presentation into distinct components, with the query service reading stored traces for the UI.

    Source: README, components

  • Pluggable storage support — The collector can write to storage directly or through a storage plugin, and the project documents support policies for several storage backends.

    Source: README, docker-compose

Quick start

Copied verbatim from the project's README.

# Run Jaeger all-in-one (includes UI, collector, query, and in-memory storage)
docker run --rm --name jaeger \
  -p 16686:16686 \
  -p 4317:4317 \
  -p 4318:4318 \
  jaegertracing/jaeger:latest

# Access the UI at http://localhost:16686
# Send traces via OTLP: gRPC on port 4317, HTTP on port 4318

Who it may suit

Inference: may suit developers who want to run local distributed tracing and teams operating trace collection, storage, and query infrastructure.

Topics to discuss

  • How should teams choose a storage backend for different deployment environments?

  • What operational guidance would help users migrate existing tracing configurations?

  • Which community examples would be most useful for new contributors?


Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/jaegertracing/jaeger#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/jaegertracing/jaeger

Comments

…