Tag: bugfix

LogAnalyzer 3.4.2 (v3-stable)

Download file name: LogAnalyzer 3.4.2 (v3-stable)

Version 3.4.2 (stable), 2012-05-07

  • Fixed a #bugid 303, VerifyChecksumTrigger function in logstreamdb class did not generate a lowercase triggername.
  • Fixed typo in lang files
  • Changed processid field type to string in logstreamclass. Filtering for non-numeric processids is now possible.
  • Added support to filter by day (Date field – for example: timereported:=2012-01-01

File size: 1002.472 KB

LogAnalyzer v3.5.0 (v3-beta)

Download file name: LogAnalyzer v3.5.0 (beta)

Changes:

  • Added new Report “Eventlog Audit Summary Report” which can generate detailed security reports for Windows Eventlog security records. It supports Windows 2003 and 2008 Server and is compliant with the Sarbanes-Oxley (SOX) Act, 2002.
  • Added support for customized boolean report filters. This enhancement is also used by the new “Eventlog Audit Summary Report”.

Version: 3.5.0
File size: 1018658 bytes

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