IDE Services provides the /api/metrics endpoint to monitor the state of your infrastructure. It relies on Prometheus to expose database connections, CPU usage, uptime, and more.
The response will look similar to this example:
# HELP logback_events_total Number of log events that were enabled by the effective log level
{...}
For better system observability, you can use the following metrics:
process_start_time_seconds
Defines the start time of the process since unix epoch in seconds.
process_uptime_seconds
Defines the uptime of the Java virtual machine.
r2dbc_pool_pending_connections
Defines the size of pending to acquire connections from the underlying connection factory.
r2dbc_pool_allocated_connections
Defines the size of allocated connections in the pool which are in active use or idle.
r2dbc_pool_idle_connections
Defines the size of idle connections in the pool.
executor_pool_core_threads
Defines the core number of threads for the pool.
cwm_lobby_current_sessions
Defines the number of Code With Me sessions currently running.
cwm_lobby_client_join_counter_events_total
Defines the number of client join events.
system_cpu_usage
Defines the recent CPU usage of the system the application is running in.
process_cpu_usage
Defines the recent CPU usage for the Java Virtual Machine process.