Component
core/observability/jaeger
A Jaeger distributed-tracing backend in its single-node shape. Jaeger receives trace spans over the OpenTelemetry protocol, keeps them in a local embedded key-value trace store, and serves trace-lookup and search queries over its query UI. Every Jaeger subsystem — the OTLP receiver, the storage writer, and the query service — runs inside one process backed by a local on-disk store, so it renders as a single stateful server with a data volume rather than a set of microservices. Its primary contract to consumers is the OTLP gRPC receiver: a trace producer wires to it and pushes spans there. The OTLP HTTP receiver and the query UI are exposed on their own ports. Realized on Kubernetes via its Helm Recipe, which synthesizes the workload directly from the official Jaeger image; helm-only. Exports its OTLP gRPC receiver host and port to consumers via the uses topology, and carries `observability.aggrega.ai/traces: otlp-grpc`, so an OpenTelemetry Collector's `traces` socket takes it and exports spans to that receiver. The packaged Jaeger server is Apache-2.0. With `values.metrics_enabled` true the Recipe has Jaeger serve its own metrics, at /metrics on port 8888, on every interface rather than its loopback address, and publishes that address as `metrics_endpoint`; false, that key is empty. The port checks no caller.
来源
- 内容摘要
- sha256:83bfdc2d401b83dd421af951624c76844590da235f919faafc8f4666eb38baf9
- 发布时间
- 2026-11-10T10:13:00Z
- 签名身份
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
签名
- 官方application/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:1cd36c5987ac05c0dc5f27a04a22a0bed6a098afe8367dc1d17540c9865af046
此版本的引用
oci://hub.aggrega.ai/component/core/observability/jaeger:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| metrics_enabled | boolean | false | 否 | Makes Jaeger's own metrics, served at /metrics on port 8888, reachable on every interface rather than its loopback address alone, and publishes their address as `metrics_endpoint`; while false that key is empty. The port checks no caller, so anything that reaches it can read them. |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| engine_version | string | 2.19.0 | 否 | Jaeger server image tag. Pins the packaged Jaeger version the workload references. |
| otlp_grpc_port | integer | 4317 | 否 | Port for the OTLP gRPC trace receiver — the primary ingestion endpoint trace producers push spans to. |
| otlp_http_port | integer | 4318 | 否 | Port for the OTLP HTTP trace receiver. |
| query_port | integer | 16686 | 否 | Port for the Jaeger query UI and its trace-lookup API. |
| compute | object | — | 否 | — |
| storage | object | — | 否 | — |
| overrides | object (open) | — | 否 | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| host | string | — | 是 | In-cluster DNS name of the Service receiving trace spans. An application exporting spans points its exporter at this name together with `port`. |
| port | integer | — | 是 | TCP port spans are ingested on. It carries the OpenTelemetry gRPC receiver port, not the query UI port, so a consumer wires its exporter rather than its browser. |
| protocol | string | — | 否 | How the published address is spoken to — `grpc`, so an exporter is configured for the gRPC transport rather than the HTTP one. |
| metrics_endpoint | string | — | 否 | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:8888/metrics`, the host being the tracing backend's Service name. Empty while values.metrics_enabled is false. |
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
未声明 uses 套接字。
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
未声明附加槽位。
自注入允许列表
未声明自注入管道。
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
此实体未使用目录中的任何内容。
被使用
使用套接字 «backend»
使用套接字 «databases»
使用套接字 «etcd»
使用套接字 «backend»
使用套接字 «backend»
使用套接字 «forward_target»
使用套接字 «traces»
使用套接字 «scrape_target»
使用套接字 «backend»
使用套接字 «database»
适用于
适用于
适用于
实现