Worker

The Rhesis worker runs background processing on Celery with Redis as the broker and result backend: test execution, trace ingestion, metric evaluation, and Architect chat turns.

Design and internals

• Architecture: how the worker relates to the backend, SDK, database, and broker.
• Multi-Worker RPC: routing RPC requests to the worker that holds an SDK’s WebSocket connection.
• Background Tasks: Celery configuration, the BaseTask base class, tenant context, and the task launcher.
• Architect Background Tasks: Architect chat execution and async resume.
• Trace Ingestion Pipeline: how traces flow through storage, linking, enrichment, and metric evaluation.
• Test Execution: the executor architecture and async batch engine.
• Test Types: single-turn vs. multi-turn tests.
• Execution Modes: parallel vs. sequential test runs.

Operations

• Logging: log sources, configuration, and analysis.
• Troubleshooting: stuck tasks, tenant-context errors, broker connectivity, and worker registration.
• GKE Troubleshooting: diagnosing workers in Google Kubernetes Engine.

Related

• Backend: the API services that queue background tasks.