Syslog Examiner FAQ

    Port 514 open but don't receive any data

    If you know for sure, that your firewall on the Windows PC running SLE has port UDP 514 open and that you have a syslog sending device sending to the ip of this PC and you still get no data, you should examine what other programs are running on the PC.
    Chance is that you have been experimenting with other Syslog Servers and one of these still has a collection program running as a service - and the it eats all the data before SLE collect has a chance.


    Routerlog in email

    Some routers cannot send syslog messages but can send a mail with the proprietary internal log. If you send us a sample mail with a log like that, we'll do what we can to include that in the syslogexaminer interpretation of data.

    You can just tell us it's coming and then tell your router to send the logfile to

    If for some reason, your router cannot send the logfile to your external smtp server, you can run our simple "SMTP server" on your own Windows computer. It's a very simple SMTP server, that listens for any mail received on port 25 and collects it to a email_raw.txt file, that you can send to us attached to a normal email.

    You may need to open port 25 for incoming data in your windows firewall. Just start the program and click on Receive Email and wait for an email to be received. The received email will automatically be saved as email_raw.txt.

    You can download the syslogSMTP program here or in a .zip archive if you (or your antivirus program) prefer that.


    Alternative syslog format

    If the records from your syslog isn't interpreted correctly by Syslog Examiner, you can send us a sample dataset and we'll include the correct interpretation in the next version of the program. And if possible real quick.

    Just use the Toolbox menu and click on Collect Raw Data to Text and send us the file at, when the collection is done. (You choose the position of the file, when starting the collection)