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

Update ingest pipeline docs with new integrations pattern naming #863

Merged
merged 1 commit into from
Feb 6, 2024
Merged

Update ingest pipeline docs with new integrations pattern naming #863

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 6 additions & 3 deletions docs/en/ingest-management/data-streams.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -223,14 +223,14 @@ PUT _ingest/pipeline/logs@custom
}
----

`${type}-${package}`::
`${type}-${package}.integration`::
Apply processing to all events of a given type in an integration
+
For example, the following request creates a `logs-nginx@custom` pipeline that adds a new field `my-nginx-field` for all log events in the Nginx integration:
For example, the following request creates a `logs-nginx.integration@custom` pipeline that adds a new field `my-nginx-field` for all log events in the Nginx integration:
+
[source,console]
----
PUT _ingest/pipeline/logs-nginx@custom
PUT _ingest/pipeline/logs-nginx.integration@custom
{
"processors": [
{
Expand All @@ -243,6 +243,9 @@ PUT _ingest/pipeline/logs-nginx@custom
]
}
----
+
Note that `.integration` is included in the pipeline pattern to avoid possible collision with existing dataset pipelines.


`${type}-${dataset}`::
Apply processing to a specific dataset.
Expand Down