Hello, the first step it's a parse problem, that's right, the error is if you say "Yes" to create a New Parser, the app doesn't open the Parser's edition window, opens the third window and I can't create a new parser for this file can't be parsed. LogMX v6.2.0 has just been released and it includes ...

Hello Marko, Thanks, happy to hear you like LogMX :) You don't have to enter the Log4j pattern(s) each time you start LogMX. When you click "OK" or "Apply" in the "Options" window after having set your parser up, all your parsers should be saved to disk (by default, file "<LogMX-install-dir>/config/...

Hello Craig, It seems that the Pattern you're using for your Parser may not be quite right: from the tests I did with your log format, it seems that the Pattern to use should be me more something like this: %d{ISO8601} SAST %-6level %c %mx{version::int}:%mx{subversion::int} [%t] %m%n The difference ...

Mail re-sent. I replaced the base URL of our website with XXXXX, I guess your mail server doesn't like URLs ending with ".jar" (which could make sense!)

I just sent you an e-mail containing a link for the patch to apply (cannot post this Pro version here )

Hello, Sorry my bad, I forgot about that. My initial idea was to use the config file "<LogMX_Dir>/config/managers.properties" to list the headers you want the HTTP server to return, so that you don't need our help to add/update/remove headers. Since this file can be used for other Manager settings, ...

Hello, It's actually not using the "Error" log level, but the log level named "<NO_LEVEL>", which is a built-in log level used in case of missing log level. Looking at your parser, you are, indeed, not using any log level field, hence this behavior. By default, the color and the criticality used for...

Hello, You can achieve this through a couple of different ways, but first let me ask you: when you say "simple parser", are you referring to the Parser type named "SimpleParser"? If the answer is yes, then options 1.x below are not for you, go directly to option 2: Option 1: Ask the Parser to ignore...

You're welcome (I was about to post a message here to let you know about the release!)

Hello, The default Log4j v1 Parser that comes with LogMX doesn't support the NDC part, hence the issues you encountered. This may be fixed in a future version (also now the focus is more on Log4j v2). So for now, you can create your own Parser: in the menu "File", pick item "Configure Log Parsers......

OK thanks we will investigate that. In the meantime, you can always create Parsers at anytime by going to menu "Tools" > "Options" > tab "Parsers" > green "+" button at the right.

Hi, About the first message: it seems that a network issue happened. When did this message show up? What is the file size? You said "With connection reset in 15 or 20 seconds" . What does it mean? About the second message: it means the log file you are trying to read is using a log format that none ...

Hi, In the end, we had to slightly adjust the LogMX code in order to allow Authentication in HTTP[S] Log File Managers, so instead of sending you the new Log Manager only, I sent you (via Private Message on this forum) the links to nightly builds so you can try the new Log Manager. Please let me kno...

Hello, You're right, and you just discovered a bug. Sorry about that. Thank you for your (detailed!) feedback, I think it should be fixed in the next release, that should be available in a couple of weeks. Please let me know if you don't want to wait for the release, I will send you just the new Htt...