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.
Asal-usul
- Digest konten
- sha256:bf3f8e4de581d48ff15094c39173367362f157624093eb39f6b2e114583d32a8
- Dipublikasikan
- 2026-11-10T10:07:30Z
- Identitas penandatangan
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Tanda tangan
- Resmiapplication/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
Referensi pada versi ini
oci://hub.aggrega.ai/component/core/ai-agent/agenta-worker-streams:1.0.0Parameter pengembang
Nilai yang ditetapkan pengembang di Aggregate.
| Nama | Tipe | Bawaan | Wajib | Deskripsi |
|---|---|---|---|---|
| streams | string | — | tidak | 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. |
Penentuan ukuran oleh operator
Ukuran infrastruktur yang disesuaikan operator untuk setiap lingkungan.
| Nama | Tipe | Bawaan | Wajib | Deskripsi |
|---|---|---|---|---|
| engine_version | string | v0.114.1 | tidak | 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 | tidak | Log verbosity the worker emits. |
| compute | object | — | tidak | — |
| overrides | object (open) | — | tidak | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Kontrak keluaran
Nilai yang dipublikasikan komponen ini kepada konsumen melalui topologi uses.
Tidak ada nilai keluaran yang dideklarasikan.
Soket uses
Soket dependensi yang menjadi jalur koneksi komponen ini. Target setiap koneksi yang dihubungkan melalui sebuah soket harus memenuhi selektor labelnya, dan setiap koneksi dapat membawa lampiran pada slot yang dideklarasikan soket tersebut. Slot wajib harus diisi oleh setiap koneksi yang dihubungkan oleh Aggregate atau Release melalui soket tersebut.
backend
- Selektor
- component.aggrega.ai/category=datastore
- Injeksi
- env
Slot yang dapat diisi oleh setiap koneksi melalui soket ini
| Slot | Selektor | Wajib | Injeksi | Sensitif | Deskripsi |
|---|---|---|---|---|---|
| credential | feature.aggrega.ai/kind=secret | tidak | env | ya | 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
- Selektor
- component.aggrega.ai/category=datastore
- Injeksi
- env
Slot yang dapat diisi oleh setiap koneksi melalui soket ini
| Slot | Selektor | Wajib | Injeksi | Sensitif | Deskripsi |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | tidak | file | ya | 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
- Selektor
- component.aggrega.ai/category=datastore
- Injeksi
- env
Slot yang dapat diisi oleh setiap koneksi melalui soket ini
| Slot | Selektor | Wajib | Injeksi | Sensitif | Deskripsi |
|---|---|---|---|---|---|
| server_ca | feature.aggrega.ai/kind=secret | tidak | file | ya | 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. |
Slot lampiran
Titik pengikatan bernama tempat sebuah Feature dilampirkan ke komponen ini. Selektor sebuah slot membatasi Feature mana yang dapat mengisinya, dan daftar injeksinya menyebutkan cara materi Feature dapat dikirimkan. Slot wajib harus terikat pada setiap instans, melalui lampiran pada instans tersebut atau pada cakupan di atasnya, dan slot sensitif dideklarasikan untuk menangani materi rahasia. Sebuah Feature juga dapat dilampirkan dengan nama yang tidak dideklarasikan oleh slot mana pun.
| Slot | Selektor | Wajib | Injeksi | Sensitif | Deskripsi |
|---|---|---|---|---|---|
| auth_key | feature.aggrega.ai/kind=secret | ya | env | ya | 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 | ya | env | ya | 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. |
Daftar izin injeksi mandiri
env
Relasi
Sisi bertipe ke dan dari entitas lain yang dipublikasikan. Referensi tanpa target yang dipublikasikan ditampilkan sebagai sisi yang terputus, bukan sebagai tautan.
Menggunakan
- menggunakanmenggunakan soket «backend»
component.aggrega.ai/category=datastore
Slot lampiran: 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 → - menggunakanmenggunakan soket «cache»
component.aggrega.ai/category=datastore
Slot lampiran: 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 → - menggunakanmenggunakan soket «queue»
component.aggrega.ai/category=datastore
Slot lampiran: 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 →
Digunakan oleh
menggunakan soket «runner»
menggunakan soket «api»
menggunakan soket «runner»
menggunakan soket «api»
menggunakan soket «services»
menggunakan soket «api»
menggunakan soket «services»
menggunakan soket «services»
menggunakan soket «sandbox»
menggunakan soket «plugin_daemon»
menggunakan soket «ssrf_proxy»
menggunakan soket «sandbox»
menggunakan soket «plugin_daemon»
menggunakan soket «ssrf_proxy»
menggunakan soket «api»
menggunakan soket «ssrf_proxy»
menggunakan soket «api»
menggunakan soket «api»
menggunakan soket «sandbox»
menggunakan soket «plugin_daemon»
menggunakan soket «ssrf_proxy»
menggunakan soket «sandbox»
menggunakan soket «plugin_daemon»
menggunakan soket «ssrf_proxy»
menggunakan soket «target_agent»
menggunakan soket «scrape_target»
berlaku untuk
berlaku untuk
berlaku untuk
mengimplementasikan