Skip to content

doc: update filebeat dissect processor field tokenization example #29680

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

Merged
merged 1 commit into from
Jan 18, 2022
Merged

doc: update filebeat dissect processor field tokenization example #29680

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
6 changes: 3 additions & 3 deletions libbeat/processors/dissect/docs/dissect.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,14 +74,14 @@ For this example, imagine that an application generates the following messages:
"789 - App02 - Database is refreshing tables"
----

Use the `dissect` processor to split each message into two fields, for example,
Use the `dissect` processor to split each message into three fields, for example, `service.pid`,
`service.name` and `service.status`:

[source,yaml]
----
processors:
- dissect:
tokenizer: '"%{pid|integer} - %{service.name} - %{service.status}"'
tokenizer: '"%{service.pid|integer} - %{service.name} - %{service.status}"'
field: "message"
target_prefix: ""
----
Expand All @@ -98,7 +98,7 @@ This configuration produces fields like:
----

`service.name` is an ECS {ref}/keyword.html[keyword field], which means that you
can use it in {es} for filtering, sorting, and aggregations.
can use it in {es} for filtering, sorting, and aggregations.

When possible, use ECS-compatible field names. For more information, see the
{ecs-ref}/index.html[Elastic Common Schema] documentation.