Fields with a field key matching one of the patterns will be discarded from the metric.
This is tested on metrics after they have passed the fieldpass test.
Only tags with a tag key matching one of the patterns are emitted.
In contrast to tagpass, which will pass an entire metric based on its tag,
taginclude removes all non matching tags from the metric.
Any tag can be filtered including global tags and the agent host tag.
Tags with a tag key matching one of the patterns will be discarded from the metric.
Any tag can be filtered including global tags and the agent host tag
Collect Swarm metrics (desired_replicas, running_replicas)
Note: Configure this for one of the manager nodes in a Swarm cluster only
as you will see duplicate metrics otherwise.
Podman compatibility settings (auto-enabled when Podman detected). Cache
TTL for accurate CPU percentage calculation. Should be higher than your
collection interval for accurate measurements. Zero will keep cache entries
forever (not recommended for dynamic environments).
Returns the relative, descendent directory path between this module and other.
Throws if no such path exists.
For example, if module mod1 has path /dir1/mod1.pkl, and module mod2 has path
/dir1/dir2/dir3/mod2.pkl, then mod1.relativePathTo(mod2) will return
List("dir2", "dir3").
A common use case is to compute the directory path between a template located at the root of a
hierarchy (say rootModule.pkl) and the currently evaluated module (accessible via the
module keyword):
The Docker input plugin uses the Docker Engine API to gather metrics on running Docker containers.