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.

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

Mark add_docker-metadata process as unsupported in packetbeat #39241

Merged
merged 3 commits into from Apr 29, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -5,6 +5,11 @@
<titleabbrev>add_docker_metadata</titleabbrev>
++++

ifeval::["{beatname_lc}"=="packetbeat"]
There is currently extremely limited capability for using {beatname_lc} to monitor and coexist with containers, for example Docker, Podman, or Kubernetes). Using the `add_docker_metadata` processor with {beatname_lc} is not recommended nor supported.
kilfoyle marked this conversation as resolved.
Show resolved Hide resolved
endif::[]

ifeval::["{beatname_lc}"!="packetbeat"]
The `add_docker_metadata` processor annotates each event with relevant metadata
from Docker containers. At startup it detects a docker environment and caches the metadata.
The events are annotated with Docker metadata, only if a valid configuration
Expand Down Expand Up @@ -88,3 +93,4 @@ forget metadata for a container, 60s by default.

`labels.dedot`:: (Optional) Default to be false. If set to true, replace dots in
labels with `_`.
endif::[]