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

The elastic-agent-autodiscover library is updated to version 0.6.4, disabling metadata for deployment and cronjob #38571

Open
wants to merge 2 commits into
base: 8.12
Choose a base branch
from
Open

The elastic-agent-autodiscover library is updated to version 0.6.4, disabling metadata for deployment and cronjob #38571

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ee33c8e
Update shared-autodiscover.asciidoc
asmith-elastic Mar 22, 2024
0bb9470
Merge branch '8.12' into asmith-elastic-patch-autodiscover
rdner Apr 24, 2024
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 libbeat/docs/shared-autodiscover.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,8 +178,8 @@ Configuration parameters:
* `node` or `namespace`: Specify labels and annotations filters for the extra metadata coming from node and namespace. By default all labels are included while annotations are not. To change default behaviour `include_labels`, `exclude_labels` and `include_annotations` can be defined. Those settings are useful when storing labels and annotations that require special handling to avoid overloading the storage output.
Note: wildcards are not supported for those settings.
The enrichment of `node` or `namespace` metadata can be individually disabled by setting `enabled: false`.
* `deployment`: If resource is `pod` and it is created from a `deployment`, by default the deployment name is added, this can be disabled by setting `deployment: false`.
* `cronjob`: If resource is `pod` and it is created from a `cronjob`, by default the cronjob name is added, this can be disabled by setting `cronjob: false`.
* `deployment`: If resource is `pod` and it is created from a `deployment`, by default the deployment name is not added, this can be enabled by setting `deployment: true`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* `deployment`: If resource is `pod` and it is created from a `deployment`, by default the deployment name is not added, this can be enabled by setting `deployment: true`.
* `deployment`: If resource is `pod` and it is created from a `deployment`. By default the deployment name is not added, this can be enabled by setting `deployment: true`.

* `cronjob`: If resource is `pod` and it is created from a `cronjob`, by default the cronjob name is not added, this can be enabled by setting `cronjob: true`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* `cronjob`: If resource is `pod` and it is created from a `cronjob`, by default the cronjob name is not added, this can be enabled by setting `cronjob: true`.
* `cronjob`: If resource is `pod` and it is created from a `cronjob`. By default the cronjob name is not added, this can be enabled by setting `cronjob: true`.

+
Example:
["source","yaml",subs="attributes"]
Expand Down
Loading