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.

Sign up for GitHub

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

docs: Remove references to rollovers where a rollover is not required #12112

Merged
merged 3 commits into from
Nov 30, 2023
+0 −13
Merged

docs: Remove references to rollovers where a rollover is not required #12112

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6a66708
remove unnecessary references to rollovers
colleenmcginnis Nov 27, 2023
346d8f8
Merge branch 'main' into issue-11593
colleenmcginnis Nov 29, 2023
0b7ed0f
Merge branch 'main' into issue-11593
simitt Nov 30, 2023
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
12 changes: 0 additions & 12 deletions docs/apm-data-security.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -483,18 +483,6 @@ TIP: If you prefer using a GUI, you can instead open {kib} and navigate to
**Stack Management** -> **Ingest Pipelines** -> **Create pipeline**.
Use the same naming convention explained previously to ensure your new pipeline matches the correct APM data stream.

**Roll over the data stream (optional)**

Pipeline changes are not applied retroactively to existing indices.
For changes to take effect immediately, you must create a new write index for the data stream.
This can be done with the {es} {ref}/indices-rollover-index.html[Rollover API].
For example, to roll over the default application traces data stream, with a `namespace` of "default", run:

[source,console]
----
POST /traces-apm-default/_rollover/
----

That's it! Passwords will now be redacted from your APM HTTP body data.

To learn more about ingest pipelines, see <<custom-index-template>>.
Expand Down
1 change: 0 additions & 1 deletion docs/ingest-pipelines.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,6 @@ The process for creating a custom ingest pipeline is as follows:

* Create a pipeline with processors specific to your use case
* Add the newly created pipeline to an `@custom` pipeline that matches an APM data stream
* Roll over your data stream

If you prefer more guidance, see one of these tutorials:

Expand Down