I’m considering a switch from Logstash to Heka for all of my log ingestion needs. I like what I’m seeing, but I’m concerned about validating and maintaining my heka configs. Logstash has a really nice test runner that allows me to write very focused tests against pieces of my config. I don’t see such a facility in Heka and it’s making me reluctant to switch. For example, with Logstash, I’m able to write a test that ensures that an event with a particular message and type is properly fed through the appropriate filters and rewritten or modified into a form suitable for indexing in Elasticsearch. That may be grokking something from syslog or adding geoip metadata to an http access log entry.
Have folks tackled this yet? -- Brian Lalor [email protected] _______________________________________________ Heka mailing list [email protected] https://mail.mozilla.org/listinfo/heka
