Monitoring covers Coroid's own health rather than your application's. Find it under Monitoring, with Health, Performance and Status views.
Health
Whether the services Coroid depends on are operating normally.
Worth checking when something behaves oddly and you cannot tell whether the cause is your configuration or the platform. Ruling the platform out takes seconds and saves a long investigation in the wrong place.
Performance
How the platform is performing — throughput, latency and processing times.
The distinction that matters when reading this: queue time is capacity, execution time is work. A task that took four hours because it waited three for a slot is a capacity signal. One that took four hours running is a scope or test-suite signal. They look identical in a total and have unrelated fixes.
Status
The service status view, corresponding to Coroid's public status page.
Check it first when something stops working across the board rather than on one project. Platform-wide symptoms with a healthy status page point back at your own configuration.
What this is not
This is not application monitoring. Coroid does not watch your production services, and nothing here tells you whether your deployed application is healthy — that remains your own observability stack.
What Coroid can do is react to signals from those systems. A hook can respond to a deploy event, and Sentinel can watch for a condition and open remediation work. See Hooks and Sentinel.