Pools Every machine runs are placed on, by pool: ec2, the instances orca launches for runs; kubernetes, a run's pods on the Kubernetes runner; and worker:<pool>, the machines of your own running orca worker. The one machine that runs the scheduler, this UI and Postgres is Control ; Watchdog lists the rules that pause pipelines.
This scheduler's runner is local: it runs every run on its own machine and launches no instances, so there are none to list and no per-instance cost. The machine is Control ; its price is the server's fixed price.
All 1 EC2 0 Kubernetes 0 Self-hosted 1 Pool: all
Machines? A row per machine of each pool runs are placed on: the EC2 instances orca launches, a Kubernetes run's pods, and the machines running orca worker for a worker:<pool> pool, the worker in the row's last column. Refreshed every 10 s. Docs ↗ No machines in this view.
Range: 24h 7d (UTC, by the hour)
Hosts that ran during each hour, by role.
1.0 0 11-07 17:00 UTC; heads 0; workers 0; control 1 11-07 18:00 UTC; heads 0; workers 0; control 1 11-07 19:00 UTC; heads 0; workers 0; control 1 11-07 20:00 UTC; heads 0; workers 0; control 1 11-07 21:00 UTC; heads 0; workers 0; control 1 11-07 22:00 UTC; heads 0; workers 0; control 1 11-07 23:00 UTC; heads 0; workers 0; control 1 11-08 00:00 UTC; heads 0; workers 0; control 1 11-08 01:00 UTC; heads 0; workers 0; control 1 11-08 02:00 UTC; heads 0; workers 0; control 1 11-08 03:00 UTC; heads 0; workers 0; control 1 11-08 04:00 UTC; heads 0; workers 0; control 1 11-08 05:00 UTC; heads 0; workers 0; control 1 11-08 06:00 UTC; heads 0; workers 0; control 1 11-08 07:00 UTC; heads 0; workers 0; control 1 11-08 08:00 UTC; heads 0; workers 0; control 1 11-08 09:00 UTC; heads 0; workers 0; control 1 11-08 10:00 UTC; heads 0; workers 0; control 1 11-08 11:00 UTC; heads 0; workers 0; control 1 11-08 12:00 UTC; heads 0; workers 0; control 1 11-08 13:00 UTC; heads 0; workers 0; control 1 11-08 14:00 UTC; heads 0; workers 0; control 1 11-08 15:00 UTC; heads 0; workers 0; control 1 11-08 16:00 UTC; heads 0; workers 0; control 1 17:00 23:00 05:00 11:00
Runs started and runs that ended each hour; failures (failed runs, and every failed step attempt, even one a retry fixed) are overlaid on the finished bar.
1000 0 11-07 17:00 UTC; started 20; finished 20; failures (runs and attempts) 0 11-07 18:00 UTC; started 20; finished 20; failures (runs and attempts) 0 11-07 19:00 UTC; started 20; finished 20; failures (runs and attempts) 0 11-07 20:00 UTC; started 22; finished 762; failures (runs and attempts) 0 11-07 21:00 UTC; started 53; finished 52; failures (runs and attempts) 0 11-07 22:00 UTC; started 42; finished 42; failures (runs and attempts) 0 11-07 23:00 UTC; started 64; finished 63; failures (runs and attempts) 0 11-08 00:00 UTC; started 68; finished 69; failures (runs and attempts) 0 11-08 01:00 UTC; started 62; finished 62; failures (runs and attempts) 0 11-08 02:00 UTC; started 61; finished 60; failures (runs and attempts) 0 11-08 03:00 UTC; started 91; finished 92; failures (runs and attempts) 0 11-08 04:00 UTC; started 252; finished 249; failures (runs and attempts) 13 11-08 05:00 UTC; started 134; finished 135; failures (runs and attempts) 0 11-08 06:00 UTC; started 145; finished 145; failures (runs and attempts) 0 11-08 07:00 UTC; started 143; finished 143; failures (runs and attempts) 0 11-08 08:00 UTC; started 138; finished 138; failures (runs and attempts) 0 11-08 09:00 UTC; started 133; finished 133; failures (runs and attempts) 0 11-08 10:00 UTC; started 120; finished 120; failures (runs and attempts) 1 11-08 11:00 UTC; started 121; finished 121; failures (runs and attempts) 0 11-08 12:00 UTC; started 126; finished 126; failures (runs and attempts) 13 11-08 13:00 UTC; started 136; finished 140; failures (runs and attempts) 0 11-08 14:00 UTC; started 179; finished 181; failures (runs and attempts) 1 11-08 15:00 UTC; started 142; finished 144; failures (runs and attempts) 0 11-08 16:00 UTC; started 131; finished 129; failures (runs and attempts) 1 17:00 23:00 05:00 11:00
The vCPUs of all sampled hosts: busy, and available.
Throughput summed over all sampled hosts.