Sentinel Link is now supported on Sentinel Log Manager 1.1.
In Sentinel Link Integrator, a new Alert Settings window is added that allows you to configure the conditions for the Integrator to generate alerts (internal events), while configuring the Sentinel Link Integrator. For more information about setting Alerts, refer to the Sentinel Link Integrator document.
Table B-1 Bugs Fixed
|
Bug Number |
Resolution |
|---|---|
|
596479 |
The.JSON file is now created with the correct name when the Sentinel Link Collector runs in the debug execution mode. |
|
582547 |
In Sentinel Link Collector, the DeviceEventTimeString field is now set to the correct value. |
|
536119 |
In Sentinel Link Collector, the values of the incoming event fields are now preserved by the Collector except for RV 21 - RV 25, which are overwritten to track the ESM nodes that parsed the event. |
|
529913 |
The Sentinel Link Connector now does not allow you to run two Sentinel Link Event Source servers on the same port, and displays an error message indicating that ‘Port is already in use’. |
|
531859 and 535964 |
Log message errors are fixed. |
|
541101, 536115, and 541272 |
A number of event message handling errors are fixed. |
|
539925 |
Sentinel Link Integrator is now supported on Sentinel 6.1.1.2 and later. |
|
603050 |
In Sentinel Link Integrator, the logging level of some chatty messages is now changed from INFO to FINE so that they do not show up in the log unless specifically requested. |