Search found 552 matches
- Fri Jan 10, 2020 1:01 am
- Forum: Writing a Parser
- Topic: Custom Paser
- Replies: 3
- Views: 12211
Re: Custom Paser
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...
- Mon Jan 06, 2020 2:02 am
- Forum: Using LogMX
- Topic: (Mac) LogMX HTTP Server Not Receiving Logs
- Replies: 10
- Views: 43295
Re: (Mac) LogMX HTTP Server Not Receiving Logs
Hello,
LogMX v7.9.0 has just been released, and it contains, among many other things, a fix for ADDITIONAL_CLASSPATH (i.e. this variable in "startup.conf" now also works on macOS to add extra classpath elements).
Xavier
LogMX v7.9.0 has just been released, and it contains, among many other things, a fix for ADDITIONAL_CLASSPATH (i.e. this variable in "startup.conf" now also works on macOS to add extra classpath elements).
Xavier
- Tue Nov 26, 2019 11:44 pm
- Forum: Writing a Parser
- Topic: Windows MSI Log Parser
- Replies: 1
- Views: 19214
Re: Windows MSI Log Parser
Hello,
I don't think there is a LogMX parser for these logs yet, but you or we can easily create one. Would you mind sharing an example of logs here, as well as the fields you want to retrieve?
Thanks,
Xavier
I don't think there is a LogMX parser for these logs yet, but you or we can easily create one. Would you mind sharing an example of logs here, as well as the fields you want to retrieve?
Thanks,
Xavier
- Mon Sep 23, 2019 3:45 am
- Forum: Using LogMX
- Topic: Using LogMX with log4j2
- Replies: 2
- Views: 21500
Re: Using LogMX with log4j2
Hello, Did you open the logs tab in LogMX before your JBoss application? For Socket Appenders, LogMX should be started first so that somebody opens the TCP port and listens to it, otherwise the logging may never happen. Also, I'm a bit confused why you tried to add the Log4j JARs in LogMX: if you ar...
- Fri Aug 23, 2019 3:22 am
- Forum: Using LogMX
- Topic: Jump Host - Two Factor Authentication
- Replies: 1
- Views: 15053
Re: Jump Host - Two Factor Authentication
Hello, To be honest, I had never heard of an SSH session opened using a physical RSA token, until today. So I looked it up. According to https://www.ssh.com/manuals/clientserver-product/52/Clientserver-securid.html (Tectia, pretty famous), such 2FA is implemented using the SSH Authentication method ...
- Thu Jul 11, 2019 11:54 pm
- Forum: Installing LogMX
- Topic: Log file alerts option
- Replies: 4
- Views: 28391
Re: Log file alerts option
OK great, added to our backlog. We will post a message in this thread when the feature will be available.
- Thu Jul 11, 2019 1:39 am
- Forum: Installing LogMX
- Topic: Log file alerts option
- Replies: 4
- Views: 28391
Re: Log file alerts option
Hello, There is no such feature for now in LogMX, but it's a good idea. Maybe we can add an optional suffix to specify an individual log entry field: for example %e{message}, or %e{timestamp} (and of course we would keep the possibility to use just %e to output the complete log entry). What do you t...
- Fri Jun 14, 2019 12:09 am
- Forum: Using LogMX
- Topic: (Mac) LogMX HTTP Server Not Receiving Logs
- Replies: 10
- Views: 43295
Re: (Mac) LogMX HTTP Server Not Receiving Logs
I did test on macOS, but only to reply at your first post to check how the HTTP server is behaving on macOS Mojave (I didn't use your Parser because I didn't have it back then, so I used a Parser I already had). But I just tried with your Parser and your JAR, and I reproduced the issue. I still thin...
- Thu Jun 13, 2019 12:04 am
- Forum: Using LogMX
- Topic: (Mac) LogMX HTTP Server Not Receiving Logs
- Replies: 10
- Views: 43295
Re: (Mac) LogMX HTTP Server Not Receiving Logs
I tried to open the same URL (http-server://127.0.0.1:8080/logmx), with your Parser "GlogJSONParser.GlogJSONParser", with your library "json-20141113.jar", and with your LogMX config file ("logmx.properties" from your health-report), and it worked fine, even with all the HTTP headers you specified i...
- Wed Jun 12, 2019 12:43 am
- Forum: Using LogMX
- Topic: (Mac) LogMX HTTP Server Not Receiving Logs
- Replies: 10
- Views: 43295
Re: (Mac) LogMX HTTP Server Not Receiving Logs
Hello, Looking at your Health Report, it seems that if you don't see any log entry, it's because the Log Parser you wrote (GlogJSONParser.GlogJSONParser) failed: it cannot find the class org.json.JSONArray (I guess it's the JSON library you'd like to use in order to parse the json log entry). If you...
- Mon Jun 10, 2019 10:55 pm
- Forum: Using LogMX
- Topic: (Mac) LogMX HTTP Server Not Receiving Logs
- Replies: 10
- Views: 43295
Re: (Mac) LogMX HTTP Server Not Receiving Logs
Hello, I just tried on macOS Mojave (same URL, with curl), and it worked fine. Here are a couple of things you can try: In the terminal, type: lsof -nP -iTCP:8080 You should see the LogMX process listening on the port 8080. If not, you may encounter some OS network config issue (firewall, network in...
- Fri Jun 07, 2019 12:26 am
- Forum: Using LogMX
- Topic: Parsing logback: attribute line break and CDATA
- Replies: 5
- Views: 19826
Re: Parsing logback: attribute line break and CDATA
Wow, I was not aware of this weird Layout offered by Logback :shock: . It's basically a Layout that tries (but clearly fails) to mimic the Log4j XML Layout. I personally think it's wrong that Logback provides this. If at least it had the same format, why not, but since it's not the same format, I wo...
- Thu Jun 06, 2019 12:38 am
- Forum: Using LogMX
- Topic: Parsing logback: attribute line break and CDATA
- Replies: 5
- Views: 19826
Re: Parsing logback: attribute line break and CDATA
Hello, These logs look like they were actually produced by Log4j, not Logback (see https://howtodoinjava.com/log4j/how-to-create-logs-in-xml-format-using-log4j). But even then, this new line character right before the timestamp prevents LogMX from recognizing this Log4j syntax (and as you said, the ...
- Tue May 28, 2019 9:40 pm
- Forum: Using LogMX
- Topic: Log file size limitations
- Replies: 1
- Views: 14517
Re: Log file size limitations
Hello, I would actually consider a 60 MB log file rather small. There is no file size limitation. But there are 2 cases: You want to load all the log events in memory to see them in the graphical user interface. You want to monitor only the end of a log file being updated in real-time (and maybe get...
- Sun May 12, 2019 11:32 pm
- Forum: Submitting a feature request
- Topic: cancel opening multiple files when out of memory
- Replies: 5
- Views: 32924
Re: cancel opening multiple files when out of memory
LogMX v7.8.0 has been released: If LogMX runs out of memory when loading multiple log files, it now doesn't try to load the remaining log files anymore The "Open file" dialog received a few improvements for local files: it now provides 2 new file filters (for "*.log" files, and for compressed files)...