Skip to main content
Analytics & ObservabilityOfficial Appaloft catalog

Jaeger

Distributed tracing backend and UI with OpenSearch storage.

Appaloft · Official Appaloft catalogReviewed 2026-05-24cloud-jaeger · v1.0.0

Deployment highlights

  • Runs the cr container image.jaegertracing.io/jaegertracing/jaeger:2.18.0.
  • OpenSearch stores trace data.
  • Jaeger UI is exposed as the primary Appaloft route on port 16686.
  • OTLP HTTP ingestion is available for instrumented services.

Good for

  • Distributed trace exploration
  • OpenTelemetry span collection
  • Latency and request path debugging

Deployment variants

Deployment variants

The public Blueprint describes application topology. Appaloft's install plan confirms resource creation, reuse, and upgrade checks.

This Blueprint uses a single deployment shape.

Environment profiles

PreviewProduction · Default

Upgrade impact

Upgrade strategy: image-tag
Manual review required · No destructive changes declared

Blueprint manifest

Topology Appaloft will create

This topology comes from the public Blueprint manifest. Dependencies are created or bound to existing resources through the install plan.

Components · 1

Jaeger

service
Runtime
container-image · cr.jaegertracing.io/jaegertracing/jaeger:2.18.0
Public ports
web:16686/http Public · otlp-http:4318/http Private
Routes
web/
Health check
HTTP /
Bound resources
opensearch

Dependencies · 1

Jaeger trace storage

opensearch
Dependency
opensearch
Required
Required

Installation configuration

Installation configuration

Parameters are ordinary install-time settings. Secrets are shown only by key and source; this page never collects or displays their values.

Parameters · 1

App name

APP_NAME

Type: string · Required · Default: Jaeger

Secrets · 0

None