Hello, I tried to reproduce this error with LogMX v7.12.0 but I didn't manage to. I tried with a Regex parser using the date format you mentioned, and the date "17/May/2020:8:00:00 -0400" in the logs, but it worked fine. Could you please post here a few lines from your logs as well as the compete Re...

Hello Chemo, Happy to hear you like LogMX ;-) In order to parse the given text 10:52:15,123 FATAL Exception 1 thrown caused by Exception 2 caused by Exception 3 using a Regex parser, I would use this Regex instead: (\S+?:\S+?:\S+?,\S+?)\s+?(\S+)\s+?(.*) Basically, when you want to match multiple cha...

Hello Eyal, The issue with using just milliseconds is that by default, the reference time will be the UNIX epoch (i.e. Jan 1st 1970, 00:00), so instead of getting 20:00:00 you would get "Jan 1st 1970 20:00:00", and instead of 25:00:00 you would get "Jan 2nd 1970 01:00:00". And it would actually be e...

Hello, This feature is now available in the new LogMX version 7.11.0 :) You can now use %e{message}, %{date}, %{level}... to include just the entry message, date, level... in an external program command line or email when an alert is triggered (sorry it was actually released 2 weeks ago, but I misse...

Hi Rod,

Got it, here is a new version (you can recognize it in LogMX options, "Parsers" tab, because its version is "v2"):
Let me know!
Xavier

Hello Rod, OK so I gave it a try, and a 2 MB log file consisting of only 1 giant line worked, but I already felt that the parsing was not immediate (~half a second) on a pretty good machine (due to this giant line). Some optimizations may be required. You will first have to add this JSON parser libr...

Hello, Yes, the built-in JSON parser is only compatible with Log4j JSON files, so it is not compatible with this format. But to be honest, I find this log format really weird, I have never seen a log file composed of a single line containing all the log entries... What about when there are a lot of ...

Hello,

Here is a new version of the Parser handling these cases.
Let me know if you have any questions/problems!

Xavier

OK thanks, but what about the "Process ID" now surrounded by square brackets [] instead of parentheses () ? Was it a typo or both are possible?

Hello,

Better late than never, this feature is now available in LogMX v7.11.0 which has just been released (to use it, go to the "Parser" tab from the "Open logs" dialog): This feature can also be used with Bookmarks and all kind of workspace elements.

Hello, Yes, basically Java Parsers can do all of that. I made some changes to handle both date formats, but then I realized that in your example, the "Process ID" is now around square brackets [] and not parentheses () anymore. Is it really the case, or was it a typo in your message? Basically Java ...

I forgot: for the other forum users who don't want to import the Parser, here is the Java code I used for reference: package sample.parser; import java.text.SimpleDateFormat; import java.util.Arrays; import java.util.Date; import java.util.HashMap; import java.util.List; import java.util.regex.Match...

Hello Rod, This log format may be a bit too complex to be tackled through a Regex. It might be possible, but because of the optional third line, the regex would be so long and complicated that it would not be maintainable. Instead, I would recommend using a Parser of type "JavaClass". It also allows...

Since this file starts with a log entry being spread over 158 lines, I think you need to change a setting: in menu "Tools" > item "Options" > tab "Parsers", at the bottom you have a text field next to "Switch to next parser when no entry found after XXX lines" . By default, the value is 100, which m...

Hello, Here are 2 possible Log4j and Regex Parsers, but I think the Regex will be better because of all the white space characters present in your logs: I'm not sure which exact padding is used to produce these logs, so depending on the number of characters next to the padded zone, you may have 4, 5...