4 out of 5.0, Reviewed Nov 30, 2016
The initial implementation was fairly straightforward. Tuning and testing are where the real work is required. You can't just install a bunch of management packs and walk away. For this product to be effective in your organization, you must customize the management packs to fit your environment and sometimes create your own monitors where no MPs are avaiable. If you want alerts to be meaningful, then you have to treat each alert as either an actual issue or an opportunity to fine-tune the rule/monitor. If you just "ignore" alerts that are transient or not indicative of a problem, you weaken the whole system and those who use it. I recommend starting off with only a basic up/down monitor for each server/service in your organization and then slowly bring in MPs and monitors as the business needs are identified.
If you want alerts to be meaningful, then you have to treat each alert as either an actual issue or an opportunity to fine-tune the rule/monitor. If you just "ignore" alerts that are transient or not indicative of a problem, you weaken the whole system and those who use it. I recommend starting off with only a basic up/down monitor for each server/service in your organization and then slowly bring in MPs and monitors as the business needs are identified.
It is a framework that works well within the microsoft infrastructure. We are a mostly microsoft shop, so this means it integrates very well with some of our main software suites.
as I mentioned before, the software is complex and does pretty much nothing out of the box. Management packs are available and are a good place to start, but they are also complex and often need to be modified and have setting overridden to work properly. Setting up even simple monitoring can be a bit overwhelming for a new user and the UI makes it difficult to retrace one's steps when attempting to correct mistakes.
The UI is is not very intuitive and the workflow for adding monitors/rules/alerts is not very easy to understand. Wizards could help for some known tasks, but the UI itself hasn't changed much in the past 10 years. Its time to make some improvements that make the console more useable for untrained users such as operations staff.
As I mentioned earlier, we would have started much smaller with fewer management packs activated and spent more time at the beginning fine-tuning so that we didn't have as many erroneous alerts. Also, we should have had a better understanding of what each metric is and what is affected when it triggers. often times, those on call have to google and research to find out what an alert actually means when it comes up as management packs often contain hundreds of rules/alerts.
dealing with microsoft support is rarely a positive experience, regardless of the software package in question.
4 out of 5.0, Reviewed Aug 29, 2016
We really like the product and how well it is integrated into Azure. The Analytics query language and graph generation is very good. Integration with PowerBI was an added plus. Our biggest challenge is that we were an early adopter and started using the service while it ws still in preview so many things changed/improved while we were using. The benefit of this was that Microsoft was very responsive to our feedback and introduced/prioritized enhancements based on our needs.
Embrace Azure PaaS services to get the best out of the box service monitoring.
Application Insights Analytics. This tool has helped us do ad hoc investigations into issues we are having with our system that we did not initially account for.
The portal graphs are good and getting better, but sometimes the interface is slow or difficult to find the controls we need.
Provide a more specific roadmap of new functionality and regional deployments.
Adopt Application Insights across the board. We used ELK stack for a couple of services and have not been able to get the same depth of functionality without additional effort.
We've had good access to members of the product team to answer our questions, understand our needs and provide solutions.
5 out of 5.0, Reviewed Jun 14, 2016
SCOM is a solid Windows monitoring product. It provides great flexibility in creating new monitoring rules. It has been critical for us, not just for operational rules, but security monitoring also.
flexibility and role-based administration.
Console can be slow and web-based console isn't worth using.
Microsoft is spending too much.
We currently monitor client systems. Due to their scale, we wished we had looked at alternatives for our non-critical desktop systems.
4 out of 5.0, Reviewed Dec 9, 2015
SCOM has been strong to Alert to knowledge and task recovery on Day 1 to ensure Mode 1 can focus on improving the configuration standard. There are challenges of the knowledge to alerts is still at the Engineering level that is above Mode1 capability to understand the many variables why alerts may be generated above and below the technology layer that reached its threshold level. This is not a tool issue but a skillset to understand what it needed to be a monitor operator.
Hold the line - minimize tuning the Management Packs if no standard service templates exist.
Management Pack design to include the key areas of Reliability (Availability, Performance, Security, and Configuration). These principles help build a strong BASE, Standards Services, and as well the abiltiy to customize to specific applications.
Network segmenation will be a huge challenge for AD integrated tool. There are major trade-offs to get to market when there are some major requirements to have implement for an untrusted domain.
Engineers are curious to view thresholds and SCOM does not provide a single spreadsheet view of the complexity of workflows that make up UnitMonitors and Rules. This is a challenge to provide the default thresholds with the override rules in one spreadsheet.
Define Service Templates in the following structure: Health Policy (WEB, APP, or Database MPs), HA Policy ( non-HA vs HA e.g. Stand-alone SQL vs SQL AO), Applicaiton Profile (Manageability Apps vs LOB apps), OS Profiles (Linux vs Windows and custom tweaks), HW Profiles ( Medium, Large, and Extra Large definitions)
Microsoft support has always met my expectation. In our cloud heterogeneous environment we had to leverage Microsoft to solve other third-party solutions (e.g. VMware).
5 out of 5.0, Reviewed Dec 9, 2015
It does great job with monitoring Microsoft components.
High license cost.
In-depth monitoring of Windows servers with Microsoft components/solutions installed.
High license cost. Notification is quite noisy.
Acquire more license.
4 out of 5.0, Reviewed Dec 2, 2015
Overall we are very happy with the product.