If no-one answers, it's because no-one knows (or have time).
hugh_jass joined the channel
dhollinger joined the channel
bfoote has quit
dodobrain joined the channel
Darcidride joined the channel
jakelandis joined the channel
xificurC joined the channel
xificurC
anyone knows where can I bend what certificates does logstash-plugin install use saving me some time digging into the sources?
ERROR: Something went wrong when installing logstash-output-riemann, message: certificate verify failed
we have a custom certificate in the chain which is bundled in /etc/ssl/certs/ca-certificates.crt but as many package managers this one decided to not use it
hi all - we are currently sending a large amount of logs from the 'journald' input to a remote syslog server (papertrail). we have noticed that a very small amount of our logs arrive in Papertrail hours later. I'm currently looking at this problem from Logstash's perspective. any obvious metrics/performance tweaks that we can look at implementing on logstash?
Sp0oKeR joined the channel
xificurC has quit
kcas_ joined the channel
shog
jb: but logstash is kind of FIFO thing, it won't really delay some of the logs (rather all of them or none)
hugh_jass joined the channel
jb
shog: my thoughts exactly :/
shog: which makes me thing it's a problem with our syslog receiver (papertrail).
shog
is there any common pattern in those logs that are delayed? (same host, program, etc?)
jb
no, comming from different hosts, different apps, etc :/
we are running logstash as a container on the hosts (ECS hosts) running our applications
input is journald, output is syslog.
shog
ah, so every container has its own logstash?
jb
shog: no, we run logstash on the ECS instance as a single container.
shog: each container logs to journald
shog: so we give the 'logstash' container access to the host's journald