From a33e193f0e1a9a5d9e62d2b2cac5d6fccae522ff Mon Sep 17 00:00:00 2001 From: Brandon Morelli Date: Mon, 2 Aug 2021 14:07:20 -0700 Subject: [PATCH] docs: update apm ds naming scheme (#946) --- docs/en/ingest-management/data-streams.asciidoc | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/en/ingest-management/data-streams.asciidoc b/docs/en/ingest-management/data-streams.asciidoc index cceb2cc3ed..ef51546ac6 100644 --- a/docs/en/ingest-management/data-streams.asciidoc +++ b/docs/en/ingest-management/data-streams.asciidoc @@ -34,8 +34,6 @@ A generic `type` describing the data, such as `logs`, `metrics`, `traces`, or `s The `dataset` is defined by the integration and describes the ingested data and its structure for each index. For example, you might have a dataset for process metrics with a field describing whether the process is running or not, and another dataset for disk I/O metrics with a field describing the number of bytes read. -+ -For APM data, the `dataset` is the instrumented service's `service.name`. `namespace`:: A user-configurable arbitrary grouping, such as an environment (`dev`, `prod`, or `qa`), @@ -59,12 +57,12 @@ For example, if you've set up the Nginx integration with a namespace of `prod`, logs-nginx.access-prod -- -Alternatively, if you use the APM integration with a namespace of `dev`, and a `service.name` of `frontend`, +Alternatively, if you use the APM integration with a namespace of `dev`, {agent} stores data in the following data stream: [source,text] -- -traces-apm.frontend-dev +traces-apm-dev -- All data streams, and the pre-built dashboards that they ship with,