The endpoint should have metrics formatted in one of the supported
input data formats.
Each data format has its own unique set of configuration options which can be added to the input configuration.
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
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 HTTP input plugin collects metrics from one or more HTTP(S) endpoints.