-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add reference documentation about indexers and matchers #17139
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
14 changes: 14 additions & 0 deletions
14
filebeat/docs/kubernetes-default-indexers-matchers.asciidoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
When `add_kubernetes_metadata` is used with {beatname_uc}, it uses the | ||
`container` indexer and the `logs_path`. So events whose path in `log.file.path` | ||
contains a reference to a container ID are enriched with metadata of the pod of | ||
this container. | ||
|
||
This behaviour can be disabled disabling default indexers and matchers in the | ||
configuration: | ||
[source,yaml] | ||
------------------------------------------------------------------------------- | ||
processors: | ||
- add_kubernetes_metadata: | ||
default_indexers.enabled: false | ||
default_matchers.enabled: false | ||
------------------------------------------------------------------------------- |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
14 changes: 14 additions & 0 deletions
14
metricbeat/docs/kubernetes-default-indexers-matchers.asciidoc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,14 @@ | ||||||
When `add_kubernetes_metadata` is used with {beatname_uc}, it uses the `ip_port` | ||||||
indexer and the `fields` matcher with the `metricset.host` field. So events that | ||||||
contain a `metricset.host` field are enriched with metadata of the pods that | ||||||
exposes the same port in the same IP. | ||||||
|
||||||
This behaviour can be disabled disabling default indexers and matchers in the | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. minor but maybe a
Suggested change
|
||||||
configuration: | ||||||
[source,yaml] | ||||||
------------------------------------------------------------------------------- | ||||||
processors: | ||||||
- add_kubernetes_metadata: | ||||||
default_indexers.enabled: false | ||||||
default_matchers.enabled: false | ||||||
------------------------------------------------------------------------------- |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor but maybe a
by
is needed here:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better, yes, thanks!