System Center Operations Manager
| Developer(s) | Microsoft |
|---|---|
| Stable release |
2016
|
| Operating system | Microsoft Windows |
| Type | Performance and event monitoring |
| License | Trialware |
| Website | microsoft |
System Center Operations Manager (SCOM) is a cross-platform data center monitoring system for operating systems and hypervisors. It uses a single interface that shows state, health and performance information of computer systems. It also provides alerts generated according to some availability, performance, configuration or security situation being identified. It works with Microsoft Windows Server and Unix-based hosts.
The product began as a network management system called SeNTry ELM, which was developed by the British company Serverware Group plc. In June 1998 the intellectual property rights were bought by Mission Critical Software, inc who renamed the product Enterprise Event Manager. Mission Critical undertook a complete rewrite of the product, naming the new version OnePoint Operations Manager (OOM). Mission Critical Software merged with NetIQ in early 2000, and sold the rights of the product to Microsoft in October 2000. It was renamed Microsoft Operations Manager (MOM) and had another release as Microsoft Operations Manager 2005. Microsoft renamed the product System Center Operations Manager and released System Center Operations Manager 2007. System Center Operations Manager 2007 was designed from a fresh code base, and although sharing similarities to Microsoft Operations Manager, is not an upgrade from the previous versions.
The basic idea is to place a piece of software, an agent, on the computer to be monitored. The agent watches several sources on that computer, including the Windows Event Log, for specific events or alerts generated by the applications executing on the monitored computer. Upon alert occurrence and detection, the agent forwards the alert to a central SCOM server. This SCOM server application maintains a database that includes a history of alerts. The SCOM server applies filtering rules to alerts as they arrive; a rule can trigger some notification to a human, such as an e-mail or a pager message, generate a network support ticket, or trigger some other workflow intended to correct the cause of the alert in an appropriate manner.
...
Wikipedia