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`.
来源
- 内容摘要
- sha256:f18ddfb195f109038457d006de50752a385ac09898522d173af030fa6f8d5cbd
- 发布时间
- 2026-11-10T10:13:09Z
- 签名身份
- 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:e3c0b97a1f971a3f4c1a90a0c14c522f1587e2d3d131e4555d3873539925974f
此版本的引用
oci://hub.aggrega.ai/component/core/observability/loki:1.0.0开发者参数
开发者在 Aggregate 中设置的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| retention_period | string | 168h | 否 | How long stored log streams are kept before the in-process compactor deletes them. Expressed as a Go duration (e.g. `168h` for seven days). |
运维规格
运维人员按环境调整的基础设施规格。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| source_version | string | — | 否 | Source 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. |
| compute | object | — | 否 | — |
| storage | object | — | 否 | — |
| overrides | object (open) | — | 否 | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
输出契约
此组件通过 uses 拓扑向使用方发布的值。
| 名称 | 类型 | 默认值 | 必需 | 描述 |
|---|---|---|---|---|
| host | string | — | 是 | 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. |
| port | integer | — | 是 | 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. |
| protocol | string | — | 否 | How the published address is spoken to — `http`, so a consumer reaches both the push and the query paths with an HTTP client. |
| otlp_http_endpoint | string | — | 否 | The base address OpenTelemetry logs are received at — `http://<host>:<port>/otlp`. An OTLP HTTP exporter given it appends `/v1/logs` itself. |
| metrics_endpoint | string | — | 否 | The 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. |
uses 套接字
此组件用于建立连接的依赖套接字。通过某个套接字接入的每个连接,其目标都必须满足该套接字的标签选择器,且每个连接都可以在该套接字声明的槽位中携带附加项。必需槽位须由 Aggregate 或 Release 通过该套接字接入的每个连接来填充。
chunk_cache
- 选择器
- component.aggrega.ai/category=datastore
- 注入
- env
经由此套接字的每个连接可填充的槽位
| 槽位 | 选择器 | 必需 | 注入 | 敏感 | 描述 |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | 否 | file | 是 | 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. |
附加槽位
Feature 附加到此组件时所用的命名绑定点。槽位的选择器限定哪个 Feature 可以填充该槽位,其 inject 列表则指明 Feature 的内容可以如何交付。必需槽位必须在每个实例上完成绑定,可以通过实例上的附加,也可以通过其上层作用域的附加;敏感槽位则声明为用于处理机密内容。Feature 也可以以任何槽位都未声明的名称进行附加。
未声明附加槽位。
自注入允许列表
env
关系
与其他已发布实体之间的类型化边。没有已发布目标的引用会呈现为断开的边,而不是链接。
使用
- 使用使用套接字 «chunk_cache»
component.aggrega.ai/category=datastore
附加槽位:server_ca
core/datastore/chroma v1.0.0 →core/datastore/cognee v1.0.0 →core/datastore/documentdb v1.0.0 →core/datastore/elasticsearch v1.0.0 →core/datastore/etcd v1.0.0 →core/datastore/ferretdb v1.0.0 →core/datastore/mariadb v1.0.0 →core/datastore/mariadb-operator v1.0.0 →core/datastore/memcached v1.0.0 →core/datastore/milvus v1.0.0 →core/datastore/mysql v1.0.0 →core/datastore/mysql-innodb-cluster v1.0.0 →core/datastore/mysql-operator v1.0.0 →core/datastore/opensearch v1.0.0 →core/datastore/pgvector v1.0.0 →core/datastore/postgres v1.0.0 →core/datastore/qdrant v1.0.0 →core/datastore/redis v1.0.0 →core/datastore/timescaledb v1.0.0 →core/datastore/valkey v1.0.0 →core/datastore/weaviate v1.0.0 →
被使用
使用套接字 «backend»
使用套接字 «databases»
使用套接字 «etcd»
使用套接字 «backend»
使用套接字 «backend»
使用套接字 «forward_target»
使用套接字 «logs»
使用套接字 «scrape_target»
使用套接字 «backend»
使用套接字 «database»
适用于
适用于
适用于
实现
实现