On Wed, Nov 23, 2016 at 1:32 PM, Bob Gregory <[email protected]> wrote:
> I can easily enough knock together an omriemann - it's protobuf over TCP or
> UDP. TCP allows for message ack.
>
> There are a couple of C clients that are useful as prior art, and I've
> worked with a bunch of clients in python, haskell and golang.
That would be pretty great!
We have been for a couple of years sending messages to Riemann by having
omprog start up a Ruby script that basically looks like this:
```
def process_log_entries(io, &block)
until io.eof?
process_log_entry(io.gets.chomp, &block)
end
end
require 'riemann/client'
riemann = Riemann::Client.new(host: 'localhost', port: 5555, timeout: 5)
process_log_entries($stdin) do |event|
riemann << event
end
```
```
action(type="omprog"
binary="/usr/sbin/omriemann"
template="omriemann-json"
queue.type="linkedlist"
queue.size="50000"
queue.dequeuebatchsize="100"
queue.filename="riemannqueue"
queue.highwatermark="40000"
queue.lowwatermark="20000"
queue.maxdiskspace="5g"
queue.saveonshutdown="on")
```
My understanding is that omprog will create a few of these processes if
necessary to keep queues happy. I have certainly seen times when there are
a couple of omriemann.rb processes owned by rsyslog!
- Adam Williams
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
