|
|
The new features, bug fixes, and limitations in each of the release are mentioned below.
7.2 - Build 7020 - Standalone Edition
The general features available in this release include all the features of EventLog Analyzer Version 7.2 Build 7020 and
Features:
- Print Server Activity monitoring - Print Server logs are collected and server and printer specific reports are generated
- Apache Web Server monitoring - Access and Error logs are supported
- Report Scheduler enhanced with edit option
- In Windows and Linux 64 bit installations of the product, live syslog viewer is supported
- In the username field of Custom Report wizard, wildcard character '*' is supported
Bug Fixes:
Known Issues:
- To fix the DHCP windows logs schedule import issue, new file pattern is added
- In non-English Linux platforms, free memory space was displayed as '0'. Fixed the issue
- If the report is drilled down for a specific Host or User from Scheduled Compliance Report profile and exported as PDF, the PDF file is blank, This issue is fixed
- For custom Host type, archive search result is blank. Fixed the issue
- If Windows 7 logs are forwarded to EventLog Analyzer using Snare, it is detected as Cisco host. The issue is fixed
- Fixed the issue in resetting Email and SMS limits - same calendar reference was used in resetting 'Sent Email' count and 'Sent SMS' count
- Fixed the issue, Monthly schedule not getting created
- Fixed the issue in source based custom report. The report displayed 'No data available', when drilled down and exported
- The issue 'No data available', when Oracle logs are collected from Linux host, is fixed.
- SysEvtCol process crashed when logs are collected from Oracle host. The issue is fixed
- The 'Computer account changes' and 'Successful user account validation' SOX Compliance reports displayed empty fields. Fixed the issue
- In the Alert Email, IP address was sent instead of resolved DNS name. Fixed the issue
- The script was getting invoked twice, when 'Run a script' action was performed on Alert generation. Fixed the issue
- The logging issue is fixed, in OS Windows XP and above, if Server and Host are in different time zones
- In both English and non-English installations, Object access reports were not properly categorized. Fixed the issue
- If more than one Agent is assigned in OS Windows Vista and above, the Agent crashes. Fixed the issue
- If the event is having invalid priority (len is greater than 5) in a Syslog, the SysEvtCol is quit. Fixed the issue
- The Log Agent's host name is getting stored as Fully Qualified Domain Name (FQDN) in database, where as hostname from Agent is not FQDN. Hence, Agent does not work. Fixed the issue
- If the Process name length is greater than 40 in a Syslog, SysEvtCol is quit while parsing the Syslog. The issue is fixed
- The issue, Event ID 566 not getting displayed in Compliance reports, is fixed
- In Chrome browser web client,
- Dashboard view creation is not available
- Scheduled Application log import is not available
- If Log Agent is used, Print Server log collection and Oracle log collection is not applicable