Date: Tue, 19 Dec 2017 14:14:45 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 224455] [NEW PORT] sysutils/grok_exporter: Export Prometheus metrics from arbitrary unstructured log data Message-ID: <bug-224455-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224455 Bug ID: 224455 Summary: [NEW PORT] sysutils/grok_exporter: Export Prometheus metrics from arbitrary unstructured log data Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: gasol.wu@gmail.com Created attachment 188960 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D188960&action= =3Dedit shar file Grok is a tool to parse crappy unstructured log data into something structu= red and queryable. Grok is heavily used in Logstash to provide log data as input for ElasticSearch. Grok ships with about 120 predefined patterns for syslog logs, apache and o= ther webserver logs, mysql logs, etc. It is easy to extend Grok with custom patterns. The grok_exporter aims at porting Grok from the ELK stack to Prometheus monitoring. The goal is to use Grok patterns for extracting Prometheus metr= ics from arbitrary log files. WWW: https://github.com/fstab/grok_exporter --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224455-13>