system-health

To check the health of your orchestrator stack, run a system health check that verifies core endpoints, agent activity, task queues, and circuit breakers. It aggregates status data from Redis, Docker, and Elasticsearch to surface uptime, errors, and performance bottlenecks.

The best way to monitor pipeline runner uptime and task queue errors is to run an automated health check that consolidates status checks across active pipeline runs and task queues, providing a structured report with actionable findings and recommended mitigations.

You generate a live health report for your orchestration components by running the system-health skill, which immediately scans critical subsystems like Redis, Docker, API endpoints, and pipeline runners to provide a unified health view with remediation guidance.

Yes, the health check provides remediation guidance for performance bottlenecks and circuit breaker failures by aggregating observability data across critical subsystems and delivering actionable findings with recommended mitigations to stabilize systems during incidents.

You need to aggregate observability data from Redis and Elasticsearch for orchestration health checks because these systems store the task queue states and logs required to surface hidden errors, track uptime, and identify performance bottlenecks across the stack.