i am early enough in my testing that i can just nuke the data and start over, having grok explcitly store them as ints
spuder has quit
tchiang has quit
matanya joined the channel
bvi joined the channel
matanya has quit
matanya joined the channel
matanya has quit
matanya joined the channel
wilmoore has quit
windowsrefund has quit
pjanzen
How can I check which data is in a elastic index and if maps to a custom mapping template?
I am getting error on queries: Failed to query elasticsearch for previous event {:query=>"exim_msg_id:\"1XBWUN-0007Hw-Fz,1XBWUN-0007Hw-Fz\" AND exim_msg_state:\"received\"",
mak0_reactor - the add_tag is not needed...LS will auto add this tag when it discovers a mutltiline msg
mako_reactor
mrlesmithjr: OK
Sketch
b#ew
hacfi has quit
hacfi joined the channel
jmreicha_ has quit
zz_pdvyas is now known as pdvyas
mikeface_
logstash is automatically switching codecs from json to json_line on an input, is there any way to prevent that?
shoerain
mikeface_: can you give an example? I don't think it should do that, so it would be useful to see the situation where it's occurring. Here's an example of the "json" codec vs the "json_lines" codec. Make sure to clone the repo and then run it
mikeface_: hm I see, do you think you can still give a nexample?
willejs has quit
willejs joined the channel
willejs has quit
xelra has quit
willejs joined the channel
xelra joined the channel
beata joined the channel
FortySix2 has quit
FortySix2 joined the channel
FortySix2 has quit
FortySix2 joined the channel
krenn082 has left the channel
_Bryan_
Has there been a new drop of the logstash forwarder recently? While testing I found out that is the SSL certs are wrong it can cause the indexer to crash
I was wondering if this is somethign known and if ithas been fixed in a newer version
joef has left the channel
loide has quit
juarez has quit
avleen
_Bryan_: not afaik :(
nextdoorwarren joined the channel
_Bryan_
avleen; Hmm...ok...any idea how I can protect against someone brining up a forwarder with invlaid SSL certs and trying to connect and crashing my indexers/
avleen
_Bryan_: i do it by controling all my forwarders from chef, so they all get the same cert and config
that's all i got right now, other than fixin the bug itself :)
_Bryan_
right...but if somoene else builds on to connect which it shoudl get denied without the right SSL certs...how would you prevent them from crashing you indexer