Component
core/observability/thanos-store
Thanos Store Gateway, the read side of a Thanos metrics stack. The Store Gateway reads historical metric blocks from an S3-compatible object store and serves them to queriers over its StoreAPI on a gRPC port. The object store it reads from is wired through its `objstore` uses-socket: the endpoint the store publishes gives the S3 endpoint in the object-store configuration, and its scheme whether that connection is plain HTTP or TLS. Credentials reach the process as environment variables through the AWS SDK credential chain rather than being embedded in that configuration, so the rendered configuration carries no secret: the access key's secret half is the connection's `credential`, and its identifier the connection's `credential_id` where one is attached, else the `s3_access_key` value. The Store Gateway keeps only an ephemeral local cache of index data — the object store is the system of record — so it renders as a stateless server. Exports its StoreAPI host, port, and protocol to consumers via the uses topology. The gateway serves its own metrics in the Prometheus format at /metrics on its HTTP port, not the published StoreAPI port, and publishes that address as `metrics_endpoint`.
Provenance
- Content digest
- sha256:d72db93af276a5cf3f877eea9d563e888ed7e96587318aa71688d73fe939f37d
- Published
- 2026-11-10T10:13:20Z
- 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:c98c2833eb7473faf6e304aa4b848670713311d41b2f33a638f1510c942d5215
Reference at this version
oci://hub.aggrega.ai/component/core/observability/thanos-store:1.0.0Developer parameters
Values the developer sets in the Aggregate.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| s3_access_key | string | admin | no | S3 access-key identifier presented to the object store where the `objstore` connection carries no `credential_id`; a `credential_id` attached there is presented in its place. Its secret is the `credential` the `objstore` connection carries. |
| bucket | string | thanos | no | Object-store bucket the Store Gateway reads metric blocks from. The bucket must be pre-created out of band; the read tier does not provision it. Where the store wired to `objstore` publishes a bucket of its own, this names the same one, or the build halts. |
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| http_port | integer (min 1024, max 65535) | 10902 | no | HTTP port serving health and metrics endpoints, reachable in-cluster only. |
| grpc_port | integer (min 1024, max 65535) | 10901 | no | gRPC port serving the StoreAPI; queriers connect here. |
| engine_version | string | v0.42.0 | no | Thanos container image tag. |
| compute | object | — | no | — |
| overrides | object (open) | — | no | Provider-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.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| host | string | — | yes | In-cluster DNS name of the Service the gateway serves historical metric blocks on. A query front end adds this name to its store list together with `port`. |
| port | integer | — | yes | TCP port the store API is served on. It carries the gRPC port an operator set, never the health-and-metrics HTTP port. |
| protocol | string | — | no | How the published address is spoken to — `grpc`, so a query front end dials it as a store rather than as an HTTP endpoint. |
| metrics_endpoint | string | — | no | The full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<http_port>/metrics` on the HTTP port, which is not the published `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.
objstore
- Selector
- component.aggrega.ai/type=resource,component.aggrega.ai/category=storage
- Inject
- env
Slots each connection through this socket may fill
| Slot | Selector | Required | Inject | Sensitive | Description |
|---|---|---|---|---|---|
| credential_id | feature.aggrega.ai/kind=secret | no | env | yes | Access-key identifier the Store Gateway presents to the object store this connection reaches, the identifier half of the pair whose secret half is this connection's credential, supplied as the object-store access key ID via the credential subsystem. It names an account on that store, so it matches whatever the store itself was given. Unattached, the s3_access_key value is presented instead. |
| credential | feature.aggrega.ai/kind=secret | no | env | yes | S3 secret key the Store Gateway presents to the object store this connection reaches, supplied as the object-store secret access key via the credential subsystem. There is no default: the build halts when nothing fills this slot, unless the connection's values set unauthenticated: true. |
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
- usesuses socket «objstore»
component.aggrega.ai/type=resource,component.aggrega.ai/category=storage
Attachment slots: credential_id, credential
Used by
uses socket «upstream»
uses socket «forward_target»
uses socket «scrape_target»
uses socket «store»
applies to
applies to
applies to
applies to
applies to
applies to
applies to
implements