Even after all these years; System Center Operations Manager (SCOM) is still going strong as an on-premises performance and application monitoring solution. To really get any value from your investment you need to take time deploying and tuning SCOM, building processes that help you sort out the noise from the real issues and getting buy in from other teams to support your deployment.
With the foundations in place, you can then gain greater insight into your applications health by ensuring all that data is collected can be viewed quickly and easily by the various teams. This might be a high level overview dashboard for service managers, such as is shown below, or drill down performance and availability dashboards that can quickly help identify issues and speed up the remediation process.
To do that; I’d suggest taking a look at Squared Up.
Not only does Squared Up deliver super-fast HTML5 dashboards, they can also provide automatic application discovery and even dynamically integrate external data – all delivered via a single, lightweight, easy-to-install product.
I’m going to run through a series of articles on how to develop monitoring using Visual Studio bringing together examples of work I have done over the years as a consultant at enterprises across Europe as well my time as a Senior Premier Field Engineer at Microsoft and now as a customer at a major financial institution in the UK.
But the bottom line is that unless individuals look at the results of your monitoring, then all your development work isn’t going to reap the rewards it should. So I’ll pay particular attention on building monitoring in such a way that it can be easily displayed on dashboards across your enterprise. And to design the monitoring so that you, or your internal customers, can decide on how health roll up will work and which monitored objects will go red. For example; if you have separate infrastructure and application teams then you want to ensure that the right objects display the right status for the right teams.
This authoring series won’t be a full tutorial – for that you cannot beat the great work of Brian Wren on the MVA training. I also won’t be duplicating the official documentation. Instead, I’ll be looking to supplement both of those sources of information with examples of different ways of authoring management packs depending on what it is you are looking to achieve.