leev: I just use logstash to "tail" my log files and drop them to redis or RabbitMQ
gilhoum joined the channel
zimbatm has quit
leev: but that does use quite a lot of RAM
zimbatm joined the channel
stonith has quit
leev
yeah, think i might use beaver shipping to redis
stonith joined the channel
cwebber has quit
zimbatm has quit
gilhoum has quit
gilhoum joined the channel
nmistry joined the channel
fedesilva joined the channel
revg has quit
awheeler has quit
awheeler joined the channel
nmistry has quit
awheeler has quit
trombik joined the channel
nmistry joined the channel
zimbatm joined the channel
zimbatm has quit
nmistry has quit
zimbatm joined the channel
nhhagen has quit
BaM`
does anyone know if the pdf version of the logstash book has DRM?
only asking so I know if I'm limited to particular readers
nhhagen joined the channel
Borre-go
when i pass all my logs into redis the host changes from the sender to 0.0.0.0
someone knows why?
jhulten has quit
zimbatm has quit
nmistry joined the channel
nhhagen__ joined the channel
nhhagen has quit
joeblow750
Hi all. If all ES instances are down, how long (if at all) would a logstash indexer typically buffer for before the event is lost?
nmistry has quit
nhhagen__ has quit
my specific error is ""Failed to flush outgoing items" and wondered if there are some logstash setting to queue to disk or perhaps not read from its input queue unless it knows it has an ES node to write to?
gilhoum has quit
dvogt has quit
threesome has quit
jhulten joined the channel
nhhagen joined the channel
blackmaria joined the channel
nhhagen has quit
gilhoum joined the channel
sagarC_
does the syslog input filter do anything smart with the @timestamp? I'm seeing the messages displayed as the timestamp local to that machine (and then converted to UTC), I thought without a date filter @timestamp would be be set to when the message is received
nmistry joined the channel
fenrus02 joined the channel
nmistry has quit
zimbatm joined the channel
awheeler joined the channel
Borre-go has quit
zimbatm has quit
zimbatm joined the channel
awheeler has quit
zimbatm has quit
awick joined the channel
stonith has quit
gilhoum has quit
zimbatm joined the channel
when I look at the debug information it look like a date filter is applied, even if not specified in the config
gilhoum joined the channel
ggoZ has quit
blackmaria has quit
danshultz joined the channel
blackmaria joined the channel
joeblow750
Hi there. Having a strange time getting two linux openvz ES nodes joined into a cluster. They both have unique node.name entries and share the same cluster.name ... i haven't set any of the discovery options, but have set bootstrap.mlockall: true, indices.memory.index_buffer_size: 50%, index.translog.flush_threshold_ops: 50000
fedesilva has quit
blackmaria
joeblow750 I have never really done this but network.bind_host
I have had issues if they are not in the same network/vlan or vpn
dec has quit
nhhagen joined the channel
dec joined the channel
nhhagen has quit
joeblow750
blackmaria: i tried network.bind_host but to no avail ... both hosts are on the same network/vlan and can both telnet to each other's 9200 port
blackmaria
joeblow750 give me a sec...
sagarC_
joeblow750: try unicast instead of multicast zen discovery
blackmaria: i've narrowed it down to literally an es cluster as I have stopped all logstash shippers and indexers, cleared out all ES indexes and it still won't join for a vanilla install
blackmaria
that is odd
can you do your telnet magic from es host to es host ?
… and this is linux right?
joeblow750
yup the telnet to each other on 9200 / 9300 works .. linux containers (openvz)
joeblow750 I have been googling … "There seem to be general problems/needed workarounds with OpenVZ - I am tempted to close this bug" sorry I cant be of more help ( it is getting late in my TZ :)
goodluck!
fwiw I have never had to set the multi/unicast setting is I used a bind host.
anyway, gtg
joeblow750
blackmaria: no probs, thanks for your efforts
blackmaria
cool, I hope you can get it working … check back in #elasticsearch and check their bug tracker to help direct your question… and evidently the ES mailinglist might help too.