Event Console reduces the need to maintain separate tools to monitor computers, software, printers, and other devices. Event Console collects SNMP traps and other status messages and displays them in a single location. All status messages that are received by Event Console are converted to a common format that links each received message to the affected resource in the CMDB. These formatted messages are called alerts.
See the following sections for information about this release:
The following are features of this release:
Consolidated alert management in a single event console
Alert management shows a consolidated view of device health across your network. Health is viewed by network layout, by organization group, or by directly monitoring the list of received alerts in the Event Console.
The event console displays alerts from many sources. These sources could include but are not limited to:
Event Console provides a rule-based triggering system which lets you process alerts in the following ways:
Each alert is color coded based on priority. You can filter alerts according to criteria. These criteria can include for example, data range, host name, alarm type, severity or status.
A double-click on any alert provides a pop-up with more details about the alert. Each alert has its own unique set of details depending on the source. For instance Monitor Solution alerts have data from the rule definition and the associated metric, this data is often predictable. In the case of SNMP traps the alert details are specified in the associated MIB.
You can right-click on an alert and “acknowledge” it. This signifies that the alert is known and can safely be ignored while it is worked on.
Resolved or Normal events are displayed in the event console and are colored as green. This is useful information for server/NOC technicians as it provides positive confirmation that an alert condition has been resolved or has entered a normal state. You can configure an interval for which normal events are resolved.
The following are unresolved issues in this release:
Known Issue | Article ID | Internal ID |
"Time of day" is not working for Alert Forward rules and Alert Tasks rules |
45977 | ET 1531994 |
An upgrade of Event Console returns the settings to default
|
||
Unhandled server side exception in IIS causes ‘Data cannot be loaded error’
|
||
When resolving alerts, use the "Close" button and not the "X" icon
|
||
The Alert Rule Settings page has issues with refreshing rule status
|
||
The Event Console View web part jitters around after initial installation
|
||
Multiple alerts cannot be resolved or acknowledge if not on the same page
|
||
If Event Console services are not running alerts will not be received in the database
|
||
SNMP Traps might not be received by Event ConsoleEvent Console should be able to receive SNMP traps out of the box. If not, check the following:
|
||
Windows SNMP Service must be turned off in order for Event Console to receive SNMP events
|
||
The context menu might close while you are working in it
|
||
The right-click context menu might not react to your curser
|
||
You cannot delete the Purge Policy Schedule even though the user interface includes a Delete option
|
||
When non-English regional settings are used in Internet Explorer, but the operating system is set to English, then some localized strings in the user interface may not appear
|
||
Event Console Report issues when using non-English and non-Japanese regional settings
|
||
KNOWN ISSUE: Event Console view cannot be opened in remote resource client manager |
45456 | |
KNOWN ISSUE: Event Console Filter reset option does not reset |
45464 | |
Issue with Alert purging when Dell Management Console and Dell Client Manager are installed together on same maching. Alert purging keys off of the database server’s system time. If this differs from the NS server’s system time, then a purging delay of up to 1 day may be experienced. For more information see knowledgebase article 46002. |
46002 |
Subscribing will provide email updates when this Article is updated. Login is required.
This will clear the history and restart the chat.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)