View services
Read the APM service list, grouped by system, with each service's health, traffic, errors, latency and inventory link.
APM → Services is the catalog of everything that sends telemetry. Each service appears on its own when its first trace arrives; you don't have to register it.
Before you start
View permission in the APM module.
At least one instrumented application. If the list is empty, click See how to instrument a system.
Steps
Go to APM → Services.
Review the indicators at the top: Services, With problems, Environments, Browsers and Inactive.
Use Filter… to search for a service by name.
Click a service's name to open its detail page.
How to read the table
Services are grouped by the inventory group they belong to (or by their service.namespace if they don't have a group yet). The same service can have one row per environment.
Column | What it shows |
|---|---|
Colored dot | Health over the last few minutes: Healthy, Slow, With errors, No data or No traffic |
Service | Name, type (Server, Browser, Process or Other), environment, version and language. Active alerts appear as red tags |
Where it runs | The detected platform: cloud, container, cluster or server |
Traffic | Requests per minute |
Errors | Percentage of requests with an error. In red if it exceeds the threshold |
p95 | Latency that 95% of requests do not exceed. In yellow if it exceeds the threshold |
Seen | When the last data arrived |
Link | The inventory group and, if any, the server, web service or Railway service it was linked to. No group means it still needs to be linked |
A service that has gone days without telemetry becomes Inactive: it is shown dimmed and does not appear on the dependency map. The number of days is set in Retention and personal data.
Delete a service
Useful for test services that no longer exist.
Click the trash button on its row (or Delete service on its detail page).
Type the service's name to confirm and click Delete service.
Its traces, logs, metrics, errors and map connectors are deleted, and it no longer counts toward the plan. If it sends telemetry again, it reappears. Only someone with the Administer permission in APM can do this.