Comtrade has recently re-branded to HYCU and are hard at work and have updated the Nutanix and F5 MPs to be fully supported by SCOM 1801
Comtrade has recently re-branded to HYCU and are hard at work and have updated the Nutanix and F5 MPs to be fully supported by SCOM 1801
This is a summary of the wave of Management Packs that were released in October 2017. Information and download location in the links provided:
DHCP 2016 MP v10.0.9.0 – here
DHCP 2012 MP v6.0.7307.0 – here
SQL 2017+ MP – here
If you know of any other Management Packs that have been released recently that I may have missed leave me a note in the comments and I’ll add them
This is a summary of the wave of Management Packs that were released in December 2016. Information and download location in the links provided:
Windows Server MP v10.0.8.0 – here
WS-Management and SMASH Device Discovery MP v7.0.8707.0 – here
Windows Server 2016 AD, ADFS and DNS MPs – here
If you know of any other Management Packs that have been released recently that I may have missed leave me a note in the comments and I’ll add them
This is a summary of the wave of Management Packs that were released in August 2016. Information and download location in the links provided:
SCCM MP v5.00.8239.1009 – here
SQL Server MP (Community Technical Preview 1) v6.7.3.0 – here
UNIX and Linux MPs v7.5.1060.0 – here
If you know of any other Management Packs that have been released recently that I may have missed leave me a note in the comments and I’ll add them
This is a summary of the wave of Management Packs that were released in July 2016. Information and download location in the links provided:
NiCE Oracle MP 4.00 – here
Microsoft Azure (Technical Preview) MP v1.3.22.0 – here
Windows Server Operating System MP v6.0.7316.0 – here
If you know of any other Management Packs that have been released recently that I may have missed leave me a note in the comments and I’ll add them
A new version of the Azure technical preview MP has been released you can get version 1.3.18.0 here
New in this version
I’ve made some amendments to the Database Status Report that I posted about in 2015, Version 4 is now more streamlined and cleaner.
Sample screenshot:
Feel free to contact me for information on this report or the questions about the RDL.
I would be interested to hear from anyone who has any comments or suggestions on this report or ideas for future ones.
This posting is a continuation of my basics series, this one deals with Understanding Grooming and Aggregation, two very important concepts which can have great impact on your environment if they are not functioning properly.
First you need to understand the different between these two concepts, at their most basic, Grooming is the method where data older then a specific period, called the retention period, is deleted. Aggregation is the method where raw data, which is collected on short intervals i.e. 5 minutes, are averaged into hourly and daily time intervals used for reporting purposes.
The Operations Database
A stored procedure, called p_PartitioningandGrooming is run by a SCOM rule on a once a day schedule. The retention settings for each data type can be set in the console under Administration > Settings > Database Grooming.
You can see the history of the OpsDB grooming jobs with the following SQL query:
select * from InternalJobHistory order by InternalJobHistoryId desc
A Status of 1 indicates a successful completion.
The Operations Data-warehouse
The Data Warehouse is more complex, you cannot change data retention settings from the console, they exist in a table called StandardDatasetAggregation, which contains the grooming and aggregation retention periods, intervals and other related data.
Data in the DW database moves through several tables as part of the aggregations process as the data is collected it is written to a Raw Data table, from there is will move to a Staging table where it will be aggregated and then moved to a relevant aggregated data table (Hourly / Daily) where it will be available to the reporting services.
Then once the data in these tables is older then the data retention period it will be groomed out of the database.
So why is it important for aggregation to work?
Reports use the hourly and daily data in order to generate, this means that if your aggregations are not working or slow there will be gaps in your reporting. Example below:
And there you have it. the basics behind aggregation and grooming, I hope this has been informative.