|
|
|
|
|
|
|
|
|
|
The following features are new in Log Central 5.0:
Log Central monitors and manages WebLogic Enterprise log files. Log Central provides predefined log mappings and predefined message definitions for these files. See the "Predefined Mappings and Message Definitions" section in the Release Notes for the specific WebLogic Enterprise versions that are supported. See Predefined Log Mapping for information about predefined log mappings. See Creating Message Definitions for information about message definitions.
Log Central monitors and manages Tuxedo 7.1 log files. Log Central provides predefined log mappings and predefined message definitions for these files. See Predefined Log Mapping for information about predefined log mappings. See Creating Message Definitions for information about message definitions.
You can define different actions for the same messages originating in different domains. See Filtering Based on a Domain for information about how to implement domain-based message filtering.
In addition to using a filter condition to determine whether or not to perform an action, you can also apply suppression criteria to actions. Suppression critera can be based on a time interval or a number of occurrences or both. If you used an intermediate version of Log Central that supported filter suppression criteria, the name of one of the filter suppression criteria was changed from OCCURENCES to OCCURRENCES. See Suppressing an Action for information about how to use filter suppression criteria.
Log Central can start Log Monitors automatically in addition to the Central Collector and Data Collection Agents when you call start_messaging. For information about how to configure Log Monitors to start automatically, see the descriptions for the DEFINE_LOG_MONITOR and MANAGED_NODE configuration file entries.
Log Central supports long names and special characters for host names. |
Support for BEA WebLogic Enterprise
|
|