So on the hunch that the underscores were your hurdle, I took your file and removed the underscores, then set up a file monitor on a windows 10 UF running 6.5.2.
{"version":"1.1","host":"t800.skynet.com","short_message":"Msg TzjTJPqvUaGqaOpHXFdKXyXVaHiLpbTKfhePqbEtammLeaZVaaTb \r\n","full_message":"Msg TzjTJPqvUaGqaOpHXFdKXyXVaHiLpbTKfhePqbEtammLeaZVaaTb \r\n","timestamp":1484920098.408,"level":4,"app":"skynet","level_name":"WARN","mdcKeybIwMa":"mdcValueNYUGJgYJaTFaWcdicara","thread_name":"sample","logger_name":"common.log.json.LogFileProducer","env":"ut"}
{"timestamp":"2017-01-20 14:48:18.428","level":"DEBUG","thread":"sample","logger":"common.log.json.LogFileProducer","msg":"Msg TzjTJPqvUaGqaOpHXFdKXyXVaHiLpbTKfhePqbEtammLeaZVaaTb","mdc":{"mdcKeybIwMa":"mdcValueNYUGJgYJaTFaWcdicara"}}
inputs on the UF was :
[your input]
disabled=false
index=n00blab
sourcetype=_json
And now all fields are parsed.....So one option here is to pre-parse or re-configure logging source to remove the leading underscores to allow index time field creation..
Obviously easy for me to say with 2 events...
I also got it to work by setting both indexed_extractions= json AND KV_MODE=json.
Bit of a hacky workaround, but it works...
[salem34json]
CHARSET=UTF-8
INDEXED_EXTRACTIONS=json
KV_MODE=json
NO_BINARY_CHECK=true
SHOULD_LINEMERGE=true
TIMESTAMP_FIELDS=timestamp
category=Custom
description=indexed_extracted json for eventbreak and timestamp, kv_mode json for kvpairs to workaround underscores
disabled=false
pulldown_type=true
I decided to keep the indexed_extractions=json to enable us to declare the timestamp field for timestamp extraction, which you need here because you have multiple time formats....
then a KV_MODE=json props on your SH to pull your key value pairs to workaround the leading underscores that are messing with those fields at index time...
... View more