This documentation contains work-in-progress information for future Elastic Stack and Cloud releases. Use the version selector to view supported release docs. It also contains some Elastic Cloud serverless information. Check out our serverless docs for more details.
« High-level overviews of application data Traces »
Elastic Docs ›Elastic Observability [master] ›Application and service monitoring ›Application performance monitoring (APM) ›View and analyze data ›High-level overviews of application data

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 Applications UI in Kibana

Want to monitor service logs without instrumenting all your services? Learn about our Inventory.

Service groupsedit

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 Applications UI in Kibana

To create a service group:

  1. To open Service inventory, find Applications in the main menu or use the global search field.
  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.)
« High-level overviews of application data Traces »