Log Reaper
Introduction
The Access Labs Log Reaper is a multi-purpose log parsing web application with an emphasis on break/fix and identification of errors in your log files. Whereas other log parsers are more generalized and require server-side infrastructure, this app is completely client side and allows for quick analysis and automatic recommendations.
Functionality
- High level overview of the log file, duration, number of lines parsed.
- Automatic solution recommendations based on the top error messages.
- Zero server side upload with the exception of sending error/warn messages for Recommendations. All parsing done in the browser.
- Reactive visualizations to filter data to the subset you want.
Usage
- Browse and select a file or drop a file into the drop zone.
- Wait for the file to be identified, if it could not be identified you will see 'Could not Identify' in red.
- Once Identified click the Parse button.
- The log will be parsed iteratively and you will be displayed a page containing analysis specific to the log type in question.
Accepted Input
- Syslog (/var/log/messages)
- Log4j logs (JBoss, RHEVM, ect..)
- LSOF output
- Apache access
- VDSM logs
Was this helpful?
We appreciate your feedback. Leave a comment if you would like to provide more detail.
It looks like we have some work to do. Leave a comment to let us know how we could improve.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
10 Comments
Subscriber exclusive content
An active Red Hat subscription is required to participate.
Log Incan we add gluster logs?
Is this Tool Avilaible to download and use
Nice! just found out about it more comments to follow...
could not parse console.log containing threaddump of EAP 6.3
Can this be released as a gear or similar for offline use? I work in a financial institution and can't upload log files. It looks extremely useful though and would certainly streamline troubleshooting.
+1 for RHSS and Satellite log parsing as well ;)
@Paul Drop me an email with a gluster log so I can create an RFE
@Babu That is not surprising, I cover about 90% of server.log formats, but not ones with thread dumps
@Matthew There is zero upload to our servers except for GC logs. So as long are you are not parsing GC logs, there will be absolutely nothing sent to our servers.
Is the APP availaible
@Scott yes, just give it a few seconds to load: https://access.redhat.com/labs/logreaper/
I am receiving a custom 404 error when I browse this link. I would like to try this App to parse my JBoss logs. Please advise. Thanks.
Must have been a glitch in the matrix :) it is back online!
Sorry about Richard! App is up now.
Thanks so much!
Hi,
For me the tool woks fine with server.log file but it's throwing error "failed to identify" with JBoss "access_log" file. Is this expected behaviour ? Can this tool be used for access_log ?
@Pankaj I don't currently support JBoss access logs specifically, only Apache access logs. If there is enough desire of the JBoss ones I can look into it, typically they are not often used as most people front with Apache. Not to say they aren't still useful in certain troubleshooting scenarios, but the usage is slim typically.
When will this tool support other than the Default logging pattern for the server.log file?
Response to Case:
" The pattern which is getting used by you will not work as per this tool configuration currently so you should try to change the above logging pattern to the default one which is working fine as I stated above."
@Patrick there are hundreds of possible logging combinations other than the default, I don't necessarily plan to target any other than the default and a few others except on request. Feel free to drop me an email @ smendenh@redhat.com with your log and I can investigate.
Samuel, I browsed to my log file and hit parse with the default severities chosen and it says it parsed the 1 file 100%, but sits at 80% 4 chunks parsed and never returns. File is 4.43 MB and the parser says it's log4j:std-time. Any idea why it's not coming back and displaying anything? It's an EAP 6.2 server.log file.
Thanks.
Hi Kristi, if you'd like to zip and send me the log @ smendenh@redhat.com I'd be happy to take a look and see what might be the problem.
Do you plan on supporting sosreports?
Hi John, Not currently, we have excellent tools for parsing and visualizing sosreports. Try https://access.redhat.com/discussions/469323 (https://github.com/ryran/xsos) for example.
02/23/2016 -- I just release a pretty significant update to the app including a cleaner UI, better error handling, faster hashing and identifying, better set of recommendations for errors, more intuitive interface, and many bug fixes
i liked it
Will this work with A-MQ logs?
It really depends on the format the a-mq logs are in. Give it a try, if they don't parse, open an issue @ https://github.com/engineersamuel/logreaper/issues
Very usefull tool. I am missing some comfortabilities though:
Hi Pavel,
Thank you for the feedback! I created three new new issues for you in github to track these:
Feel free to watch those in github for notifications. I won't get to them immediately due to some other pressing apps I'm working on, however, I will put some priority to the #5 the first chance I get as that is a more serious bug.
Nice!
please share the download link.
The application link is https://access.redhat.com/labs/logreaper/ and the upstream code link is: https://github.com/engineersamuel/logreaper
Hi, I'm getting the below error while analyzing JBOSS server.log file, parsing is: log4j:std Cannot read property 'trim' of undefined
hi man