I didn’t find any program out there that suited my needs for a log reader to read the server audit logs, so I made one. I thought I’d share my work for anyone that might find it usefull.
Very simple to use:
Click on Open Log, browse to the log files from the server.
This populates the names on the left.
Click one of the names to show the messages to and from that person on the right.
Click a particular message on the right to show the entire message (if it is longer than visible) at the bottom.
No need to convert or edit the logs.
No need to know how many / what users there are.
Fast and simple.
Updates:
2009/08/14 - Fixed error when file didn’t close out Jive tag (believe this happens from taking log still being written to by server), thanks wr00t.
2012/10/24 - @Seth Randall made some improvements. Thanks! File attached
2013/04/04 - Joshua Cantara - Fixed a bug resulting from when a user messages themself.
2013/04/29 - Seth Randall - New version that fixes the bug Joshua found. Now it will log the message appropriately without teminating the import.
2013/11/21 - Seth Randall - Release 1.2.0.0 - see below for changes
I created it for work…work that I no longer work at. However, I would be more than happy to share the source code with anyone that asks (or you could let me know of the bugs and I’ll see if I can update the viewer…although I may need a log to attempt this, as I do not have any)
Thanks for the program, it looks very interesting but not e able to work with.
I have some doubts
1-there are two types of history, which seguarda on the local computer and is generated by activating and which activates segenera when activated openfire server configuration audit policies,
"to which one does the program work?
2 - I have windows 7 and if I try to open the local computer error I get an unexpected end tag attached photo of the error “errorlocal”
3 - Com Windows 7 and if that keeps trying to open the audit I get an error can not be read as an added value Cadem photo error “errorauditoria”
4-Sera I’m doing wrong?
I have the openfire Openfire 3.7.0, Spark 2.5.8, handling windows 7,
I can do is very complicated the preparation of the program if I can help in some dime, but this program is looking Bengo, c reo many seek this program
This program hasn’t been updated for years, so probably it is not working normally with new operating systems (or maybe you are running on 64-bit?) or maybe audit logs schema has changed. Author of this plugin will not update it i think, but the source is provided. You can try to find some programmer to fix that program for your needs.
I find the log reader super useful and thank you for developing it. There is a bug that kills me though. Sometimes a user will copy and paste something from the internet into a Spark message. The log reader reads the messages fine but if I go to print them the pages just scroll on forever. I am assuming there is some kind of illegal character in the log file which causes the print to think the file never ends. I have no been able to pinpoint it but can upload a log which will show the problem.
I am using the latest version available of Openfire Audit Log Reader (1.2.0.0).
As we are in Brazil, the identification of some of the months is different. (in log file)
February (feb) = Fevereiro (fev)
April (apr) = Abril (abr)
May (may) = Maio (mai)
August (aug) = Agosto (ago)
September (sep) = Setembro (set)
October (oct) = Outubro (out)
Thus, an error occurs in the reading of the records of these months.
Error Parsing date
To solve the problem, I changed the log files by modifying the acronym of the months with different nomenclature. Exemple:
timestamp=“fev 03, 2018 07:37:33:590 AM”
timestamp=“feb 03, 2018 07:37:33:590 AM”
Oi Sergio!
Não tenho conhecimento para mexer no código do programa… aí o jeito foi fazer substituição dentro do arquivo, trocando "fev " por "feb " … e assim por diante.
Deu trabalho… mas usei o Notepad++ que tornou as coisas um pouco mais fáceis.
Is there something that will enable compatibility with Windows 10? When I select the file to import, it will not populate the information in the file. A popup briefly appears but then the reader screen remains empty.