[mq] working branch - merge de561ca on top of master at 34592a9

{"baseBranch":"master","baseCommit":"34592a9317e8d595362615f2f2a35b5c919e9afd","createdAt":"2025-05-16T19:10:41.695137Z","headSha":"de561ca7f75b1a4afcde08b4e5651fc99064ba5a","id":"51d9c61b-3956-492a-bf98-fd39e171d30c","priority":"200","pullRequestNumber":"29052","queuedAt":"2025-05-16T19:10:41.694232Z","status":"STATUS_QUEUED"}

Author: dd-mergequeue[bot]

content/en/containers/guide/container-discovery-management.md

@@ -33,7 +33,16 @@ You can set exceptions in two ways:
 
 ## Agent configuration
 
-Use the environment variables in the table below to configure container filtering. Each inclusion or exclusion is defined as a list of space-separated regex strings. You can include or exclude containers based on their container name (`name`), image name (`image`), or Kubernetes namespace (`kube_namespace`).
+Use the environment variables in the table below to configure container filtering. Each inclusion or exclusion is defined as a list of space-separated regex strings. You can include or exclude containers based on their:
+- container name (`name`)
+- container image name (`image`)
+- Kubernetes namespace (`kube_namespace`)
+
+<div class="alert alert-warning">
+
+The `name` parameter only applies to container names, not pod names, even if the container runs in a Kubernetes pod.
+
+</div>
 
 ### Environment variables
 In **Agent v7.20+**, use the following environment variables to exclude containers by image name, container name, or Kubernetes namespace. Logs and metrics are not collected from excluded containers.