Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.x] docs: update apm ds naming scheme (#946) #948

Merged
merged 1 commit into from
Aug 2, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions docs/en/ingest-management/data-streams.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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`),
Expand All @@ -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,
Expand Down