10
Novell Sentinel Log Manager 1.0.0.5 Release Notes
no
vd
ocx
(e
n)
19
Fe
bru
a
ry
20
10
4.3.1 Enhancement
Top N type reports are now supported. A Top N type report named
All Vendors All Products
Top 10 Report
is installed with this hotfix and is available as a Visualization from the Search Save
As Report dialog as well from the main report list. This report provides an easy way to view a
dashboard of the most frequent activity being monitored by Sentinel Log Manager.
4.4 Issues Fixed in Sentinel Log Manager 1.0.0.2 Release
This section lists the issues fixed in Novell Sentinel Log Manager 1.0.0.2 Release.
Table 5
Issues fixed in Sentinel Log Manager 1.0.0.2 Release
545837
Issue: The Event Source Management (ESM) user interface is not able to
read the maxclausecount property in the
SentinelPreferences.properties
file.
Fixed: The Event Source Management (ESM) user interface works fine
with a high number (>=~1000) event sources and does not log any
max
clause count exceeded
exceptions.
545197
Issue: When many event sources are configured (for example, 2000+), the
Event Source Management (ESM) user interface consumes lot of memory
on webstart (for example, 1GB) and also becomes unusable.
Fixed: The ESM user interface now works fine if there are many event
sources are configured.
527007
Issue: To turn on or off the data logging for all of the operating system
event sources and all of the Application collectors, a
Data logging (All) On
and Off
option is required for the
APPLICATIONS
and
OS
tables under the
Collection
>
Syslog Server
tab.
Fixed: To turn on or off the data logging for all of the operating system
event sources and all of the Application collectors, a
Data logging (All) On
and Off
option is provided for the
APPLICATIONS
and
OS
tables under
the
Collection
>
Syslog Server
tab.
Issues Fixed
Description
537273
Issue: Non-admin user is able to log in to the Event Source Management
interface by using a cached ESM jnlp file.
Fixed: Only authorized admin user can log in to the Event Source
Management interface.
536377
Issue: Lucene indexes are not being committed on a timely basis.
Fixed: Lucene indexes are now being committed on a timely basis - once a
minute.
535736
Issue: The Rule user interface does not perform the filter validation.
Fixed: The specified filter value is validated by the Rule user interface.
Issues Fixed
Description