diff --git a/docs/en/serverless/alerting/create-manage-rules.asciidoc b/docs/en/serverless/alerting/create-manage-rules.asciidoc index 2c9bfbefde..13fc1c6dbb 100644 --- a/docs/en/serverless/alerting/create-manage-rules.asciidoc +++ b/docs/en/serverless/alerting/create-manage-rules.asciidoc @@ -67,7 +67,7 @@ Learn more about Observability rules and how to create them: You start by defining the rule and how often it should be evaluated. You can extend these rules by adding an appropriate action (for example, send an email or create an issue) to be triggered when the rule conditions are met. These actions are defined within each rule and implemented by the appropriate connector for that action e.g. Slack, Jira. You can create any rules from scratch using the **Manage Rules** page, or you can create specific rule types from their respective UIs and benefit from some of the details being pre-filled (for example, Name and Tags). -* For APM alert types, you can select **Alerts and rules** and create rules directly from the **Services**, **Traces**, and **Dependencies** UIs. +* For APM alert types, you can select **Alerts and rules** and create rules directly from the **Service Inventory**, **Traces**, and **Dependencies** UIs. * For SLO alert types, from the **SLOs** page open the **More actions** menu image:images/icons/boxesHorizontal.svg[action menu] for an SLO and select **Create new alert rule**. Alternatively, when you create a new SLO, the **Create new SLO burn rate alert rule** checkbox is enabled by default and will prompt you to <> upon saving the SLO. //// diff --git a/docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc b/docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc index 9a4394f20c..2c2591e96b 100644 --- a/docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc +++ b/docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc @@ -16,7 +16,7 @@ address or region, is facing increased latency due to local data center issues. To find correlations: -. In your {obs-serverless} project, go to **Applications** → **Services**. +. In your {obs-serverless} project, go to **Applications** → **Service Inventory**. . Select a service. . Select the **Transactions** tab. . Select a transaction group in the **Transactions** table. diff --git a/docs/en/serverless/apm/apm-get-started.asciidoc b/docs/en/serverless/apm/apm-get-started.asciidoc index 08a55a1d3a..2b3b9856d8 100644 --- a/docs/en/serverless/apm/apm-get-started.asciidoc +++ b/docs/en/serverless/apm/apm-get-started.asciidoc @@ -164,7 +164,7 @@ refer to <>. After one or more APM agents are installed and successfully sending data, you can view application performance monitoring data in the UI. -In the _Applications_ section of the main menu, select **Services**. +In the _Applications_ section of the main menu, select **Service Inventory**. This will show a high-level overview of the health and general performance of all your services. Learn more about visualizing APM data in <>. diff --git a/docs/en/serverless/apm/apm-query-your-data.asciidoc b/docs/en/serverless/apm/apm-query-your-data.asciidoc index 7d0e1e62cf..c3f244da08 100644 --- a/docs/en/serverless/apm/apm-query-your-data.asciidoc +++ b/docs/en/serverless/apm/apm-query-your-data.asciidoc @@ -28,10 +28,10 @@ To learn more about the {kib} query language capabilities, see the {kibana-ref}/ [[observability-apm-query-your-data-apm-queries]] == APM queries -APM queries can be handy for removing noise from your data in the <>, <>, +APM queries can be handy for removing noise from your data in the <>, <>, <>, <>, and <> views. -For example, in the **Services** view, you can quickly view a list of all the instrumented services running on your production +For example, in the **Service Inventory** view, you can quickly view a list of all the instrumented services running on your production environment: `service.environment : production`. Or filter the list by including the APM agent's name and the host it’s running on: `service.environment : "production" and agent.name : "java" and host.name : "prod-server1"`. diff --git a/docs/en/serverless/apm/apm-ui-overview.asciidoc b/docs/en/serverless/apm/apm-ui-overview.asciidoc index 1698cfce9b..82edfc6b74 100644 --- a/docs/en/serverless/apm/apm-ui-overview.asciidoc +++ b/docs/en/serverless/apm/apm-ui-overview.asciidoc @@ -9,7 +9,7 @@ preview:[] For a quick, high-level overview of the health and performance of your application, start with: -* <> +* <> * <> * <> * <> diff --git a/docs/en/serverless/apm/apm-ui-service-map.asciidoc b/docs/en/serverless/apm/apm-ui-service-map.asciidoc index 8bf6d636c8..496eb05a47 100644 --- a/docs/en/serverless/apm/apm-ui-service-map.asciidoc +++ b/docs/en/serverless/apm/apm-ui-service-map.asciidoc @@ -30,7 +30,7 @@ distributed tracing will not work, and the connection will not be drawn on the m [[observability-apm-service-map-visualize-your-architecture]] == Visualize your architecture -From **Services**, switch to the **Service Map** tab to get started. +From **Service Inventory**, switch to the **Service Map** tab to get started. By default, all instrumented services and connections are shown. Whether you're onboarding a new engineer, or just trying to grasp the big picture, drag things around, zoom in and out, and begin to visualize how your services are connected. diff --git a/docs/en/serverless/apm/apm-ui-services.asciidoc b/docs/en/serverless/apm/apm-ui-services.asciidoc index 8c87b3f985..16886e094d 100644 --- a/docs/en/serverless/apm/apm-ui-services.asciidoc +++ b/docs/en/serverless/apm/apm-ui-services.asciidoc @@ -1,11 +1,11 @@ [[observability-apm-services]] -= Services += Service Inventory // :keywords: serverless, observability, reference preview:[] -The **Services** inventory provides a quick, high-level overview of the health and general +The **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: @@ -45,7 +45,7 @@ image::images/services/apm-service-group.png[Example view of service group in th To create a service group: -. In your {obs-serverless} project, go to **Applications** → **Services**. +. In your {obs-serverless} project, go to **Applications** → **Service Inventory**. . Switch to **Service groups**. . Click **Create group**. . Specify a name, color, and description.