It still seems like most of the requests (if not all) use “short_message” instead of “message” (what if I understated from someone in seq team is some sort of standart).
Here is example log message from seq when I enable diagnostic mode (then it should have property with raw message at least I hope).
It seems that the “message” property is not standard as I wrote (sorry I am not an expert in this area).
Unfortunately we don’t have any way in Seq to define an alternative message property, but we do have a bit of logic in this GELF server already that tries to find and set properties on nested JSON objects based on some common conventions. I think it would be reasonable for us to look for a property called message or msg and use it as Seq’s @m property if one isn’t set already. I’ll put a PR together
Yes, 6688 should work. What is the problem? There is a message now. “HTTP request executed”
Short_message is not from me, it is from your docker engine I think. Everything within “short_message” is from Squidex but is wrapped in another json object.
Oh, sorry I missed the message in raw json. Then now it should be seq problem, I guess. From there github it seems like standart for logging is actually use @m by default i do not know what is the standard (if there is any). But the current state should be ok (for me after seq implement support for message).
