NAME
logster - generate metrics from logfiles
SYNOPSIS
logster [options] parser logfile
DESCRIPTION
Tail a log file and filter each line to generate metrics that can be sent to common monitoring packages.
OPTIONS
- -h, --help
-
show this help message and exit
- --logtail=LOGTAIL
-
Specify location of logtail. Default /usr/sbin/logtail2
- -p METRIC_PREFIX, --metric-prefix=METRIC_PREFIX
-
Add prefix to all published metrics. This is for people that may multiple instances of same service on same host.
- -x METRIC_SUFFIX, --metric-suffix=METRIC_SUFFIX
-
Add suffix to all published metrics. This is for people that may add suffix at the end of their metrics.
- --parser-help
-
Print usage and options for the selected parser
- --parser-options=PARSER_OPTIONS
-
Options to pass to the logster parser such as "-o VALUE --option2 VALUE". These are parser-specific and passed directly to the parser.
- --gmetric-options=GMETRIC_OPTIONS
-
Options to pass to gmetric such as "-d 180 -c /etc/ganglia/gmond.conf" (default). These are passed directly to gmetric.
- --graphite-host=GRAPHITE_HOST
-
Hostname and port for Graphite collector, e.g. graphite.example.com:2003
- -s STATE_DIR, --state-dir=STATE_DIR
-
Where to store the logtail state file. Default location /var/run
- -o OUTPUT, --output=OUTPUT
-
Where to send metrics (can specify multiple times). Choices are 'graphite', 'ganglia', or 'stdout'.
- -d, --dry-run
-
Parse the log file but send stats to standard output.
- -D, --debug
-
Provide more verbose logging for debugging.
SEE ALSO
logtail(1)
AUTHOR
logster was written by Etsy, Inc.
This manual page was written by Andreas Rütten <[email protected]>, for the Debian project (and may be used by others).