Tag: LogAnalyzer

LogAnalyzer v3.3.0 (v3-beta) released

Hi all,

We have just released LogAnalyzer 3.3.0. The new release has the following changes:

LogAnalyzer v3.3.0 (v3-beta)

Download file name: LogAnalyzer v3.3.0 (beta)

Changes:

  • New view for Reports in main area. The new view is simular to the statistics page and makes the report more aware and accessible to  loganalyzer users. The reports are still edited in the Admin Center.
  • Syslog/Eventlog Summary Report – both reports have been upgraded to V2! The “Event Count” column has been moved to the left of the report. The reports are using  logstream functions now to generate the report data. This has a huge positive impact on performance of database logstream  sources. Checksum calculation needed to consolidate messages is now  done by the logstream source.
  • Added function to generate missing checksums for all messages in  logstream reports. This means first time you generate a report could  take a little bit longer than usual.
  • Added optimization check into logstream sources. This check is automatically performed by the report admin. If Fields, Indexes or Triggers are missing, the report admin will inform you and give you the possibility optimize the logstream source. These checks are supported for Mysql, PostgreSQL and MSSQL only. Loganalyzer will need ALTER TABLE rights in order to fix or optimize the database structure. Indexes added by the a Report will enhance generation time as the involved fields are used for grouping or sorting. Triggers are used to generate the message checksum when a new data record is INSERTED into the database.
  • Added more debug output at critical areas.
  • Fixed bug with filter edit handling in report admin
  • Changed mininum width of context menu on mainpage from  200 to 250px due display problems in some browsers.

Version: 3.3.0
File size: 1027276 bytes

LogAnalyzer 3.2.3 (v3-stable)

Download file name: LogAnalyzer 3.2.3 (v3-stable)

Changes:

  • Removed magic quotes check from database functions (obselete due the changes in the last version)
  • Merged Changes from BUGID #288 (Thanks to User Jeff)
  • Fixed internal Filter parsing bug introduced in 3.2.2.
  • Fixed bug in syslog summary report missing checksum in report generation
  • Fixed bug in preparing filters for display in basic report class
  • Fixed bug in verification routine of sources admin when backslashes were in any other variables
  • Fixed BUGID #291, custom filters are now taken care in database logstream sources when cleaning up data.
  • Changed minwidth for context menus from 200 to 250px due display problems in some browsers.

Version: 3.2.3

File size: 985.88672 KB

LogAnalyzer v3.2.2 (v3-stable) released

Hi all,

We have just released LogAnalyzer 3.2.2. The new stable release has the following changes:

LogAnalyzer 3.2.2 (v3-stable)

Download file name: LogAnalyzer 3.2.2 (v3-stable)

Changes:

  • Implemented support to use User or Group configured logstream sources in commandline report generator (cmdreportgen.php). The Report Admin will generate an additional parameter for the sample commandline: userid=$uid or groupid=$gid
  • Fixed syntaxlogic bugs in proxy utilisation, thanks to forum member Pierre: http://kb.monitorware.com/post-t10570.html#p20033
  • Fixed ignoring “IPAddressResolve” setting when “EnableContextLinks” was disabled.
  • Added check in core function to automatically remove MagicQuotes (via “magic_quotes_gpc” setting).
  • Added support to search for full phrases instead of words only. Kindly use Quotes to mark the start and end of a phrase, for example:
    “Search for this”     // Searches for full phrase
    -“Search for this”    // Excludes full phrase
  • Report admin:
    • Fixed saving custom filterstring if new report was created or the previous custom filterstring was empty.
    • Fixed filter editor issues when full phrase strings (with spaces) were configured.
    • Fixed error in parsing include/exclude filters for numeric fields in report admin panel. Changes in the main filter parser were also necessary to fix this issue.
  • Fixed filter detection bug in report class which could lead to problems with certain filter evaluations.

Version: 3.2.2

File size: 1,005 MB

How to setup EventReporter to view Windows Eventlogs in Adiscon LogAnalyzer

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

Article created 2009-08-11 by Andre Lorbach.

Last edited 2018-03-15 by Pascal Withopf.

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. Continue reading “How to setup EventReporter to view Windows Eventlogs in Adiscon LogAnalyzer”

Running LogAnalyzer on IIS7

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. Continue reading “Running LogAnalyzer on IIS7”

Using rsyslog mmnormalize module effectively with Adiscon LogAnalyzer

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. Continue reading “Using rsyslog mmnormalize module effectively with Adiscon LogAnalyzer”