Component
core/ai-agent/agenta-worker-streams
The stream-consuming worker tier of an agent workspace — the process that drains the platform's continuous streams and writes what they carry into the relational backend. Three families of stream reach it: the spans an instrumented application or an agent run emits, the platform's own internal events, and the transcript records of an agent session. It reads its work from the stream side of the queue wired through the `queue` socket, writes to the relational backend wired through `backend` using the two database names given on that edge, and uses the cache wired through `cache` for the same read-caching the rest of the platform does. Its `streams` value selects which families one container runs; left unset it runs all three, which is what a single-container installation wants. An Aggregate that needs one family scaled apart from the others declares a second instance of this same component with a value naming just that family — the stream names and consumer groups are unchanged by the split, so two instances share the work rather than duplicating it. Wire here because trace and session ingestion happens off the request path. With nothing running this tier the platform accepts spans and session records into the streams and never drains them, so the console's traces stay empty while nothing reports an error — which is why this is a component of its own and not an optional extra. It serves no port and nothing connects to it, so it publishes no provides contract. Realized on Kubernetes via its Helm Recipe, which synthesizes the tier as a stateless Deployment with no Service, running the platform image under the stream-consumer entry point.
Procedencia
- Digest del contenido
- sha256:bf3f8e4de581d48ff15094c39173367362f157624093eb39f6b2e114583d32a8
- Publicado
- 2026-11-10T10:07:30Z
- 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:449efce671658525cd980717242e96fcfe7402bb73c127edc51ac9ec5fe848cf
Referencia en esta versión
oci://hub.aggrega.ai/component/core/ai-agent/agenta-worker-streams:1.0.0Parámetros del desarrollador
Valores que el desarrollador establece en el Aggregate.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| streams | string | — | no | Comma-separated list of stream families this container runs, drawn from spans, events and records. Left unset it runs all three, which is what a single-container installation wants; naming a subset is how one family is scaled apart from the others. |
Dimensionamiento del operador
Dimensionamiento de la infraestructura que el operador ajusta para cada entorno.
| Nombre | Tipo | Predeterminado | Obligatorio | Descripción |
|---|---|---|---|---|
| engine_version | string | v0.114.1 | no | Platform API container image tag. This tier runs the same image as the control-plane API under a different entry point, so a Release moves both together. |
| log_level | string (DEBUG | INFO | WARNING | ERROR | CRITICAL) | INFO | no | Log verbosity the worker emits. |
| compute | object | — | no | — |
| overrides | object (open) | — | no | Provider-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.
No se declararon valores de salida.
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.
backend
- Selector
- component.aggrega.ai/category=datastore
- Inyección
- env
Slots que cada conexión a través de este socket puede llenar
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | no | env | sí | Password the worker authenticates to the relational backend this connection reaches with, delivered as an env secret reference and substituted into the connection URL at run time. The same credential is attached to the control-plane API's backend connection, because both reach the same server. Unattached, the Recipe emits the development literal `apppass`, the default the standard-library relational Recipes leave in place; this catalog publishes it, so every Release that leaves the slot unattached shares that password. |
cache
- Selector
- component.aggrega.ai/category=datastore
- Inyección
- env
Slots que cada conexión a través de este socket puede llenar
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | no | file | sí | Optional authority the platform's Redis client checks the cache's certificate against while the cache publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and names the file in the connection's URL. 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. |
queue
- Selector
- component.aggrega.ai/category=datastore
- Inyección
- env
Slots que cada conexión a través de este socket puede llenar
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | no | file | sí | Optional authority the platform's Redis client checks the queue's certificate against while the queue publishes protocol valkey-tls or redis-tls, where the image does not already trust the authority that signs it. Its Secret holds ca.crt. The Recipe mounts the whole Secret read-only and names the file in the connection's URL. The build halts on a server_ca publishing no Secret name, and on one wired to a queue 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.
| Slot | Selector | Obligatorio | Inyección | Sensible | Descripción |
|---|---|---|---|---|---|
| auth_key | feature.aggrega.ai/kind=secret | sí | env | sí | Required key the platform signs its own internal tokens with. It carries the same value as the control-plane API's slot. There is no default: the build halts when nothing fills this slot. |
| crypt_key | feature.aggrega.ai/kind=secret | sí | env | sí | Required key stored credentials are encrypted under. The worker decrypts them where a drained record references one, so it carries the same value as the control-plane API's slot. There is no default: the build halts when nothing fills this slot. |
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
- usausa el socket «backend»
component.aggrega.ai/category=datastore
Slots de acoplamiento: credential
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 → - usausa el socket «cache»
component.aggrega.ai/category=datastore
Slots de acoplamiento: 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 → - usausa el socket «queue»
component.aggrega.ai/category=datastore
Slots de acoplamiento: 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 →
Usado por
usa el socket «runner»
usa el socket «api»
usa el socket «runner»
usa el socket «api»
usa el socket «services»
usa el socket «api»
usa el socket «services»
usa el socket «services»
usa el socket «sandbox»
usa el socket «plugin_daemon»
usa el socket «ssrf_proxy»
usa el socket «sandbox»
usa el socket «plugin_daemon»
usa el socket «ssrf_proxy»
usa el socket «api»
usa el socket «ssrf_proxy»
usa el socket «api»
usa el socket «api»
usa el socket «sandbox»
usa el socket «plugin_daemon»
usa el socket «ssrf_proxy»
usa el socket «sandbox»
usa el socket «plugin_daemon»
usa el socket «ssrf_proxy»
usa el socket «target_agent»
usa el socket «scrape_target»
se aplica a
se aplica a
se aplica a
implementa