Below is the full list of results for the Big SCOM Survey 2021. We surveyed 81 SCOM users with the same 27 questions we asked in 2020. We include comparison charts at certain points to track how the SCOM landscape is changing. Click here for the results from 2020.
SCOM and the Monitoring Landscape
43% of respondents have 0-1 management groups. 17% have 2, another 17% have 3, and 16% have 4-10. The remaining 5% are split across 11-500 and participants who were unsure.
The majority of respondents have below 10 management servers. 44% have 1-5 and 21% have 6-10.
37% of respondents have 1-5 gateways. 33% have none. 12% have 6-10. The remaining 18% are split across 11 and 141+, with 2% indicating that they are unsure.
Most respondents have between 101 and 2000 agents (61%). Of these, 24% have 1001-2000, 20% have 101-500, and 17% have 500-1000.
Comparing 2021 to 2020, there has been a steep increase in respondents running SCOM 2019. 60% of 2021 respondents run SCOM 2019, in comparison to 44% in 2020.
There has also been a significant drop in respondents running SCOM 2021 R2 (19% in 2020 to 10% in 2021) and SCOM 1801/1807 (10% in 2020 to 5% in 2021).
On the flip side, what SCOM is used to monitor has remained fairly consistent.
The majority of respondents (56%) primarily use custom MPs for additional rules & monitors. 23% use them for monitoring application specific components, and 18% use them for monitoring additional platforms/technology.
Most respondents’ organizations have been using SCOM for between 7 and 15 years (69%).
There has been an interesting spike in respondents selecting ‘other’ when asked about the monitoring tools they use aside from SCOM. Stay tuned for our upcoming experts’ analysis to see what the pros make of it.
These are the ‘other tools’ respondents specified they are using:
TrueSight Operations Management
Virtana, Solutions Manager, OEM
Elasticsearch with Kibana, Network Node Manager, Service Trace, Catchpoint
Google Cloud Monitoring
Splunk and dynatrace , but not under my responsibility
Virtana, Solutions Manager, eggplant, status cake, elk
Ca Tools for network
The SCOM administrator
The majority of respondents across both 2020 and 2021 were in charge of administering SCOM, Windows Monitoring, and Infrastructure Monitoring.
Interestingly, there has been a steep increase in respondents with the job title ‘Monitoring Engineer’ and a similarly steep drop in respondents with the job title ‘Infrastructure Engineer’. See what the industry leaders make of it at our upcoming experts’ analysis.
The majority of respondents have been using SCOM for 7-15 years.
SCOM integration and alert interactivity
Out of all the respondents who selected ‘Yes’, the majority send their alerts to ServiceNow, SCOM, Service Manager and ‘Other’. There has been a 10% drop in respondents who send all their alerts into SCOM, and a similar increase in respondents who selected ‘Other’. See what the experts have to say.
The majority of respondents use SCOM Operations Console, SquaredUp and SCOM Web Console to create dashboards and reports for SCOM.
The majority of respondents tune their management packs using the SCOM Console.
Attitudes towards SCOM
SCOM’s NPS rating dropped from 36 in 2020 to 31 in 2021.
There has been an increase in respondents indicating that 3-4 people are involved in administering SCOM.
In contrast, there has been a decrease in respondents indicating that 1-2 people are involved in administering SCOM.
The majority of respondents expect their SCOM use to grow over the next year. However, in comparison to 2020, a bigger proportion of 2021 respondents expect their SCOM use to reduce.
Here are the reasons specified for respondents who indicated a projected reduction in SCOM usage.
38% Weak cloud monitoring
38% Replacing SCOM with Azure Monitor
13% Removing due to license cost
13% Lack of application specific MPs
33% Weak cloud monitoring
33% Replacing SCOM with Azure Monitor
7% Lack of container monitoring
7% SCOM’s future unclear
7% Replacing SCOM with Elasticsearch
7% Replacing SCOM with other monitoring tool (unspecified)
7% Increased outsourcing of monitoring
Here are the reasons specified for respondents who indicated a projected growth in SCOM usage.
49% Increased depth of monitoring
27% Monitoring more existing infrastructure
21% Expanding infrastructure
3% Single source of truth
37% Increased depth of monitoring
32% Monitoring more existing infrastructure
27% Expanding infrastructure
2% Application Monitoring
2% Monitoring Linux servers
The majority of respondents (54%) expect to continue using SCOM for 5+ years.
Changes in MP adoption and MP authoring
Veeam for VMware continues to be the most popular paid for third-party MP. GripMatix’s Citrix MP is now the second-most favourite, having gone from 2% to 9% of respondents indicating that they use it.
There has been a 10% increase in respondents using Visual Studio Authoring Extension to author custom monitoring, and a 6% drop for SCOM Console.
Distributed Applications, Synthetic Transaction Monitoring and Enterprise Applications (SquaredUp) continue to be popular choices. There has been a notable decrease in respondents who selected ‘We don’t monitor applications’.
There has been a 4% increase in respondents who indicated that SCOM is hosted in the Cloud.
Above are some of the most common responses. Notably, 2021 saw a steep increase in respondents asking for ‘More cloud monitoring’ and ‘Better Azure Monitor integration’.
Below is the list of all the features respondents would like to see:
Ability to customise alert contents from existing off the shelf monitoring
Ability to modify sealed MPs
Agentless monitoring improvements
Alert correlation to suppress alert storms when a dependant component is down (eg top layer Network Router/Switch fails)
Azure HCI Monitoring
Better Azure monitoring
Better integration with Azure Monitoring tools
Better relationship between alerts and performance data to unlock perf data’s value
Easier custom authoring, especially for custom classes and discoveries
Easier to get data into SCOM
Endpoint defender integration
Hyper-v monitoring improvements
Improved maintenance mode
Improve file system and network device filtering
Improved cloud monitoring
Improved hardware monitoring
Improved Linux monitoring
Improved migration between SCOM versions
Improved Network monitoring
Improved reporting on alerts
Improved Unix monitoring
Improved Windows desktop OS performance monitoring
Improved/modernised dashboards (natively)
Intrusion detection and security monitoring out of the box
Kerberos support for all Linux distros
Modern consoles for operations and administration
More MPs that add monitoring capabilities and are supported
Native integration with ITSM tools
Non SQL DB support
Optimize perf collection so values only written when they change
Reset monitors automatically when alerts from them are closed
Rest API improvements
SaaS monitoring capabilities
Server watcher behaviour from Windows for Linux servers
Simpler native way to add custom properties to objects
Subscription priority order and overlapping ability
Synthetic transaction monitoring
URL Monitoring failover
URL Monitoring improvements
URL Monitoring improvements
Use custom properties in alerts and for subscription criteria