!!Background
Effective [event] correlation should be an integral part of modern infrstrucutre administration. Reducing alarm volume while improving information content is a key determinant of a successfully managed infrstrucutre.

!! Why it is a Problem
If monitoring is done at the following levels:
* [Application]
* [Operating System]
* [Network]

If an outage happens at the Network Level, then obviously the [Operating System] and [Application] level should have an event generation as about [Availability]. But, we do not want to cause trouble tickets to be generated for erroneous or redundant reasons or to the teams that can not help fix the problem.

An [{$pagename}] engine would be able to determine the "root" cause to be the Network and not cause ticket to go to the application owner.

[{$pagename}] is really the final piece in a network management environment. You get just so many events out there, whether polled [events] or trap events.  Taking all that information and correlating it, and efficiently figuring out what’s important and what‘s not – what are false positives, etc -- is critical.  

If I get “xyz” it might mean one thing; if I get “xyz” and you add “abc” to it, then it’s something else entirely.  So, the [{$pagename}] engine really drives root cause analysis as well.  

Without [{$pagename}], you’re stuck with additional manual processes.   If I can identify the event quickly with root cause analysis and I can figure out what’s causing that event through automated correlation, then effectively driven down response time and trouble shooting time. 

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]