LogViewPlus Support » LogViewPlus Support » Configuration & Customization » Monolog LineFormatter parsing config?

Monolog LineFormatter parsing config?

sirlogalot — Thu, 07 Mar 2024 21:41:50 GMT

Hi,
Does anyone have working parser settings for Monolog's default LineFormatter output? I'm finding the mixed string/JSON output a little tricky to parse.

This is the format LineFormatter uses: [code]"[%datetime%] %channel%.%level_name%: %message% %context% %extra%\n"[/code]

Here's examples of the two types of output. In the first line the JSON part is an object, in the second it's an array.
[code][2023-08-28 17:37:40 MDT] Site.ERROR: Error adding note to entry {"entry_id":41000,"error":"Invalid or empty note"} {"foo":"bar"}
[2023-08-28 17:37:40 MDT] Site.ERROR: Error adding note to entry [] {"foo":"bar"}[/code]

RE: Monolog LineFormatter parsing config?

sirlogalot — Thu, 07 Mar 2024 21:41:50 GMT

Thanks! After trying that, I ended up switching the output of Monolog to use the JsonFormatter instead, much easier to load and parse.

RE: Monolog LineFormatter parsing config?

LogViewPlus Support — Wed, 06 Mar 2024 09:26:44 GMT

This is a tricky file to parse because the message, context and 'extra' are all separated by a single space. This does not sufficiently delineate where one field stops and another begins.

The LogViewPlus default parser is pretty good in this case which just treats all three fields as a message. Messages can then be parsed separately where needed, so this isn't a bad option.
[code][%d{yyyy-MM-dd %H:mm:ss ZZZ}] %c.%p: %m%n[/code]
You could also parse out the message and detail by ending the message on the '{' character. This would treat the context as part of the message. Something like:
[code][%d{yyyy-MM-dd %H:mm:ss ZZZ}] %c.%p: %m {%S{Detail}%n[/code]
It looks like there is another problem here too. The 'context' field looks like it may be optional. LogViewPlus requires all log entries to follow the same schema, so optional fields are not fully supported. However, there is a work around. You can parse optional fields by using a multi-pattern and progressing from most to least complicated scenario. Something like:
[code][%d{yyyy-MM-dd %H:mm:ss ZZZ}] %c.%p: %m [%S{Context}] %S{Detail}%n
[%d{yyyy-MM-dd %H:mm:ss ZZZ}] %c.%p: %m {%S{Detail}%n
[%d{yyyy-MM-dd %H:mm:ss ZZZ}] %c.%p: %m%n[/code]
Adding some context between the [], this would produce a grid like:

Hope that helps,

Toby