[GH-ISSUE #62] rsyslog module #48

Closed
opened 2026-02-26 05:31:09 +03:00 by kerem · 1 comment
Owner

Originally created by @marklr on GitHub (Apr 3, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/62

It would be awesome if harvesters could be fed directly from rsyslog. We have partially centralized logging and running harvesters on 50+ machines would be problematic.

Originally created by @marklr on GitHub (Apr 3, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/62 It would be awesome if harvesters could be fed directly from rsyslog. We have partially centralized logging and running harvesters on 50+ machines would be problematic.
kerem closed this issue 2026-02-26 05:31:09 +03:00
Author
Owner

@msmathers commented on GitHub (Aug 1, 2014):

This is possible using log.io's TCP API, however we've never implemented an rsyslog adaptor. We did write a logstash output plugin, however:

github.com/msmathers/logstash@b14a6c51ba/lib/logstash/outputs/logio.rb

<!-- gh-comment-id:50855590 --> @msmathers commented on GitHub (Aug 1, 2014): This is possible using log.io's TCP API, however we've never implemented an rsyslog adaptor. We did write a logstash output plugin, however: https://github.com/msmathers/logstash/blob/b14a6c51ba56902c8aad76073ccbf13ef708ffce/lib/logstash/outputs/logio.rb
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/log.io-NarrativeScience-old#48
No description provided.