Esta página se tradujo automáticamente. Leer el original en inglés.

Component

core/observability/loki

A Grafana Loki log-aggregation server. Loki receives log streams from shippers and agents over its HTTP push API, indexes them by label rather than by full-text content, stores them in a chunk object store, and answers log-query and range requests over the same HTTP API. This component models Loki in its single-binary shape: every Loki subsystem — distributor, ingester, querier, compactor — runs inside one process backed by a local filesystem chunk store, so it renders as a single stateful server with a data volume rather than a set of microservices. A memcached may be wired to the optional `chunk_cache` socket to hold decompressed chunks between queries; the per-connection values on that edge — batch size, parallelism, timeout and entry lifetime — tune how this server drives that one cache, and with nothing wired the server runs without a chunk cache. The socket takes one connection, and a second halts the build, as does a target publishing a protocol other than memcached or memcached-tls, or none. Its contract to consumers is that HTTP endpoint: a log shipper pushes streams to it, and a dashboards server reads them back over the query API. It also receives OpenTelemetry logs at the base address it publishes as `otlp_http_endpoint`, and carries `observability.aggrega.ai/logs: otlp-http`, so an OpenTelemetry Collector's `logs` socket takes it. Realized on helm by `loki`, which sources the official Grafana Loki chart, and on compose by `loki`, a compose service running the same image and publishing nothing to the host. Loki serves its own metrics in the Prometheus format at /metrics on its HTTP port, on by default, and every Recipe publishes that address as `metrics_endpoint`.

Procedencia

OficialFirmado por una identidad de firma que este catálogo reconoce como editor oficial.
Digest del contenido
sha256:f18ddfb195f109038457d006de50752a385ac09898522d173af030fa6f8d5cbd
Publicado
2026-11-10T10:13:09Z
Identidad de firma
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Firma

  • Oficialapplication/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:e3c0b97a1f971a3f4c1a90a0c14c522f1587e2d3d131e4555d3873539925974f

Referencia en esta versión

oci://hub.aggrega.ai/component/core/observability/loki:1.0.0

Parámetros del desarrollador

Valores que el desarrollador establece en el Aggregate.

NombreTipoPredeterminadoObligatorioDescripción
retention_periodstring168hnoHow long stored log streams are kept before the in-process compactor deletes them. Expressed as a Go duration (e.g. `168h` for seven days).

Dimensionamiento del operador

Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.

NombreTipoPredeterminadoObligatorioDescripción
source_versionstring—noSource artifact version (Helm chart). Overrides the helm Recipe's default source version; the compose realization pulls no source artifact and ignores it. Changing from default does not guarantee value mapping compatibility.
computeobject—no—
storageobject—no—
overridesobject (open)—noProvider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads.

Contrato de salida

Valores que este componente publica para los consumidores a través de la topología uses.

NombreTipoPredeterminadoObligatorioDescripción
hoststring—síName the push and query API is reached at — the in-cluster Service on helm, the service name on compose. A shipper sending log streams and a dashboard querying them both dial this name.
portinteger—síTCP port the push and query API is served on. Each realization serves the project's own default, so a consumer reads this rather than hard-coding one.
protocolstring—noHow the published address is spoken to — `http`, so a consumer reaches both the push and the query paths with an HTTP client.
otlp_http_endpointstring—noThe base address OpenTelemetry logs are received at — `http://<host>:<port>/otlp`. An OTLP HTTP exporter given it appends `/v1/logs` itself.
metrics_endpointstring—noThe full address Prometheus scrapes this component's metrics at — scheme, host, port and path, `http://<host>:<port>/metrics` on the push and query API. Empty where the component serves none reachable.

Sockets uses

Los sockets de dependencia a través de los cuales se conecta este componente. El destino de cada conexión cableada a través de un socket debe satisfacer su selector de etiquetas, y cada conexión puede llevar un acoplamiento en los slots que declara el socket. Cada conexión que el Aggregate o la Release cablea a través del socket debe llenar los slots obligatorios.

chunk_cache

Selector
component.aggrega.ai/category=datastore
Inyección
env

Slots que cada conexión a través de este socket puede llenar

SlotSelectorObligatorioInyecciónSensibleDescripción
server_cafeature.aggrega.ai/kind=secretnofilesíOptional authority the server checks the cache's certificate against while the cache publishes protocol memcached-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Kubernetes realization mounts the whole Secret read-only into the server and names the file in its chunk-cache client; the Compose realization refuses it, since no credential Feature realized there delivers a Secret as files. The build halts on a server_ca publishing no Secret name, and on one wired to a cache served without TLS. Fill it with core/referenced-secret.

Slots de acoplamiento

Puntos de enlace con nombre en los que una Feature se acopla a este componente. El selector de un slot restringe qué Feature puede llenarlo y su lista inject indica cómo puede entregarse el material de la Feature. Un slot obligatorio debe estar enlazado en cada instancia, mediante un acoplamiento en la instancia o en un ámbito superior, y un slot sensible se declara para manejar material secreto. Una Feature también puede acoplarse con un nombre que ningún slot declara.

No se declararon slots de acoplamiento.

Lista de permitidos de autoinyección

env

Relaciones

Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.

Usa

Usado por

Referencia del concepto Component →

El catálogo de Aggrega — un índice abierto de componentes, funcionalidades, recetas y los plugins que los renderizan.

Creado con el sistema de diseño compartido de Aggrega.

Privacidad