Intelligent Event Modules (IEMs) are vendor event reference libraries that contain the proper priority designation as defined by the vendor or manufacturer and descriptive event definitions for detected events that transform cryptic event codes into human-‐understandable error definitions – simplifying the diagnosis activity and time to solve. IEMs provide ConsoleWorks with a watchlist of text messages, including error codes, system warnings, and status alerts, produced by an information source in the IT environment. ConsoleWorks watches for these messages, called Events, in the data streams of your managed systems, devices, and applications.
By automatically prioritizing events and providing an accurate definition with the cryptic event code, the “process” that leads to root cause analysis and close loop remediation is collapsed down to a fraction of what it would be without ConsoleWorks.
IEMs dramatically improve the ability to streamline and optimize IT Operations by eliminating time-‐ consuming event prioritization and research activities. With IEMs, events captured by ConsoleWorks that are in the vendor IEM “library” are automatically matched, assigned the appropriate priority, and presented with their human-‐readable definition. This enables administrators, engineers, and technicians to use their time for a value-‐add issue or problem resolution rather than priority assessment or event code researching.
By enabling events to be “clickable”, ConsoleWorks enables the correct console log file, history and best practice for the remediation action to be automatically opened in just one click – completing the “closed loop remediation cycle” in the most efficient manner possible.
Finally, IEM technology can be used as a domain knowledge repository. The user can define custom events so that when these events (or event combinations) occur again they will already be properly prioritized and described. The end user can also update IEMs with recommended remediation actions by event – even to the inclusion of the exact sequence used to correct the problem, previously. So, a less knowledgeable or less experienced administrator is now armed with the exact steps that were used by the expert to successfully remediate the error or incident. This is an important enabler of continuous process improvement.
Events can also trigger custom Actions to perform activities such as:
- Detecting Events
- Acknowledging event occurrence
- Purging Events that have not been addressed
- Escalating an event
- Copying Log files to another offsite storage
- Purging log files that are over 90 days old
