Skip to content

Commit

Permalink
scale back serverless updates
Browse files Browse the repository at this point in the history
  • Loading branch information
colleenmcginnis committed Nov 8, 2024
1 parent d750e9d commit e4b677b
Show file tree
Hide file tree
Showing 5 changed files with 7 additions and 7 deletions.
2 changes: 1 addition & 1 deletion docs/en/serverless/alerting/create-manage-rules.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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 **Service Inventory**, **Traces**, and **Dependencies** UIs.
* For APM alert types, you can select **Alerts and rules** and create rules directly from the **Services**, **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 <<observability-create-slo-burn-rate-alert-rule,Create SLO burn rate rule>> upon saving the SLO.

////
Expand Down
4 changes: 2 additions & 2 deletions docs/en/serverless/apm/apm-query-your-data.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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 <<observability-apm-services,Service Inventory>>, <<observability-apm-transactions,Transactions>>,
APM queries can be handy for removing noise from your data in the <<observability-apm-services,Services>>, <<observability-apm-transactions,Transactions>>,
<<observability-apm-errors,Errors>>, <<observability-apm-metrics,Metrics>>, and <<observability-apm-traces,Traces>> views.

For example, in the **Service Inventory** view, you can quickly view a list of all the instrumented services running on your production
For example, in the **Services** 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"`.

Expand Down
2 changes: 1 addition & 1 deletion docs/en/serverless/apm/apm-ui-overview.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ preview:[]
For a quick, high-level overview of the health and performance of your application,
start with:

* <<observability-apm-services,Service Inventory>>
* <<observability-apm-services,Services>>
* <<observability-apm-traces,Traces>>
* <<observability-apm-dependencies,Dependencies>>
* <<observability-apm-service-map,Service Map>>
Expand Down
2 changes: 1 addition & 1 deletion docs/en/serverless/apm/apm-ui-service-map.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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 **Service Inventory**, switch to the **Service Map** tab to get started.
From **Services**, 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.
Expand Down
4 changes: 2 additions & 2 deletions docs/en/serverless/apm/apm-ui-services.asciidoc
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
[[observability-apm-services]]
= Service Inventory
= Services

// :keywords: serverless, observability, reference

preview:[]

The **Service Inventory** provides a quick, high-level overview of the health and general
The **Services** 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:
Expand Down

0 comments on commit e4b677b

Please sign in to comment.