Re: [heka] GeoIPdecoder with nginx access logs

2015-03-06 Thread Mike Gibson
In order for Heka to include the GeoIpDecoder code into it's build, you will need to compile heka yourself on a system that has MaxMind's geoip-api-c libraries installed: https://github.com/maxmind/geoip-api-c/releases/ What I have in production is slightly different so I haven't tested this but h

Re: [heka] help with a config

2016-08-02 Thread Mike Gibson
Hi Wayne, The LogstreamerInput looks like it "could" be ok. Does your access.log rotate? If so you may need a to set the "priority". For debugging purposes you can try replacing your ES output with: [RstEncoder] [LogOutput]message_matcher = "TRUE"encoder = "RstEncoder" http://hekad.readthedocs.i

Re: [heka] Heka input differentiator fields to decoder

2016-08-05 Thread Mike Gibson
Hi Satish, You may be able to achieve what you are asking by using the ScribbleDecoder. http://hekad.readthedocs.io/en/latest/config/decoders/scribble.html In combination with your SomethingLogDecoder both within a MultiDecoder. i.e. [SomethingLogInput] type = "LogstreamerInput" log_dir

Re: [heka] How to inject logging in lua code

2016-08-09 Thread Mike Gibson
I've included something like this before in my lua code using pcall. It injects a new payload with the error or logs to stdout(commented out). Uncomment return value to either exit or continue on depending on your preference. local ok, err = pcall(inject_message, msg)

[heka] New plugins

2016-09-06 Thread Mike Gibson
Hello existing Heka users. I'm aware of the "DEPRECATED" status of the project but I'm still not prepared to abandon using Heka just yet. I just can't seem to find another tool out there with the equivalent number of I/O plugins, performance(hasn't been an issue for my scale) and flexibility. In th

Re: [heka] New plugins

2016-09-07 Thread Mike Gibson
, 2016 at 11:52 PM, Mathieu Parent wrote: > 2016-09-06 22:03 GMT+02:00 Mike Gibson : > > Hello existing Heka users. > > Hello, > > > > I'm aware of the "DEPRECATED" status of the project but I'm still not > > prepared to abandon using Heka just

Re: [heka] New Heka release?

2016-09-20 Thread Mike Gibson
I'm happy to help however needed. We are still using Heka for the foreseeable future. On Mon, Sep 19, 2016 at 1:23 PM, Rob Miller wrote: > Yes, there's been a lot of work done on the dev branch. There's been even > more work done on a separate branch, merging in the newer sandbox code and > putt