By default, the tail plugin acts like the following unix tail command:
tail -F --lines=0 myfile.log
-F means that it will follow the name of the given file, so
that it will be compatible with log-rotated files, and that it will retry on
inaccessible files.
--lines=0 means that it will start at the end of the file (unless
the from_beginning option is set).
see http://man7.org/linux/man-pages/man1/tail.1.html for more details.
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
Each data format has its own unique set of configuration options, read more about them here:
https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
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 tail plugin "tails" a logfile and parses each log message.