Hmmm…. Thanks. I may have to do a combination of both for some groups of servers. We have a wide and varying array of space utilization from multi-TB disks to some that maybe a few GB. Well, we’ll see where the mob makes us go. On some issues I can mandate and management will back me. On others management doesn’t care so I have to look out for my own survival needs first 😊
From: Kevin Holman Sent: Thursday, January 29, 2015 2:11 PM To: [email protected] Below: From: [email protected] [mailto:[email protected]] On Behalf Of Steven Peck Sent: Thursday, January 29, 2015 1:52 PM To: [email protected] Subject: Re: [msmom] RE: Disk Free Space Alerting Complicating this though… wasn’t this monitor a combined AND so to alert you needed to exceed TWO thresholds of both % and MB? Isn’t that what lead to the split up in the two monitors below the highlighted one? (Which are default disabled). [KH] That is correct. I was trying to ignore those. J I don’t like them. I LOVE the monitor style that accounts for both % and MB free, because it allows you to set thresholds that work for a wide range of disk sizes easily. In implementing the new environment we’re trying to figure out which we want to use. Also you mention a new base MP coming out… does this imply yet another behavior change? [KH] Personally, for any environment, I would use the one that is enabled by default, it is a solid monitor that works the way SCOM has always worked. The NEW based OS MP’s coming out only contain some bug fixes for some perf collection rules and mount point discovery. I hope we don’t make ANY more changes to the free space monitoring again…. at this point. (For another history lesson….. the REASON those two disabled monitors that I like to ignore were created, was to satisfy yet another customer request – to make all disk space monitoring the same (logical disks, cluster disks, CSV’s) and to break them out because SOME customers wanted a “%” only monitor, or a MB free only monitor. This is simply a case of trying to respond and please all the customers, but creating confusion in the process) From: Kevin Holman Sent: Thursday, January 29, 2015 9:34 AM To: [email protected] This is going to be a bit confusing, but bear with me, as it will cover the history. I had planned a blog posting on this but its just a lot to write….. and might confuse people more than it helps. You are obviously running an old version of the Base OS MP. The LATEST versions of the Base OS MP’s changed back to a non-consecutive samples monitor, which runs once per hour, and is immediate. Here is some history: The original base OS MP’s for years, all though SCOM 2007 era, ran once per hour, and checked free space in % and MB free, and had a nice alert which included these values. It was NOT a consecutive samples monitor. Life was good. Then, based on customer demand filed via requests – the free space monitor was changed, to a consecutive samples monitor. Customers asked for multiple samples to weed out transient issues where disks filled but then were cleared quickly. There were two mistakes made when this was done: 1. The number of samples was not exposed via override, only frequency 2. The alert description was changed to not contain the %free and MB free. Because of this, there was public outcry, and I wrote the addendum MP which put things back to how they used to be: http://blogs.technet.com/b/kevinholman/archive/2014/02/05/opsmgr-logical-disk-free-space-alerts-don-t-show-percent-and-mb-free-values-in-the-alert-description-updated-for-server-2012.aspx However, based on customer requests – this was put back into the Base OS MP’s…. but instead of “replacing” the existing monitor with the old one back again, they added a NEW monitor, which is an exact copy of my addendum monitor, then disabled the existing monitor. So, where are we now: The red arrow points to the old monitor (consecutive samples) now disabled. The highlighted is the “new” monitor which goes back to how it was for years. You just need to update to the new MP’s. J However! This also means you need to re-do any overrides you had set previously on the old monitor, as they won’t apply anymore to the new one. Also – keep in mind there is a new Base OS MP coming out VERY soon, to replace the one that got pulled. Sorry, wish there was a simpler story to all this. J From: [email protected] [mailto:[email protected]] On Behalf Of Pete Hakesley Sent: Thursday, January 29, 2015 9:13 AM To: MSMOM ([email protected]) Subject: [msmom] Disk Free Space Alerting All, The Logical Disk Monitor has all the normal parameters visible and able to be overridden however number of sample is not visible. We have a customer who wants us to monitor disk space using a number of sample = 1 i.e. when exceeded then raise an alert. Does anyone know if Microsoft plan to make this visible? I know I can change the frequency but I think this is dangerous as it put more load on the SCOM platform / agent especially if we were to implement a high frequency across many servers. IN this customers case approx. 200 servers all with 3 to 10 drives. Worst case 2,000 Logical disks!!! Mgt Pack Code. <UnitMonitor ID="Microsoft.Windows.Server.2008.LogicalDisk.FreeSpace" Accessibility="Public" Enabled="true" Target="Server2008!Microsoft.Windows.Server.2008.LogicalDisk" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Microsoft.Windows.Server.2008.FreeSpace.Monitortype" ConfirmDelivery="true"> <Category>Custom</Category> <AlertSettings AlertMessage="Microsoft.Windows.Server.2008.LogicalDisk.FreeSpace.AlertMessage"> <AlertOnState>Warning</AlertOnState> <AutoResolve>true</AutoResolve> <AlertPriority>Normal</AlertPriority> <AlertSeverity>MatchMonitorHealth</AlertSeverity> <AlertParameters> <AlertParameter1>$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$</AlertParameter1> <AlertParameter2>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</AlertParameter2> </AlertParameters> </AlertSettings> <OperationalStates> <OperationalState ID="UnderWarningThresholds" MonitorTypeStateID="UnderWarningThresholds" HealthState="Success" /> <OperationalState ID="OverWarningUnderErrorThresholds" MonitorTypeStateID="OverWarningUnderErrorThresholds" HealthState="Warning" /> <OperationalState ID="OverErrorThresholds" MonitorTypeStateID="OverErrorThresholds" HealthState="Error" /> </OperationalStates> <Configuration> <ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName> <DiskLabel>$Target/Property[Type="Windows!Microsoft.Windows.LogicalDevice"]/DeviceID$</DiskLabel> <IntervalSeconds>900</IntervalSeconds> <SystemDriveWarningMBytesThreshold>500</SystemDriveWarningMBytesThreshold> <SystemDriveWarningPercentThreshold>10</SystemDriveWarningPercentThreshold> <SystemDriveErrorMBytesThreshold>300</SystemDriveErrorMBytesThreshold> <SystemDriveErrorPercentThreshold>5</SystemDriveErrorPercentThreshold> <NonSystemDriveWarningMBytesThreshold>2000</NonSystemDriveWarningMBytesThreshold> <NonSystemDriveWarningPercentThreshold>10</NonSystemDriveWarningPercentThreshold> <NonSystemDriveErrorMBytesThreshold>1000</NonSystemDriveErrorMBytesThreshold> <NonSystemDriveErrorPercentThreshold>5</NonSystemDriveErrorPercentThreshold> <NumSamples>4</NumSamples> </Configuration> </UnitMonitor> Peter Hakesley | Monitoring & Automation Technical Lead Engineer, Data Centre Services t: +44(0)845 155 6556 ext: 4006 e: [email protected] | w: www.scc.com a: SCC, CV1, Cole Valley, 20 Westwood Avenue, Tyseley, Birmingham B11 3RZ
