Update 18 Dec 2023 – Solution retired in 2021 with OMS sunset.
https://github.com/uglide/azure-content/blob/master/articles/log-analytics/log-analytics-add-solutions.md Repository archived by the owner on Feb 1, 2021. It is now read-only.
Do you know what your HyperV hosts are doing?
Not a HyperV fan, there’s a VMWare solution also here
Documentation https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-capacity
https://github.com/uglide/azure-content/blob/master/articles/log-analytics/log-analytics-capacity.md
Capacity dashboard
Details
Setting up OMS Capacity and Performance
Already have the dashboard setup? Perhaps this will help troubleshoot
Do you have network connectivity, or is a proxy required?
Troubleshooting dashboard
Firewall https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-proxy-firewall
Windows Agents https://docs.microsoft.com/en-us/azure/log-analytics/log-analytics-windows-agents
Verify Operations Manager event log on local agent, then filter for error events and/or EventID 4506. Look for dates/times to see when events started.
Example Event ID 4506 details the Capacity and Performance Solution, citing ‘Microsoft.IntelligencePacks.CapacityPerformance.Collector’.
Additional options
- Search LAW (Log Analytics workspace) logs
2. Verify no proxy is set up (unless your network requires this)
3. 4506’s result from too many workflows sending data from MS to DB’s (OpsMgr and DW). Additionally, 4506 events can be communication issues from MS to DB server(s). Lastly, use TLS1.2 configuration as a best practice to enforce encryption from MS to SQL communication. Beyond encryption, TLS may be a culprit if AlwaysOn or SQL clusters are involved, particularly as the SCOM console connections fail as SDK cannot talk with SQL side. See Kevin Holman’s blog for additional TLS1.2 information and setup.
TLS blog https://kevinholman.com/2018/05/06/implementing-tls-1-2-enforcement-with-scom/
Documentation
Learn article https://learn.microsoft.com/en-us/answers/questions/212007/scom-errors-no-data-in-summary-performance-dashboa
TechNet blog https://social.technet.microsoft.com/Forums/ie/en-US/10b38121-b0e1-43ec-bf3a-d22ae9ef0220/event-4506-data-was-dropped-due-to-too-much-outstanding-data-in-rule
MS RMSe https://www.system-center.me/opsmgr/event-4506-and-new-root-management-server-rms-management-server-ms/