Component

core/observability/thanos-query

Thanos Query, the query front end of a Thanos metrics stack. Query answers PromQL requests and fans them out over the StoreAPI to one or more Store Gateways, deduplicating and merging the results. The Store Gateway it queries is wired through its `store` uses-socket: the gateway's host and port arrive on the injection context and compose the StoreAPI endpoint Query dials. Query speaks the StoreAPI over gRPC, so a component wired there that publishes a protocol other than grpc, or none, halts the build; Thanos Store publishes grpc. Query serves its PromQL API and web UI on an HTTP port and exposes its own StoreAPI on a gRPC port so queriers can be layered. Query holds no persistent state of its own — it reads through the Store Gateway — so it renders as a stateless server. Exports its HTTP host, port, and protocol to consumers via the uses topology. Query serves its own metrics in the Prometheus format at /metrics on its HTTP port and publishes that address as `metrics_endpoint`.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:c16e73c6c2243df0ff97fead322b9beec35a2740cde16ad03616b93fc58b7403
Published
2026-11-10T10:13:16Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/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:2065882df01222cda0f4130fb96d5110ff120e7aaf716d639b4ce2370b1cc201

Reference at this version

oci://hub.aggrega.ai/component/core/observability/thanos-query:1.0.0

Developer parameters

Values the developer sets in the Aggregate.

No developer parameters declared.

Operator sizing

Infrastructure sizing the operator tunes per environment.

NameTypeDefaultRequiredDescription
http_portinteger (min 1024, max 65535)10902noHTTP port serving the PromQL API and web UI; consumers connect here.
grpc_portinteger (min 1024, max 65535)10901nogRPC port exposing Query's own StoreAPI, reachable in-cluster only.
external_base_urlstring—noExternally reachable base URL of the query front end, as assembled at the ingress tier, including any path the ingress serves it under — for example https://thanos.example.com or https://tools.example.com/thanos. The web interface composes from this the link it writes beside every rule expression and every alert it lists, back to its own query page. Where the address carries a path, the links, asset paths and redirects of the web interface's own pages carry that path too. On its own the server would then also move its API and web interface under the path; the Recipe keeps it serving at its root instead, so its health checks and every consumer reaching it through its published host and port are unaffected, and an ingress in front of it maps the address's path onto that root. Omitted, those links point at localhost on the HTTP port, which no browser outside the server's own pod can follow.
engine_versionstringv0.42.0noThanos container image tag.
computeobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Output contract

Values this component publishes to consumers over the uses topology.

NameTypeDefaultRequiredDescription
hoststring—yesIn-cluster DNS name of the Service fronting the query front end. A dashboard points its data-source address at this name rather than at any single metrics server.
portinteger—yesTCP port the query API and web UI are served on. It carries the HTTP port an operator set, never the internal gRPC port.
protocolstring—noHow the published address is spoken to — `http`, so a consumer composes a data-source URL on that scheme.
metrics_endpointstring—noThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<port>/metrics` on the HTTP port. Empty where the component serves none reachable.

Uses sockets

The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.

store

Selector
component.aggrega.ai/type=server
Inject
env

This socket declares no attachment slots, so a connection through it carries no attachment.

Attachment slots

Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.

No attachment slots declared.

Self-inject allowlist

env

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

Used by

Component concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy