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

Fix processor autodiscovery docs for Filebeat #7937

Merged
merged 2 commits into from
Aug 15, 2018
Merged

Fix processor autodiscovery docs for Filebeat #7937

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0608471
Fix processor autodiscovery docs for Filebeat
ruflin Aug 10, 2018
e0d9d2b
modify according to review
ruflin Aug 14, 2018
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
4 changes: 2 additions & 2 deletions filebeat/docs/autodiscover-hints.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,8 +75,8 @@ arbitrary ordering:

["source","yaml",subs="attributes"]
-------------------------------------------------------------------------------------
co.elastic.logs/processors.1.dissect.tokenizer: "%{key1} %{key2}"
co.elastic.logs/processors.dissect.tokenizer: "%{key2} %{key1}"
co.elastic.logs/processors.1.dissect.tokenizer: "%\{key1} %\{key2}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Escaping works, but you can avoid the need to escape completely by telling asciidoc to treat the whole code block as text. There aren't any asciidoc attributes in this example, so there is no need to usesubs="attributes".

[source,yaml]
-------------------------------------------------------------------------------------
co.elastic.logs/processors.1.dissect.tokenizer: "%{key1} %{key2}"
co.elastic.logs/processors.dissect.tokenizer: "%{key2} %{key1}"
-------------------------------------------------------------------------------------

co.elastic.logs/processors.dissect.tokenizer: "%\{key2} %\{key1}"
-------------------------------------------------------------------------------------

In the above sample the processor definition tagged with `1` would be executed first.
Expand Down