IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Navigate the APM UI Traces »
Elastic Docs ›Elastic Observability [8.14] ›Application performance monitoring (APM) ›Navigate the APM UI

Services

edit

Services

edit

Service inventory provides a quick, high-level overview of the health and general performance of all instrumented services.

To help surface potential issues, services are sorted by their health status: critical > warning > healthy > unknown. Health status is powered by machine learning and requires anomaly detection to be enabled.

In addition to health status, active alerts for each service are prominently displayed in the service inventory table. Selecting an active alert badge brings you to the Alerts tab where you can learn more about the active alert and take action.

Example view of services table the APM UI in Kibana
Service groups
edit

This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.

Group services together to build meaningful views that remove noise, simplify investigations across services, and combine related alerts. Service groups are Kibana space-specific and available for any users with appropriate access.

Example view of service group in the APM UI in Kibana

To enable Service groups, open Kibana and navigate to Stack Management > Advanced Settings > Observability, and enable the Service groups feature.

To create a service group:

  1. Navigate to Observability > APM > Services.
  2. Switch to Service groups.
  3. Click Create group.
  4. Specify a name, color, and description.
  5. Click Select services.
  6. Specify a Kibana Query Language (KQL) query to filter services by one or more of the following dimensions: agent.name, service.name, service.language.name, service.environment, labels.<xyz>. Services that match the query within the last 24 hours will be assigned to the group.

Examples

Not sure where to get started? Here are some sample queries you can build from:

  • Group services by environment—​in this example, "production": service.environment : "production"
  • Group services by name—​this example groups those that end in "beat": service.name : *beat (matches services named "Auditbeat", "Heartbeat", "Filebeat", etc.)
« Navigate the APM UI Traces »