Search found 531 matches
- Thu Jan 07, 2021 4:04 am
- Forum: Using LogMX
- Topic: updating startup.conf JAVA_PATH
- Replies: 1
- Views: 10
Re: updating startup.conf JAVA_PATH
Hello, LogMX runs fine on our end with Java 15 on macOS (Java 15.0.1), as well as Java 8. As for JAVA_PATH, it should work if you point to /Home/bin, /Home/bin/, /Home, or /Home. Here are a few things you can try: Look at the LogMX log files ("LogMX*.log*" in your home directory), to see if some err...
- Tue Nov 17, 2020 1:53 am
- Forum: Writing a Parser
- Topic: NullPointerException
- Replies: 4
- Views: 11151
Re: NullPointerException
Hello,
As promised, LogMX v8.0.0 is now available for download, and includes the new method "LogFileParser.init()"
: https://logmx.com/dev/api/com/lightysof ... tml#init--
Let me know if you have any questions!
Xavier
As promised, LogMX v8.0.0 is now available for download, and includes the new method "LogFileParser.init()"

Let me know if you have any questions!
Xavier
- Tue Nov 17, 2020 1:50 am
- Forum: Using LogMX
- Topic: Parsing JSON output from log4j2
- Replies: 4
- Views: 192
Re: Parsing JSON output from log4j2
Hello,
As promised, LogMX v8.0.0 is now available for download, and includes the JSON parser I mentioned
Let me know if you have any questions!
Xavier
As promised, LogMX v8.0.0 is now available for download, and includes the JSON parser I mentioned

Let me know if you have any questions!
Xavier
- Thu Oct 29, 2020 1:11 am
- Forum: Using LogMX
- Topic: Parsing JSON output from log4j2
- Replies: 4
- Views: 192
Re: Parsing JSON output from log4j2
You are right, the new version of Log4j2 now uses an { instant } object instead of "timeMillis" (I used Log4j2 v2.10 to generate these logs, but v2.11 introduced this new JSON format). We will then also update the current "Log4j2JSONLogFileParser" shipped with LogMX. But the good news is that the ge...
- Wed Oct 28, 2020 12:15 am
- Forum: Using LogMX
- Topic: Parsing JSON output from log4j2
- Replies: 4
- Views: 192
Re: Parsing JSON output from log4j2
Hello, You have 3 options to open these logs in LogMX: Replace "compact="true"" with "compact="false"" in the Log4j config file you shared in your message (inside the "<JsonLayout>" element): The LogMX Java parser "Log4j2JSONLogFileParser" only supports this format for now, and according to your scr...
- Fri Sep 04, 2020 2:05 am
- Forum: Writing a Parser
- Topic: Regex parser, timestamp with milliseconds and timezone, time is parsed wrong
- Replies: 5
- Views: 554
Re: Regex parser, timestamp with milliseconds and timezone, time is parsed wrong
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...
- Thu Sep 03, 2020 3:28 am
- Forum: Writing a Parser
- Topic: Regex parser, timestamp with milliseconds and timezone, time is parsed wrong
- Replies: 5
- Views: 554
Re: Regex parser, timestamp with milliseconds and timezone, time is parsed wrong
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...
- Thu Sep 03, 2020 2:21 am
- Forum: Writing a Parser
- Topic: Regex parser, timestamp with milliseconds and timezone, time is parsed wrong
- Replies: 5
- Views: 554
Re: Regex parser, timestamp with milliseconds and timezone, time is parsed wrong
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...
- Tue Aug 25, 2020 1:49 am
- Forum: Installing LogMX
- Topic: Installing on macOS Catalina
- Replies: 1
- Views: 347
Re: Installing on macOS Catalina
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...
- Tue Aug 18, 2020 2:17 am
- Forum: Writing a Parser
- Topic: NullPointerException
- Replies: 4
- Views: 11151
Re: NullPointerException
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
OK, since there is clearly a need, we will add it in the next version (v8.0)

We will let you know when it's available!
Thanks for your feedback.
Xavier
- Sun May 17, 2020 7:26 pm
- Forum: Using LogMX
- Topic: Runtime Exception java.lang.reflect.InvocationTargetException
- Replies: 1
- Views: 1148
Re: Runtime Exception java.lang.reflect.InvocationTargetException
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...
- Thu Apr 16, 2020 10:57 pm
- Forum: Writing a Parser
- Topic: Regex, OR, multiline and mixed logs
- Replies: 2
- Views: 2794
Re: Regex, OR, multiline and mixed logs
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...
- Thu Apr 16, 2020 10:39 pm
- Forum: Writing a Parser
- Topic: Using milisecond timestamp with regex parser
- Replies: 1
- Views: 1501
Re: Using milisecond timestamp with regex parser
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...
- Sat Mar 21, 2020 1:25 pm
- Forum: Installing LogMX
- Topic: Log file alerts option
- Replies: 4
- Views: 18814
Re: Log file alerts option
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...
- Mon Mar 16, 2020 11:27 pm
- Forum: Writing a Parser
- Topic: Help with JSON parser
- Replies: 6
- Views: 4439
Re: Help with JSON parser
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
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