Closed mwl closed 6 years ago
Not to mention the, at least, three timestamps in there :)
This is actually an oddity of some logging that I'm doing from the nozzle, and it's currently the only case where there would be any structured content. For this reason I suggest that these logging messages should be rare enough, and frankly uninteresting enough, to either be removed completely from the nozzle (not my preferred option as they are useful if you are observing the nozzle itself) or simply left as-is since taking on the overhead of trying to unpack these JSON-in_JSON oddities is likely not worth it given their niche nature.
Okay. I accept that. In the end we might implement the required query function to be able to parse the json content.
String encoded json inside json
message
fieldGuess we could just inject the raw json on the
message
field?