New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dev.icinga.com #11436] Add LogstashWriter for Logstash in addition to GelfWriter #4054
Comments
Updated by mfriedrich on 2016-03-22 20:31:33 +00:00
|
Updated by mfriedrich on 2016-03-22 20:31:33 +00:00 Part of Kai's internship. |
Updated by mfriedrich on 2016-03-24 10:46:13 +00:00
Hi Kai, this will be part of your project in the next months. We will discuss it further then. Kind regards, |
Updated by kowalskimn on 2016-03-24 16:23:30 +00:00 widhalmt wrote:
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-03-29 15:08:33 +00:00 Thanks, that will also be part of Kai's task to evaluate whether the existing GELF specification works with Logstash or if a different format specification is required. |
Updated by mfriedrich on 2016-03-29 15:09:09 +00:00
|
Updated by mfriedrich on 2016-04-18 11:46:34 +00:00 Logstash GELF Inputhttps://github.com/logstash-plugins/logstash-input-gelf/blob/master/lib/logstash/inputs/gelf.rb
|
Updated by mfriedrich on 2016-09-28 13:49:04 +00:00
|
Updated by mfriedrich on 2016-11-09 15:11:53 +00:00
|
Updated by mfriedrich on 2016-11-09 15:13:30 +00:00
|
Code was not in a good shape, and at least the performance data part is still incomplete. TestsUse the
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. DiscussionI'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. |
This adds the UdpSocket class. refs #4054
This adds the UdpSocket class. refs #4054
@dnsmichi Any update about this? |
Still on my TODO list. Mainly tests and docs are missing. |
This adds the UdpSocket class. refs #4054
This includes Logstash and Icinga 2 configuration. refs #4054
Add LogstashWriter feature fixes #4054
I'm postponing this feature until there is a general decision about an ElasticWriter feature. There's a possible sponsor for that. |
Revert LogstashWriter feature refs #4054
@dnsmichi Just wondering if anything's changed.. |
There are plans to introduce a generic ElasticWriter, sponsored by a customer. Nothing new in this issue though. |
Ok, thank you for the quick response. Was just wondering since I couldn't find anything under ElasticWriter. |
We'll create an issue once the spec and assigned devs are clarified. |
Closing this in favor of #5538. |
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
Assignee: mfriedrich
Status: Assigned
Target Version: 2.7.0
Last Update: 2016-11-09 15:11:53 +00:00 (in Redmine)
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?
Changesets
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
Relations:
The text was updated successfully, but these errors were encountered: