Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
[dev.icinga.com #11436] Add LogstashWriter for Logstash in addition to GelfWriter #4054
This issue has been migrated from Redmine: https://dev.icinga.com/issues/11436
Created by twidhalm on 2016-03-22 15:49:55 +00:00
The GELF protocol can use UDP or TCP according to the documentation.
Since some GELF receivers (like Logstash) can only receive UDP and the Icinga 2 GELF writer can only send TCP we have the situation that 2 tools talking the same protocol still can't talk to each other.
Could you add a protocol switcher to the GELF writer object?
2016-06-15 13:21:28 +00:00 by kgoller 8ad95bd
2016-06-15 13:27:26 +00:00 by kgoller ce7a23c
2016-07-06 11:51:59 +00:00 by kgoller cd785ae
2016-07-06 12:07:15 +00:00 by kgoller 50e4c35
2016-07-11 19:03:41 +00:00 by kgoller ea5aadf
2016-07-14 07:21:20 +00:00 by kgoller 1db4852
Updated by kowalskimn on 2016-03-24 16:23:30 +00:00
I can already tell you it won't be enough to get logstash working.
There is a plugin for logstash that grabs gelf over tcp, and it's having issues with format of various fields. Not sure if that's for logstash or icinga2 to fix.
Updated by mfriedrich on 2016-04-18 11:46:34 +00:00
Logstash GELF Input
Code was not in a good shape, and at least the performance data part is still incomplete.
Configure the input and output.
Then point Icinga 2 to it inside
Note: The logstash input port is freely assignable, there is no sane default.
I'm not entirely convinced if the udp input makes sense since both logstash and elasticsearch provide a HTTP API. Elastic beats are providing output methods for both interfaces, so they probably do not differ that much.
The JSON blob is entirely written to Logstash, so you'll need to use the json codec on your own if your prefer just that.