Hello, No worries, happy to help you use LogMX :) When you say you "can't display milliseconds at the 'display entries date with custom format'" , do you mean the timestamps in the main logs view doesn't display milliseconds as indicated by this Display option? or maybe your intent was to display na...

Actually, let me help you even further: here is a Java Class Parser I wrote for you to handle nanoseconds dates: logmx.parser.export To import it, go to Options > Parsers, and click on the import button at the bottom right corner, and select the file you downloaded from the above link. You can now d...

Hello, I believe the dates in these logs don't use milliseconds, but probably nanoseconds (because there are at least 7 digits after the seconds). And as mentioned in the LogMX documentation, only milliseconds are handled. So LogMX interprets this as 1,924,648 milliseconds, which is around 32 minute...

Hello, I was not able to reproduce the issue with my macOS Catalina laptop, which makes me think that it's probably due to a security setting: the Apple support pages https://support.apple.com/en-ca/guide/mac-help/mchleab3a043/mac and https://support.apple.com/en-us/HT202491 explain how to fix these...

Hello,

OK, since there is clearly a need, we will add it in the next version (v8.0) (probably a "init()" public method to prepare the Parser if not already initialized).

We will let you know when it's available!

Thanks for your feedback.

Xavier

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.