Monitoring covers Coroid's own health rather than your application's. You'll find it under Monitoring. Monitoring, along with Health, Performance and Status views.
Health
This indicates whether the services that Coroid relies on are operating normally.
It's worth checking this when something behaves oddly and you're unsure if the cause lies in your configuration or the platform. ruling out the platform takes seconds and prevents a lengthy investigation into the wrong area.
Performance
This shows how the platform is performing — including throughput, latency and processing times.
The key distinction to remember when interpreting this data is: queue time relates to capacity, execution time relates to work. A task that takes four hours because it waits three hours for a slot reflects a capacity issue. One that takes four hours of actual running time points to a scope or test-suite problem. Though the total time appears the same, the underlying causes and fixes differ.
Status
The service status view matches Coroid's public status page.
Check this first when something stops working across the board rather than affecting just one project. If the platform-wide symptoms appear while the status page remains healthy, the issue likely stems from your own configuration.
What this is not
This is not application monitoring. Coroid does not monitor your production services, and none of this information indicates whether your deployed application is healthy — that remains the role of 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 detect a specific condition and initiate remediation tasks. See Hooks and Sentinel Hooks and Sentinel.