Automatic Login/Logoff Reports

Tuesday, September 17th, 2013

Automatic Login/Logoff Reports.

Article created 2013-09-17 by Florian Riedl.

In this article we have a scenario of a Windows Server 2008 system, which monitors the Security Logs for Logon and Logoff Events through EventReporter, writes the log data to a database and creates automatic reports through Adiscon LogAnalyzer and Scheduled Tasks. (more…)


Using MongoDB with rsyslog and LogAnalyzer

Sunday, February 24th, 2013

In this scenario we want to receive cee-formatted messages from a different system with rsyslog, store the messages with MongoDB and then display the stored messages with Adiscon LogAnalyzer. This is a very common use-case. Please read through the complete guide before starting.

We will split this guide in 3 main parts. These parts can consist of several steps.

  1. Setting up rsyslog
  2. Setting up MongoDB
  3. Setting up LogAnalyzer

This guide has been created with (more…)


How to upgrade LogAnalyzer

Tuesday, January 10th, 2012

This Step-By-Step Guide describe how to Upgrade your LogAnalyzer Version.
In this example I use a local WAMP Server.

1. First download the latest stable or beta build from here: http://loganalyzer.adiscon.com/downloads
(more…)


How to setup EventReporter to view Windows Eventlogs in Adiscon LogAnalyzer

Thursday, September 1st, 2011

How to setup EventReporter to view Windows Eventlogs in Adiscon LogAnalyzer.

Article created 2009-08-11 by Andre Lorbach.

Last edited 2012-08-14 by Tim Eifler.

This article will help you to setup an environment to log and store Windows Events at a central place using EventReporter, and view and search them using Adiscon LogAnalyzer. (more…)


Running LogAnalyzer on IIS7

Thursday, July 28th, 2011

The usual user of Adiscon LogAnalyzer is using it on a Apache Webserver. But on the other hand, there are some customers who want to use it on IIS. Though, it is not ideally optimized for IIS, it still works. Unfortunately, the installation process is not entirely straight forward and installing PHP (which is a requirement) might give one or another a rather hard time. Now, fortunately, we found a very easy way to get things set up correctly, which we want to show. (more…)


Using rsyslog mmnormalize module effectively with Adiscon LogAnalyzer

Friday, May 20th, 2011

Using the mmnormalize module in rsyslog is a bit complicated at first. We want to describe in this article how to set up the basic components for using log normalization. In addition to that we will show how to configure these components so messages will be split into pieces of information. These pieces of information should then be written into a database for review with Adiscon LogAnalyzer. (more…)


How to create automated daily/weekly reports?

Thursday, March 31st, 2011

Wouldn’t it be nice to get the reports in a preconfigured time interval, for example every day or every week?

The reports module is integrated since version 3 of LogAnalyzer. It supports HTML and PDF output and can be fully parameterized. For example, Adiscon LogAnalyzer can be used to analyze user account logons over a specific time frame, system and network errors can be identified or a status report of the whole network be generated. And at it bests: once configured, reports can be sent automatically by email in a daily, weekly or custom interval. (more…)


The connection to the interface takes long

Thursday, October 21st, 2010

Sometimes we get the message that the login to the LogAnalyzer interface takes long. There are two simple steps that can solve this issue. (more…)


Is LogAnalyzer a alternative for Logzilla?

Thursday, May 6th, 2010

Many people know Logzilla. It was known as php-syslog-ng before. But why should we write about this product from our competitors. The reason is simple. (more…)


How to resolve the error „No syslog records found (code 8 )”?

Thursday, April 15th, 2010

Some people stumbled upon a problem when installing LogAnalyzer v3.0.0. They got the following error message:

No syslog records found (code 8 ) – Error Details:
Unknown or unhandeled error occured.

Additionally, when "MiscShowDebugMsg" (more…)