@@ -229,10 +229,26 @@ running configuration for a container, 60s by default.
229229 either take `node` or `cluster` as values. `node` scope allows discovery of resources in
230230 the specified node. `cluster` scope allows cluster wide discovery. Only `pod` and `node` resources
231231 can be discovered at node scope.
232+ `add_resource_metadata`:: (Optional) Specify labels and annotations filters for the extra metadata coming from Node and Namespace.
233+ `add_resource_metadata` can be done for `node` or `namespace`. By default all labels will be included
234+ while annotations are not added by default. This settings are useful when labels' and annotations'
235+ storing requires special handling to avoid overloading the storage output.
236+ Example:
237+
238+ ["source","yaml",subs="attributes"]
239+ -------------------------------------------------------------------------------------
240+ add_resource_metadata:
241+ namespace:
242+ include_labels: ["namespacelabel1"]
243+ node:
244+ include_labels: ["nodelabel2"]
245+ include_annotations: ["nodeannotation1"]
246+ -------------------------------------------------------------------------------------
247+
232248`unique`:: (Optional) Defaults to `false`. Marking an autodiscover provider as unique results into
233249 making the provider to enable the provided templates only when it will gain the leader lease.
234250 This setting can only be combined with `cluster` scope. When `unique` is enabled enabled, `resource`
235- setting is not taken into account.
251+ and `add_resource_metadata` settings are not taken into account.
236252`leader_lease`:: (Optional) Defaults to `{beatname_lc}-cluster-leader`. This will be name of the lock lease.
237253 One can monitor the status of the lease with `kubectl describe lease beats-cluster-leader`.
238254 Different Beats that refer to the same leader lease will be competetitors in holding the lease
0 commit comments