[PG Feedback] SCOM Management Pack needing Version update and Feature updates
All - This poll is from SCOM Product Group. As a SCOM user, you would be using a lot of MPs and some of them could be outdated in terms version, monitors, rules and features. We are looking to revive Management Pack as a whole and we want to hear your feedback on the below topics.
- What are top 5 MPs (in terms of usage) used at your SCOM infra?
- Which top 5 MPs critically need version update (agnostic)?
- What are the top 3 issues that arise on MPs (in general)?
- What are top 3 workloads for which MPs are missing/unavailable?
Please do not forget to upvote this!
11 comments
-
MS
commented
Exchange 2013 MP needs to be updated. For all the exchange components getting monitored under one generic health state monitor which is very confusing like which component is having issue.
-
Ronald
commented
1.
I want to mention the exchange managementpack.
Wat especially needs to be updated is the documentation, we don't understand how it's working and how you need to tune the pack. It's running scripts, some tuning can be done on exchange itself outside of scom but its not clear.
I even has a monitor with the name '>'2. For the MS SQL packs please adopt the aditional MP's from Kevin Holman that takes care of the Run-As accounts and fix the issue that when an agent is upgraded or reinstalled the run-as config is gone.
-
Stoyan Chalakov
commented
1. What are top 5 MPs (in terms of usage) used at your SCOM infra?
• Windows Server OS
• SQL Server
• Active Directory
• Microsoft Exchange
• Windows Cluster2. Which top 5 MPs critically need version update (agnostic)?
• Microsoft Exchange (The MP is used for all versions, but the monitoring logic and ist functionalities are way outdated. This is also the reason why there are so many addendum Mps for Exchange)
• Office 365 (not the typical agnostic MP, but still considering that huge percentage of the customers use O365, not having a decent MP is not nice)
• Hyper-V
• SCCM
• Remote Desktop Service
3. What are the top 3 issues that arise on MPs (in general)?
• Unimportant/unnecessary workflows (rules,monitors) enabled by default.
• Oudated thresholds
• Updates to MPs are coming many months after the corresponding technology is updated.
• Naming of the MP is sometimes misleading (example - all the "1709 Plus" suffixes)4. What are top 3 workloads for which MPs are missing/unavailable?
• Containers (Docker/Kubernetes)
• Microsoft Teams
• Azure AD Connect Health and Performance -
Patrick
commented
1. Our top 5 MPs
Windows
Linux
IIS
SQL
Active Directory2. Top 5 needing updates
Configuration Manager MP needs to be updated to version agnostic
SQL Management packs updated to include Used space on databases and not just free space
Exchange
Windows (To display 2019 not just server 2016 or 1709)
Linux3. Top issues that arise
Custom MPs using PowerShell seem to cause spike on CPU during discoveries.
Disabling monitors still seem to end up enabled somewhere else -
Anonymous
commented
What are top 5 MPs (in terms of usage) used at your SCOM infra?
1. Windows Server
2. SQL Server
3. IIS
4. Cluster
5. SharePointWhich top 5 MPs critically need version update (agnostic)?
1. Exchange
2. SCCM
3. Mictosoft Open Source MP for LinuxWhat are the top 3 issues that arise on MPs (in general)?
1. Interval of discovery rules is too short
What are top 3 workloads for which MPs are missing/unavailable?
1. Containerization technologies - Docker/Kubernetes, etc
2. SNMP trap rules for SNMPv3 devices -
Anonymous
commented
In my opinion a management pack that should be updated is the Management Pack for TFS 2017
-
Greg
commented
I support all of these comments and recommendations on MP's with particular focus on API monitoring.
We need MP's period. with scripted remediation efforts prior to generating tickets (API commands, Service restart, etc)Power BI dashboards
Thanks for asking
-
Peter Svensson
commented
What are top 5 MPs (in terms of usage) used at your SCOM infra?
-Windows Server
-Active Directory
-MS-SQL
-PKI Certificate (Community)
-Veeam VMwareWhich top 5 MPs critically need version update (agnostic)?
-SCCM
-Windows ServerWhat are the top 3 issues that arise on MPs (in general)?
-CPU usage
-Update versions for new SWWhat are top 3 workloads for which MPs are missing/unavailable?
-Support for REST-APIs for Discovery, Rules and Monitors!
-Proper Web transaction monitoring. Why not implement Selenium support? -
Rubens
commented
What are top 5 MPs (in terms of usage) used at your SCOM infra?
1. Windows Server
2. MS-SQL
3. VMWare (https://www.nice.de/nice-vmware-mp/)
4. Office 365 (https://www.nice.de/active-365-mp/)
5. MailIn (https://github.com/Juanito99/SCOM.Addons.MailIn)Which top 5 MPs critically need version update (agnostic)?
1. MSSQL
2. Exchange ( continuing support for 2013 upwards please) !What are the top 3 issues that arise on MPs (in general)?
1. events are usually all disabled manually as I see no benefit
2. non-essential monitors enabled
3. alert closure behavior -> fixed with SCOM 2019 R2What are top 3 workloads for which MPs are missing/unavailable?
1. Support for REST-APIs for Discovery, Rules and Monitors!
-- I have created a bunch of them to integrate 3rd party tools like ( https://github.com/Juanito99/Connect.APM.Foglight ) and several more which are not public yet
-- there are more and more services, devices or applications which offer an REST API which would help us to monitor them via SCOM or to gather performance data for various aspect2.Monitoring Azure AD synchronization in all modes ( ADFS, not-ADFS, PTA, WriteBack, etc. ) including synchronization errors and performance information like consumed resources, synced users, failed synchronizations as alerts with details, failed sync objects as perf counter, the ability that the Server which runs the Sync-Agents can reach Microsoft ( low level and also with synthetic test if authentication works etc. )
thanks for asking :-)
-
anónimo
commented
What are top 5 MPs (in terms of usage) used at your SCOM infra?
-Windows Services (DHCP, DNS, etc)
-AD
-SQL
-Dell Open Management
-Hyper-VWhich top 5 MPs critically need version update (agnostic)?
-Windows Services
-Hyper-V
-System Center family
-NetworkWhat are the top 3 issues that arise on MPs (in general)?
-CPU usage
-Many rules auto-enabled
-Update versions for new SWWhat are top 3 workloads for which MPs are missing/unavailable?
-Azure (but MP is in preview)
-Network graphics (like Nagios) -
Leon Laude
commented
1. What are top 5 MPs (in terms of usage) used at your SCOM infra?
• Windows Server
• Active Directory
• DNS
• SharePoint
• Exchange2. Which top 5 MPs critically need version update (agnostic)?
• Hyper-V
• Remote Desktop Services
• Windows Server Update Services (WSUS)
• Exchange (works with newer but could at least be labeled differently to avoid confusion)
• System Center MPs (optional, but would be nice)
• Office 365 (not version agnostic) but really needs to get updated frequently, like the Azure MP3. What are the top 3 issues that arise on MPs (in general)?
• Unnecessary monitors/rules enabled by default
• Thresholds are too low
• Support for newer/newest technology is very slow4. What are top 3 workloads for which MPs are missing/unavailable?
• Monitoring of containers (for example Docker & Kubernetes)
• Proper website/URL monitoring (like in Azure)
• Monitoring of AzureAD SyncSide comment: All management packs with the naming "2016 and 1709 Plus" could be made more clear, (1709 is more referred to Windows clients), use for example 2016 - 2019+".