diff --git a/docs/en/observability/apm-alerts.asciidoc b/docs/en/observability/apm-alerts.asciidoc index 063322a2cd..34917de315 100644 --- a/docs/en/observability/apm-alerts.asciidoc +++ b/docs/en/observability/apm-alerts.asciidoc @@ -1,7 +1,7 @@ [[apm-alerts]] = APM alerts and rules -The APM UI allows you to define **rules** to detect complex conditions within your APM data +The Applications UI allows you to define **rules** to detect complex conditions within your APM data and trigger built-in **actions** when those conditions are met. The following **rules** are supported: @@ -15,7 +15,7 @@ Alert when either the latency of a service is anomalous. Anomaly rules can be se Alert when the number of errors in a service exceeds a defined threshold. Error count rules can be set at the environment level, service level, and error group level. [role="screenshot"] -image::./images/apm-alert.png[Create an alert in the APM UI] +image::./images/apm-alert.png[Create an alert in the Applications UI] Below, we'll walk through the creation of two APM rules. @@ -40,7 +40,7 @@ This guide will create an alert for all services based on the following criteria * Check every five minutes * Send an alert to a Slack channel when the rule status changes -From any page in the APM UI, select **Alerts and rules** > **Create anomaly rule**. +From any page in the Applications UI, select **Alerts and rules** > **Create anomaly rule**. Change the name of the rule, but do not edit the tags. Based on the criteria above, define the following rule details: @@ -85,7 +85,7 @@ This guide will create an alert for an error group ID based on the following cri * Check every 1 minute * Send the alert via email to the site reliability team -From any page in the APM UI, select **Alerts and rules** > **Create error count rule**. +From any page in the Applications UI, select **Alerts and rules** > **Create error count rule**. Change the name of the alert, but do not edit the tags. Based on the criteria above, define the following rule details: @@ -129,7 +129,7 @@ Click **Save**. The alert has been created and is now active! [[apm-alert-view-active]] == View active alerts -Active alerts are displayed and grouped in multiple ways in the APM UI. +Active alerts are displayed and grouped in multiple ways in the Applications UI. [float] [[apm-alert-view-group]] @@ -139,7 +139,7 @@ If you're using the <> feature, you can view aler From the service group overview page, click the red alert indicator to open the **Alerts** tab with a predefined filter that matches the filter used when creating the service group. [role="screenshot"] -image::./images/apm-service-group.png[Example view of service group in the APM UI in Kibana] +image::./images/apm-service-group.png[Example view of service group in the Applications UI in Kibana] [float] [[apm-alert-view-service]] @@ -155,7 +155,7 @@ image::./images/active-alert-service.png[View active alerts by service] [[apm-alert-manage]] == Manage alerts and rules -From the APM UI, select **Alerts and rules** > **Manage rules** to be taken to +From the Applications UI, select **Alerts and rules** > **Manage rules** to be taken to the {kib} *{rules-ui}* page. From this page, you can disable, mute, and delete APM alerts. diff --git a/docs/en/observability/apm.asciidoc b/docs/en/observability/apm.asciidoc index ba2f844727..0eed6e5b20 100644 --- a/docs/en/observability/apm.asciidoc +++ b/docs/en/observability/apm.asciidoc @@ -30,7 +30,7 @@ database queries, calls to caches, external HTTP requests, and more. This makes it easy to pinpoint and fix performance problems quickly. [role="screenshot"] -image::images/apm-app-landing.png[APM UI in {kib}] +image::images/apm-app-landing.png[Applications UI in {kib}] Elastic APM also automatically collects unhandled errors and exceptions. Errors are grouped based primarily on the stack trace, diff --git a/docs/en/observability/apm/act-on-data/custom-links.asciidoc b/docs/en/observability/apm/act-on-data/custom-links.asciidoc index f4bc31408b..1c866734d5 100644 --- a/docs/en/observability/apm/act-on-data/custom-links.asciidoc +++ b/docs/en/observability/apm/act-on-data/custom-links.asciidoc @@ -1,5 +1,5 @@ [[apm-custom-links]] -= Custom links in the APM UI += Custom links in the Applications UI ++++ Create custom links @@ -7,7 +7,7 @@ Elastic's custom link feature allows you to easily create up to 500 dynamic links based on your specific APM data. -Custom links can be filtered to only appear in the APM UI for relevant services, +Custom links can be filtered to only appear in the Applications UI for relevant services, environments, transaction types, or transaction names. Ready to dive in? Jump straight to the <>. @@ -21,7 +21,7 @@ The easiest way to create a custom link is from within the actions dropdown in t This method will automatically apply filters, scoping the link to that specific service, environment, transaction type, and transaction name. -Alternatively, you can create a custom link in the APM UI by navigating to **Settings** > **Customize UI**, +Alternatively, you can create a custom link in the Applications UI by navigating to **Settings** > **Customize UI**, and selecting **Create custom link**. [float] @@ -43,7 +43,7 @@ These variables will be replaced with transaction metadata when the link is clic Because everyone's data is different, you'll need to examine your traces to see what metadata is available for use. -To do this, select a trace in the APM UI, and click **Metadata** in the **Trace Sample** table. +To do this, select a trace in the Applications UI, and click **Metadata** in the **Trace Sample** table. [role="screenshot"] image::./images/example-metadata.png[Example metadata] diff --git a/docs/en/observability/apm/act-on-data/index.asciidoc b/docs/en/observability/apm/act-on-data/index.asciidoc index a3036dcf71..3803496d60 100644 --- a/docs/en/observability/apm/act-on-data/index.asciidoc +++ b/docs/en/observability/apm/act-on-data/index.asciidoc @@ -5,16 +5,16 @@ Act on data ++++ -In addition to exploring visualizations in the APM UI in {kib}, you can make your application data +In addition to exploring visualizations in the Applications UI in {kib}, you can make your application data more actionable with: -* *Alerts and rules*: The APM UI allows you to define rules to detect complex +* *Alerts and rules*: The Applications UI allows you to define rules to detect complex conditions within your APM data and trigger built-in actions when those conditions are met. Read more about alerts and rules in the <>. * *Custom links*: Build URLs that contain relevant metadata from a specific trace. For example, you can create a link that will take you to a page where you can open a new GitHub issue with context already auto-populated in the issue body. - These links will be shown in the _Actions_ context menu in selected areas of the APM UI (for example, by transaction details). + These links will be shown in the _Actions_ context menu in selected areas of the Applications UI (for example, by transaction details). Read more in <>. :leveloffset: +1 diff --git a/docs/en/observability/apm/api/api-ui.asciidoc b/docs/en/observability/apm/api/api-ui.asciidoc index 8bf85cf5ff..88bc879dcd 100644 --- a/docs/en/observability/apm/api/api-ui.asciidoc +++ b/docs/en/observability/apm/api/api-ui.asciidoc @@ -1,7 +1,7 @@ [[apm-app-api]] = APM UI API -Some APM UI features are provided via a REST API: +Some Applications UI features are provided via a REST API: * <> * <> @@ -45,7 +45,7 @@ users interacting with APM APIs must have <> -| {kib} APIs specific to working with the APM UI including updating configuration options, +| {kib} APIs specific to working with the Applications UI including updating configuration options, uploading real user monitoring (RUM) source maps, adding annotations, and more. | <> | APIs for working with APM Server. diff --git a/docs/en/observability/apm/collect-application-data/agents/agent-configuration.asciidoc b/docs/en/observability/apm/collect-application-data/agents/agent-configuration.asciidoc index 7441b33b76..2e0db08a26 100644 --- a/docs/en/observability/apm/collect-application-data/agents/agent-configuration.asciidoc +++ b/docs/en/observability/apm/collect-application-data/agents/agent-configuration.asciidoc @@ -5,11 +5,11 @@ Centrally configure APM agents in Kibana ++++ -APM Agent configuration allows you to fine-tune your APM agent configuration from within the APM UI. +APM Agent configuration allows you to fine-tune your APM agent configuration from within the Applications UI. Changes are automatically propagated to your APM agents, so there's no need to redeploy. To get started, choose the services and environments you wish to configure. -The APM UI will let you know when your APM agents have applied your configurations. +The Applications UI will let you know when your APM agents have applied your configurations. [role="screenshot"] image::./images/apm-agent-configuration.png[APM Agent configuration in Kibana] @@ -17,7 +17,7 @@ image::./images/apm-agent-configuration.png[APM Agent configuration in Kibana] [float] == Precedence -Configurations set from the APM UI take precedence over configurations set locally in each APM agent. +Configurations set from the Applications UI take precedence over configurations set locally in each APM agent. However, if APM Server is slow to respond, is offline, reports an error, etc., APM agents will use local defaults until they're able to update the configuration. For this reason, it is still essential to set custom default configurations locally in each of your APM agents. @@ -26,7 +26,7 @@ For this reason, it is still essential to set custom default configurations loca == Supported configurations Each APM agent has a list of supported configurations. -After selecting a Service name and environment in the APM UI, +After selecting a Service name and environment in the Applications UI, a list of all supported configuration options, including descriptions and default values, will be displayed. diff --git a/docs/en/observability/apm/collect-application-data/agents/index.asciidoc b/docs/en/observability/apm/collect-application-data/agents/index.asciidoc index d52dab9eee..16f398e673 100644 --- a/docs/en/observability/apm/collect-application-data/agents/index.asciidoc +++ b/docs/en/observability/apm/collect-application-data/agents/index.asciidoc @@ -27,7 +27,7 @@ documentation to learn how to install the agent, configure it, and more: == More APM agent resources Though you should refer to each APM agent's documentation for information on using the agent, -there are some tasks you can complete in the APM UI: +there are some tasks you can complete in the Applications UI: * <> * <> diff --git a/docs/en/observability/apm/collect-application-data/agents/source-map-how-to.asciidoc b/docs/en/observability/apm/collect-application-data/agents/source-map-how-to.asciidoc index 8c76192810..6643601276 100644 --- a/docs/en/observability/apm/collect-application-data/agents/source-map-how-to.asciidoc +++ b/docs/en/observability/apm/collect-application-data/agents/source-map-how-to.asciidoc @@ -10,11 +10,11 @@ and not something you only do when you see unhelpful errors. That's because uploading source maps after errors happen won't make old errors magically readable — errors must occur again for source mapping to occur. -Here's an example of an exception stack trace in the APM UI when using minified code. +Here's an example of an exception stack trace in the Applications UI when using minified code. As you can see, it's not very helpful. [role="screenshot"] -image::images/source-map-before.png[APM UI without source mapping] +image::images/source-map-before.png[Applications UI without source mapping] With a source map, minified files are mapped back to the original source code, allowing you to maintain the speed advantage of minified code, @@ -22,9 +22,9 @@ without losing the ability to quickly and easily debug your application. Here's the same example as before, but with a source map uploaded and applied: [role="screenshot"] -image::images/source-map-after.png[APM UI with source mapping] +image::images/source-map-after.png[Applications UI with source mapping] -Follow the steps below to enable source mapping your error stack traces in the APM UI: +Follow the steps below to enable source mapping your error stack traces in the Applications UI: * <> * <> diff --git a/docs/en/observability/apm/collect-application-data/jaeger-integration.asciidoc b/docs/en/observability/apm/collect-application-data/jaeger-integration.asciidoc index 47c1cb42d6..67ef48810a 100644 --- a/docs/en/observability/apm/collect-application-data/jaeger-integration.asciidoc +++ b/docs/en/observability/apm/collect-application-data/jaeger-integration.asciidoc @@ -77,7 +77,7 @@ See <> to learn more. [[apm-configure-sampling-local-jaeger]] ==== Local sampling in each Jaeger client -If you don't have access to the APM UI, +If you don't have access to the Applications UI, you'll need to change the Jaeger client's `sampler.type` and `sampler.param`. This enables you to set the sampling configuration locally in each Jaeger client. See the official https://www.jaegertracing.io/docs/1.27/sampling/[Jaeger sampling documentation] @@ -87,7 +87,7 @@ for more information. [[apm-configure-start-jaeger]] === Start sending data -That's it! Data sent from Jaeger clients to the APM Server can now be viewed in the APM UI. +That's it! Data sent from Jaeger clients to the APM Server can now be viewed in the Applications UI. [float] [[apm-caveats-jaeger]] @@ -106,7 +106,7 @@ it is not possible to mix and match the use of Elastic's APM agents and Jaeger's * Jaeger clients only sends trace data. APM agents support a larger number of features, like multiple types of metrics, and application breakdown charts. -When using Jaeger, features like this will not be available in the APM UI. +When using Jaeger, features like this will not be available in the Applications UI. * Elastic APM's <> is different than Jaegers. For Jaeger trace data to work with Elastic's data model, we rely on spans being tagged with the appropriate https://github.com/opentracing/specification/blob/master/semantic_conventions.md[`span.kind`]. diff --git a/docs/en/observability/apm/collect-application-data/open-telemetry/otel-limitations.asciidoc b/docs/en/observability/apm/collect-application-data/open-telemetry/otel-limitations.asciidoc index 1817d62dff..30a45d649d 100644 --- a/docs/en/observability/apm/collect-application-data/open-telemetry/otel-limitations.asciidoc +++ b/docs/en/observability/apm/collect-application-data/open-telemetry/otel-limitations.asciidoc @@ -5,7 +5,7 @@ [[apm-open-telemetry-traces-limitations]] == OpenTelemetry traces -* Traces of applications using `messaging` semantics might be wrongly displayed as `transactions` in the APM UI, while they should be considered `spans` (see issue https://github.com/elastic/apm-server/issues/7001[#7001]). +* Traces of applications using `messaging` semantics might be wrongly displayed as `transactions` in the Applications UI, while they should be considered `spans` (see issue https://github.com/elastic/apm-server/issues/7001[#7001]). * Inability to see Stack traces in spans. * Inability in APM views to view the "Time Spent by Span Type" (see issue https://github.com/elastic/apm-server/issues/5747[#5747]). diff --git a/docs/en/observability/apm/configure/agent-config.asciidoc b/docs/en/observability/apm/configure/agent-config.asciidoc index 40abb459f2..2550290cd1 100644 --- a/docs/en/observability/apm/configure/agent-config.asciidoc +++ b/docs/en/observability/apm/configure/agent-config.asciidoc @@ -11,7 +11,7 @@ image:./binary-yes-fm-yes.svg[supported deployment methods] APM agent configuration is supported by all APM Server deployment methods. **** -APM agent configuration allows you to fine-tune your APM agents from within the APM UI. +APM agent configuration allows you to fine-tune your APM agents from within the Applications UI. Changes are automatically propagated to your APM agents, so there's no need to redeploy your applications. To learn more about this feature, see <>. diff --git a/docs/en/observability/apm/configure/instrumentation.asciidoc b/docs/en/observability/apm/configure/instrumentation.asciidoc index 7b6f356c30..aac2206f47 100644 --- a/docs/en/observability/apm/configure/instrumentation.asciidoc +++ b/docs/en/observability/apm/configure/instrumentation.asciidoc @@ -42,7 +42,7 @@ Defaults to `false`. === `environment` Set the environment in which APM Server is running, for example, `staging`, `production`, `dev`, etc. -Environments can be filtered in the <>. +Environments can be filtered in the <>. [float] === `hosts` diff --git a/docs/en/observability/apm/data-model/data-model-metrics.asciidoc b/docs/en/observability/apm/data-model/data-model-metrics.asciidoc index 9f2161c2e1..9e97c9165f 100644 --- a/docs/en/observability/apm/data-model/data-model-metrics.asciidoc +++ b/docs/en/observability/apm/data-model/data-model-metrics.asciidoc @@ -4,7 +4,7 @@ **Metrics** measure the state of a system by gathering information on a regular interval. There are two types of APM metrics: * **System metrics**: Basic infrastructure and application metrics. -* **Calculated metrics**: Aggregated trace event metrics used to power visualizations in the APM UI. +* **Calculated metrics**: Aggregated trace event metrics used to power visualizations in the Applications UI. [float] == System metrics @@ -54,7 +54,7 @@ include::{apm-server-root}/docs/data/elasticsearch/metricset.json[] [float] == Calculated metrics -APM agents and APM Server calculate metrics from trace events to power visualizations in the APM UI. +APM agents and APM Server calculate metrics from trace events to power visualizations in the Applications UI. Calculated metrics are an implementation detail and while we aim for stability for these data models, the dimensions and concrete limits for aggregations are subject to change within minor version updates. @@ -104,7 +104,7 @@ include::{apm-server-root}/docs/data/elasticsearch/span_breakdown.json[] [float] === Transaction metrics -To power <> visualizations, +To power <> visualizations, APM Server aggregates transaction events into latency distribution metrics. *`transaction.duration.summary`* and *`transaction.duration.histogram`*:: @@ -175,7 +175,7 @@ include::{apm-server-root}/docs/data/elasticsearch/transaction_metric.json[] [float] === Service-transaction metrics -To power <> visualizations, +To power <> visualizations, APM Server aggregates transaction events into service-transaction metrics. Service-transaction metrics are similar to transaction metrics, but they usually have a much lower cardinality as they have significantly fewer dimensions. @@ -221,7 +221,7 @@ include::{apm-server-root}/docs/data/elasticsearch/service_transaction_metric.js [float] === Service-destination metrics -To power <> visualizations, +To power <> visualizations, APM Server aggregates span events into service-destination metrics. *`span.destination.service.response_time.count`* and *`span.destination.service.response_time.sum.us`*:: @@ -269,7 +269,7 @@ include::{apm-server-root}/docs/data/elasticsearch/service_destination_metric.js [float] === Service-summary metrics -To power <> visualizations, +To power <> visualizations, APM Server aggregates transaction, error, log, and metric events into service-summary metrics. These metric documents can be identified by searching for `metricset.name: service_summary`. diff --git a/docs/en/observability/apm/data-model/data-model-spans.asciidoc b/docs/en/observability/apm/data-model/data-model-spans.asciidoc index a0e395b2fb..4f4b110535 100644 --- a/docs/en/observability/apm/data-model/data-model-spans.asciidoc +++ b/docs/en/observability/apm/data-model/data-model-spans.asciidoc @@ -30,7 +30,7 @@ and non-keyword fields, like `span.start.us`, to 10,000 characters. For performance reasons, APM agents can choose to sample or omit spans purposefully. This can be useful in preventing edge cases, like long-running transactions with over 100 spans, that would otherwise overload both the Agent and the APM Server. -When this occurs, the APM UI will display the number of spans dropped. +When this occurs, the Applications UI will display the number of spans dropped. To configure the number of spans recorded per transaction, see the relevant Agent documentation: @@ -52,7 +52,7 @@ Agents stream spans to the APM Server separately from their transactions. Because of this, unforeseen errors may cause spans to go missing. Agents know how many spans a transaction should have; if the number of expected spans does not equal the number of spans received by the APM Server, -the APM UI will calculate the difference and display a message. +the Applications UI will calculate the difference and display a message. [float] == Data streams diff --git a/docs/en/observability/apm/data-model/distributed-tracing.asciidoc b/docs/en/observability/apm/data-model/distributed-tracing.asciidoc index dbb1e6df76..d9e6ecc628 100644 --- a/docs/en/observability/apm/data-model/distributed-tracing.asciidoc +++ b/docs/en/observability/apm/data-model/distributed-tracing.asciidoc @@ -94,10 +94,10 @@ For backward-compatibility purposes, new versions of Elastic agents still suppor [[apm-visualize-distributed-tracing]] === Visualize distributed tracing -The APM UI's timeline visualization provides a visual deep-dive into each of your application's traces: +The Applications UI's timeline visualization provides a visual deep-dive into each of your application's traces: [role="screenshot"] -image::./images/apm-distributed-tracing.png[Distributed tracing in the APM UI] +image::./images/apm-distributed-tracing.png[Distributed tracing in the Applications UI] [float] [[apm-manual-distributed-tracing]] diff --git a/docs/en/observability/apm/data-model/transactions/index.asciidoc b/docs/en/observability/apm/data-model/transactions/index.asciidoc index 3b4ade2936..549b6ff56c 100644 --- a/docs/en/observability/apm/data-model/transactions/index.asciidoc +++ b/docs/en/observability/apm/data-model/transactions/index.asciidoc @@ -32,7 +32,7 @@ which are points in time relative to the start of the transaction with some labe In addition, agents provide options for users to capture custom <>. Metadata can be indexed - <>, or not-indexed - <>. -Transactions are grouped by their `type` and `name` in the APM UI's +Transactions are grouped by their `type` and `name` in the Applications UI's <>. If you're using a supported framework, APM agents will automatically handle the naming for you. If you're not, or if you wish to override the default, diff --git a/docs/en/observability/apm/getting-started-apm/get-started-with-apm-server-binary.asciidoc b/docs/en/observability/apm/getting-started-apm/get-started-with-apm-server-binary.asciidoc index 4087a8cc64..82b7b23a53 100644 --- a/docs/en/observability/apm/getting-started-apm/get-started-with-apm-server-binary.asciidoc +++ b/docs/en/observability/apm/getting-started-apm/get-started-with-apm-server-binary.asciidoc @@ -12,7 +12,7 @@ First, see the https://www.elastic.co/support/matrix[Elastic Support Matrix] for You'll need: * *{es}* for storing and indexing data. -* *{kib}* for visualizing with the APM UI. +* *{kib}* for visualizing with the Applications UI. We recommend you use the same version of {es}, {kib}, and APM Server. See {stack-ref}/installing-elastic-stack.html[Installing the {stack}] @@ -321,10 +321,10 @@ include::{observability-docs-root}/docs/en/observability/apm/tab-widgets/install == Step 5: View your data Once you have at least one {apm-agent} sending data to APM Server, -you can start visualizing your data in the <>. +you can start visualizing your data in the <>. [role="screenshot"] -image::./images/kibana-apm-sample-data.png[APM UI with data] +image::./images/kibana-apm-sample-data.png[Applications UI with data] // If you're migrating from Jaeger, see <>. diff --git a/docs/en/observability/apm/getting-started-apm/get-started-with-fleet-apm-server.asciidoc b/docs/en/observability/apm/getting-started-apm/get-started-with-fleet-apm-server.asciidoc index 261bf4617a..f68f9a49e1 100644 --- a/docs/en/observability/apm/getting-started-apm/get-started-with-fleet-apm-server.asciidoc +++ b/docs/en/observability/apm/getting-started-apm/get-started-with-fleet-apm-server.asciidoc @@ -67,4 +67,4 @@ Back in {kib}, under {observability}, select APM. You should see application performance monitoring data flowing into the {stack}! [role="screenshot"] -image::./images/kibana-apm-sample-data.png[APM UI with data] +image::./images/kibana-apm-sample-data.png[Applications UI with data] diff --git a/docs/en/observability/apm/images/apm-ui-api-key.png b/docs/en/observability/apm/images/apm-ui-api-key.png index eae7ab1829..b110e4e876 100644 Binary files a/docs/en/observability/apm/images/apm-ui-api-key.png and b/docs/en/observability/apm/images/apm-ui-api-key.png differ diff --git a/docs/en/observability/apm/manage-storage/custom-index-template.asciidoc b/docs/en/observability/apm/manage-storage/custom-index-template.asciidoc index 51e47e3e93..3ba94d595d 100644 --- a/docs/en/observability/apm/manage-storage/custom-index-template.asciidoc +++ b/docs/en/observability/apm/manage-storage/custom-index-template.asciidoc @@ -23,7 +23,7 @@ Select any of the APM index templates to view their relevant component templates == Edit the {es} index template WARNING: Custom index mappings may conflict with the mappings defined by the {es} apm-data plugin -and may break the APM integration and APM UI in {kib}. +and may break the APM integration and Applications UI in {kib}. Do not change or customize any default mappings. The APM index templates by default reference a non-existent `@custom` component template for each data stream. diff --git a/docs/en/observability/apm/manage-storage/data-streams.asciidoc b/docs/en/observability/apm/manage-storage/data-streams.asciidoc index 682da3c402..cd9b794561 100644 --- a/docs/en/observability/apm/manage-storage/data-streams.asciidoc +++ b/docs/en/observability/apm/manage-storage/data-streams.asciidoc @@ -82,7 +82,7 @@ Logs are stored in the following data streams: + // tag::logs-data-streams[] - APM error/exception logging: `logs-apm.error-` -- APM app logging: `logs-apm.app.-` +- Applications UI logging: `logs-apm.app.-` // end::logs-data-streams[] [discrete] diff --git a/docs/en/observability/apm/manage-storage/ilm-how-to.asciidoc b/docs/en/observability/apm/manage-storage/ilm-how-to.asciidoc index 12d54c67d1..6da32cf5d4 100644 --- a/docs/en/observability/apm/manage-storage/ilm-how-to.asciidoc +++ b/docs/en/observability/apm/manage-storage/ilm-how-to.asciidoc @@ -65,62 +65,62 @@ Each policy includes a rollover and delete definition: | `metrics-apm.service_destination_1m` | 7 days / 50GB | 90 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.service_destination_10m` | 14 days / 50GB | 180 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.service_destination_60m` | 30 days / 50GB | 390 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.service_summary_1m` | 7 days / 50GB | 90 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.service_summary_10m` | 14 days / 50GB | 180 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.service_summary_60m` | 30 days / 50GB | 390 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.service_transaction_1m` | 7 days / 50GB | 90 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.service_transaction_10m` | 14 days / 50GB | 180 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.service_transaction_60m` | 30 days / 50GB | 390 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.transaction_1m` | 7 days / 50GB | 90 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.transaction_10m` | 14 days / 50GB | 180 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI | `metrics-apm.transaction_60m` | 30 days / 50GB | 390 days -| Aggregated transaction metrics powering the APM UI +| Aggregated transaction metrics powering the Applications UI |=== diff --git a/docs/en/observability/apm/manage-storage/index.asciidoc b/docs/en/observability/apm/manage-storage/index.asciidoc index aa73b774d8..d9701f0389 100644 --- a/docs/en/observability/apm/manage-storage/index.asciidoc +++ b/docs/en/observability/apm/manage-storage/index.asciidoc @@ -10,7 +10,7 @@ The <> attempts to define a "typical and there are additional settings you can tweak to <>, or to <>. -In addition, the APM UI makes it easy to visualize your APM data usage with +In addition, the Applications UI makes it easy to visualize your APM data usage with <>. Storage explorer allows you to analyze the storage footprint of each of your services to see which are producing large amounts of data--so you can better reduce the data you're collecting diff --git a/docs/en/observability/apm/release-notes.asciidoc b/docs/en/observability/apm/release-notes.asciidoc index 5287b1deb0..a73ae3614b 100644 --- a/docs/en/observability/apm/release-notes.asciidoc +++ b/docs/en/observability/apm/release-notes.asciidoc @@ -13,7 +13,7 @@ include::{apm-server-root}/CHANGELOG.asciidoc[tag=list] Looking for a previous version? See the {apm-guide-7x}/release-notes.html[7.x release notes]. -**APM UI** +**Applications UI** See the {kibana-ref}/release-notes.html[Kibana release notes]. diff --git a/docs/en/observability/apm/security/apm-agents/api-keys.asciidoc b/docs/en/observability/apm/security/apm-agents/api-keys.asciidoc index 035cd0c4c7..612efe3bda 100644 --- a/docs/en/observability/apm/security/apm-agents/api-keys.asciidoc +++ b/docs/en/observability/apm/security/apm-agents/api-keys.asciidoc @@ -38,7 +38,7 @@ privileges. The user creating an {apm-agent} API key must have at least the `manage_own_api_key` cluster privilege and the APM application-level privileges that it wishes to grant. -In addition, when creating an API key from the APM UI, +In addition, when creating an API key from the Applications UI, you'll need the appropriate {kib} Space and Feature privileges. The example below uses the {kib} {kibana-ref}/role-management-api.html[role management API] @@ -72,13 +72,13 @@ Assign the newly created `apm_agent_key_role` role to any user that wishes to cr [float] [[apm-create-an-api-key]] -== Create an API key in the APM UI +== Create an API key in the Applications UI -The APM UI has a built-in workflow that you can use to easily create and view {apm-agent} API keys. -Only API keys created in the APM UI will show up here. +The Applications UI has a built-in workflow that you can use to easily create and view {apm-agent} API keys. +Only API keys created in the Applications UI will show up here. Using a superuser account, or a user with the role created in the previous step, -open {kib} and navigate to **{observability}** > **APM** > **Settings** > **Agent keys**. +open {kib} and navigate to **{observability}** → **Applications** → **Settings** → **Agent keys**. Enter a name for your API key and select at least one privilege. For example, to create an API key that can be used to ingest APM events @@ -89,7 +89,7 @@ Click **Create APM Agent key** and copy the Base64 encoded API key. You will need this for the next step, and you will not be able to view it again. [role="screenshot"] -image::images/apm-ui-api-key.png[APM UI API key] +image::images/apm-ui-api-key.png[Applications UI API key] [float] [[apm-agent-api-key]] diff --git a/docs/en/observability/apm/security/data-security/apm-spaces.asciidoc b/docs/en/observability/apm/security/data-security/apm-spaces.asciidoc index 5c4257e3f9..dfd2d3ff73 100644 --- a/docs/en/observability/apm/security/data-security/apm-spaces.asciidoc +++ b/docs/en/observability/apm/security/data-security/apm-spaces.asciidoc @@ -1,7 +1,7 @@ [[apm-spaces]] = Control access to APM data -Starting in version 8.2.0, the APM UI is {kibana-ref}/xpack-spaces.html[Kibana space] aware. +Starting in version 8.2.0, the Applications UI is {kibana-ref}/xpack-spaces.html[Kibana space] aware. This allows you to separate your data--and access to that data--by team, use case, service environment, or any other filter that you choose. @@ -32,7 +32,7 @@ If this field is empty, see <> [float] === Step 1: Create filtered aliases -The APM UI uses index patterns to query your APM data. An index pattern can match data streams, indices, and/or aliases. +The Applications UI uses index patterns to query your APM data. An index pattern can match data streams, indices, and/or aliases. The default values are: [options="header"] @@ -46,7 +46,7 @@ The default values are: NOTE: The default index settings also query the `apm-*` data view. This data view matches APM data shipped in earlier versions of APM (prior to v8.0). -Instead of querying the default APM data views, we can create filtered aliases for the APM UI to query. +Instead of querying the default APM data views, we can create filtered aliases for the Applications UI to query. A filtered alias is a secondary name for a group of data streams that has a user-defined filter to limit the documents that the alias can access. @@ -255,9 +255,9 @@ See {kibana-ref}/xpack-spaces.html[Kibana spaces] for more information on creati [float] === Step 3: Update APM index settings in each space -Now we can change the default data views that the APM UI queries in each space. +Now we can change the default data views that the Applications UI queries in each space. -Open the APM UI and navigate to **Settings** > **Indices**. +Open the Applications UI and navigate to **Settings** → **Indices**. Use the table below to update your settings for each space. The values in each column match the names of the filtered aliases we created in step one. @@ -323,7 +323,7 @@ POST /_security/role/production_apm_viewer } ---- <1> This data view matches all of the production aliases created in step one. -<2> Assigns `read` privileges for the APM and User Experience apps. +<2> Assigns `read` privileges for the Applications and User Experience UIs. <3> Provides access to the space named `production`. ==== @@ -357,7 +357,7 @@ POST /_security/role/staging_apm_viewer } ---- <1> This data view matches all of the staging aliases created in step one. -<2> Assigns `read` privileges for the APM and User Experience apps. +<2> Assigns `read` privileges for the Applications and User Experience UIs. <3> Provides access to the space named `staging`. ==== @@ -408,4 +408,4 @@ POST /_security/user/staging-apm-user [float] === Step 6: Marvel -That's it! Head back to the APM UI and marvel at your space-specific data. +That's it! Head back to the Applications UI and marvel at your space-specific data. diff --git a/docs/en/observability/apm/security/elastic-stack/feature-roles.asciidoc b/docs/en/observability/apm/security/elastic-stack/feature-roles.asciidoc index 1e33fac6b1..d2571e3d57 100644 --- a/docs/en/observability/apm/security/elastic-stack/feature-roles.asciidoc +++ b/docs/en/observability/apm/security/elastic-stack/feature-roles.asciidoc @@ -108,12 +108,12 @@ _Central configuration management role_, which is <> is enabled (it is enabled by default). You need this role unless central configuration management has been explicitly disabled in the APM UI. +The privileges included in this role are *required* for all users when <> is enabled (it is enabled by default). You need this role unless central configuration management has been explicitly disabled in the Applications UI. ==== [[apm-privileges-agent-central-config-server]] -APM Server acts as a proxy between your APM agents and the APM UI. -The APM UI communicates any changed settings to APM Server so that your agents only need to poll the Server +APM Server acts as a proxy between your APM agents and the Applications UI. +The Applications UI communicates any changed settings to APM Server so that your agents only need to poll the Server to determine which central configuration settings have changed. To create a role with the required privileges for managing central configuration in {es} without {kib}, @@ -144,8 +144,8 @@ which requires the following privileges: |Type | Privilege | Purpose | Spaces -|`Read` on APM UI -|Allow APM Server to manage central configurations via the APM UI +|`Read` on Applications UI +|Allow APM Server to manage central configurations via the Applications UI |==== [NOTE] @@ -154,8 +154,8 @@ Assign <> to users as needed inc _Writer role_, which is <>. ==== -TIP: Looking for privileges and roles needed to use central configuration from the APM UI or APM UI API? -See <>. +TIP: Looking for privileges and roles needed to use central configuration from the Applications UI or APM UI API? +See <>. //// *********************************** *********************************** diff --git a/docs/en/observability/apm/security/index.asciidoc b/docs/en/observability/apm/security/index.asciidoc index 02ab702328..efdb1bf1fd 100644 --- a/docs/en/observability/apm/security/index.asciidoc +++ b/docs/en/observability/apm/security/index.asciidoc @@ -29,8 +29,8 @@ You should approach securing your application data from different perspectives: Read more in <>. -| *Who can use the APM UI?* -| Use role-based access control to grant users access to features of the APM UI. +| *Who can use the Applications UI?* +| Use role-based access control to grant users access to features of the Applications UI. Read more in <>. |=== diff --git a/docs/en/observability/apm/security/user-access/annotation.asciidoc b/docs/en/observability/apm/security/user-access/annotation.asciidoc index 888759bd98..a7a2bd8a8c 100644 --- a/docs/en/observability/apm/security/user-access/annotation.asciidoc +++ b/docs/en/observability/apm/security/user-access/annotation.asciidoc @@ -1,5 +1,5 @@ [[apm-app-annotation-user-create]] -= APM UI annotation user += Applications UI annotation user ++++ Create an annotation user @@ -13,7 +13,7 @@ You only need to create an annotation user to write to the annotations index [[apm-app-annotation-user]] == Annotation user -View deployment annotations in the APM UI. +View deployment annotations in the Applications UI. . Create a new role, named something like `annotation_user`, and assign the following privileges: @@ -35,7 +35,7 @@ and assign the following privileges: {kibana-ref}/apm-settings-kb.html[`xpack.observability.annotations.index`]. . Assign the `annotation_user` created previously, and the roles and privileges necessary to create -a <> or <> APM reader to any users that need to view annotations in the APM UI +a <> or <> APM reader to any users that need to view annotations in the Applications UI [float] [[apm-app-annotation-api]] diff --git a/docs/en/observability/apm/security/user-access/api-ui.asciidoc b/docs/en/observability/apm/security/user-access/api-ui.asciidoc index 7322aa39e4..380997a288 100644 --- a/docs/en/observability/apm/security/user-access/api-ui.asciidoc +++ b/docs/en/observability/apm/security/user-access/api-ui.asciidoc @@ -1,5 +1,5 @@ [[apm-app-api-user]] -= APM UI API user += Applications UI API user ++++ Create an API user @@ -9,7 +9,7 @@ [[apm-app-api-config-manager]] == Central configuration API -Users can list, search, create, update, and delete central configurations via the APM UI API. +Users can list, search, create, update, and delete central configurations via the Applications UI API. . Assign the following Kibana feature privileges: + @@ -19,14 +19,14 @@ Users can list, search, create, update, and delete central configurations via th | Kibana |`all` on the APM and User Experience feature -|Allow all access to the APM and User Experience apps +|Allow all access to the Applications and User Experience UIs |==== [float] [[apm-app-api-config-reader]] == Central configuration API reader -Sometimes a user only needs to list and search central configurations via the APM UI API. +Sometimes a user only needs to list and search central configurations via the Applications UI API. . Assign the following Kibana feature privileges: + @@ -36,7 +36,7 @@ Sometimes a user only needs to list and search central configurations via the AP | Kibana |`read` on the APM and User Experience feature -|Allow read access to the APM and User Experience apps +|Allow read access to the Applications and User Experience UIs |==== [float] @@ -78,5 +78,5 @@ and the following Kibana feature privileges to any annotation API users: | Kibana |`all` on the APM and User Experience feature -|Allow all access to the APM and User Experience apps +|Allow all access to the Applications and User Experience UIs |==== \ No newline at end of file diff --git a/docs/en/observability/apm/security/user-access/central-config.asciidoc b/docs/en/observability/apm/security/user-access/central-config.asciidoc index 59e189901a..4b9745eaac 100644 --- a/docs/en/observability/apm/security/user-access/central-config.asciidoc +++ b/docs/en/observability/apm/security/user-access/central-config.asciidoc @@ -1,5 +1,5 @@ [[apm-app-central-config-user]] -= APM UI central config user += Applications UI central config user ++++ Create a central config user @@ -29,7 +29,7 @@ and the following Kibana feature privileges to anyone who needs to manage centra | Kibana |`All` on the APM and User Experience feature -|Allow full use of the APM and User Experience apps +|Allow full use of the Applications and User Experience UIs |==== [float] @@ -57,7 +57,7 @@ and the following Kibana feature privileges to anyone who needs to read central | Kibana |`read` on the APM and User Experience feature -|Allow read access to the APM and User Experience apps +|Allow read access to the Applications and User Experience UIs |==== [float] diff --git a/docs/en/observability/apm/security/user-access/index.asciidoc b/docs/en/observability/apm/security/user-access/index.asciidoc index 4011f17066..2dd5c5e700 100644 --- a/docs/en/observability/apm/security/user-access/index.asciidoc +++ b/docs/en/observability/apm/security/user-access/index.asciidoc @@ -1,11 +1,11 @@ [[apm-app-users]] -= Secure access to the APM UI += Secure access to the Applications UI :beat_default_index_prefix: apm :annotation_index: observability-annotations ++++ -Secure access to the APM UI +Secure access to the Applications UI ++++ Use role-based access control to grant users access to secured diff --git a/docs/en/observability/apm/security/user-access/reader.asciidoc b/docs/en/observability/apm/security/user-access/reader.asciidoc index f342e277eb..f62c7cc976 100644 --- a/docs/en/observability/apm/security/user-access/reader.asciidoc +++ b/docs/en/observability/apm/security/user-access/reader.asciidoc @@ -5,7 +5,7 @@ Create an APM reader user ++++ -APM reader users typically need to view the APM UI and dashboards and visualizations that use APM data. +APM reader users typically need to view the Applications UI and dashboards and visualizations that use APM data. These users might also need to create and edit dashboards, visualizations, and machine learning jobs. [float] @@ -59,7 +59,7 @@ Here are two examples: | Kibana | `Read` or `All` on the APM and User Experience feature -| Allow the use of the the APM and User Experience apps +| Allow the use of the the Applications and User Experience UIs | Kibana | `Read` or `All` on Dashboards and Discover diff --git a/docs/en/observability/apm/security/user-access/storage-explorer.asciidoc b/docs/en/observability/apm/security/user-access/storage-explorer.asciidoc index 429fb7fe78..2a426c3af6 100644 --- a/docs/en/observability/apm/security/user-access/storage-explorer.asciidoc +++ b/docs/en/observability/apm/security/user-access/storage-explorer.asciidoc @@ -1,5 +1,5 @@ [[apm-app-storage-explorer-user-create]] -= APM UI storage explorer user += Applications UI storage explorer user ++++ Create a storage explorer user @@ -9,7 +9,7 @@ [[apm-app-storage-explorer-user]] == Storage Explorer user -View the **Storage Explorer** in the APM UI. +View the **Storage Explorer** in the Applications UI. . Create a new role, named something like `storage-explorer_user`, and assign the following privileges: @@ -19,4 +19,4 @@ include::{observability-docs-root}/docs/en/observability/apm/tab-widgets/storage -- . Assign the `storage-explorer_user` created previously, and the roles and privileges necessary to create -a <> or <> APM reader to any users that need to view **Storage Explorer** in the APM UI. \ No newline at end of file +a <> or <> APM reader to any users that need to view **Storage Explorer** in the Applications UI. \ No newline at end of file diff --git a/docs/en/observability/apm/tab-widgets/apm-app-reader/widget.asciidoc b/docs/en/observability/apm/tab-widgets/apm-app-reader/widget.asciidoc index bdffa20980..e15d50ae47 100644 --- a/docs/en/observability/apm/tab-widgets/apm-app-reader/widget.asciidoc +++ b/docs/en/observability/apm/tab-widgets/apm-app-reader/widget.asciidoc @@ -1,6 +1,6 @@ ++++
-
+