I'd like to create a global monitoring override for DiskSpace\LowLogVolumeSpaceMonitor.  Is this required to be a minimum size value, percentage or other?

This is what I've tried, but the end result is that I still receive alerts in OpsMgr that the threshold is 190GB:

Add-GlobalMonitoringOverride -Identity DiskSpace\LowLogVolumeSpaceMonitor -ItemType Monitor -PropertyName MonitoringThreshold -PropertyValue 100000 -Duration 30.00:00:00

Add-GlobalMonitoringOverride -Identity DiskSpace\LowLogVolumeSpaceMonitor -ItemType Monitor -PropertyName MonitoringThreshold -PropertyValue 100GB -Duration 30.00

Hi,

According to your description, it seems to be an OpsMgr issue, you should modify the threshold vaule in OpsMgr.

The PropertyValue parameter specifies the new value of the property you are trying to override,not required to be a minimum size value or other.

I recommend that you post this in SCOM forum:

http://social.technet.microsoft.com/Forums/en-US/home?category=systemcenteroperationsmanager

Hope this helps!

Thanks.

Hi,

Any update?

Thanks.

In order to change the threshold for "LowLogVolumeSpaceMonitor" change your powershell command to

Add-ServerMonitoringOverride -Duration 30.00:00:00 -identity dataprotection\lowlogvolumespacemonitor\E: -itemtype Monitor -propertyname MonitoringThreshold -propertyvalue ' 10000 ' -server "ServerName"

• Proposed as answer by Donald White -MSFT Thursday, April 03, 2014 7:51 PM
• Edited by Donald White -MSFT Thursday, April 03, 2014 8:02 PM
• Unproposed as answer by AmbersEd Thursday, April 03, 2014 9:01 PM
• Proposed as answer by Donald White -MSFT Friday, April 04, 2014 1:03 AM

I spoke with members of the product team at MEC this week and this particular monitor can't be changed yet. In the next CU we should be able to change the threshold using a registry key.

The reasoning is that this monitor is vital for health and drives other probes.

Hi,

Management packs in SCOM monitor services, healthset etc on default values for those services or health set. to override the default threshold please use the following powershell cmdlet.

Add-ServerMonitoringOverride -Duration 30.00:00:00 -identity DataProtection\LowLogVolumeSpaceMonitor\E: -ItemType Monitor -PropertyName MonitoringThreshold -PropertyValue '10000' -Server ServerName

Kindly mark this as answer if found helpful. Th

I guarantee you it can. I just changed it for a client today successfully.

Exactly the same powershell command I added here.

I'm testing it now and I'll update with the answer shortly. Thank you.

Any update?

Hi Ambers,

Any update on your testing?

I to am seeing the follow SCOM alert:

10/15/2014 11:25:21 AM Alert description:
Database 'MBX02-DB1' is low on log volume space. 'MBX02-DB1' is low on log
volume space. Current=155.93 GB, Threshold=195.31 GB

I have tried the following cmdlets but still receiving the alerts.  Even after closing them in SCOM.

Add-ServerMonitoringOverride
-ItemType Monitor Server mbx01 -Identity
dataprotection\lowlogvolumespacemonitor\E: -PropertyName MonitoringThreshold
-PropertyValue 50000 -ApplyVersion 15.0.913.22

-AND-

Add-ServerMonitoringOverride
-ItemType Monitor Server mbx01 -Identity
diskspace\lowlogvolumespacemonitor\E: -PropertyName MonitoringThreshold
-PropertyValue 50000 -ApplyVersion 15.0.913.22

Thanks for any information

Ian...

Unfortunately I made the last attempt, saw no difference, and then just increased the drives to the point I don't get the alert anymore.  As I understand talking to others there may have been a CU6 fix that was to address this.  Please don't hold me to the fire on that one as I had also heard a change was in CU5 but my last test was between those two releases.

Hi Ambers,

Thanks for the update!

I am also seeing no difference with these cmdlets running CU5.  Don't really feel comfortable going to CU6 because I am in co-existence with 07 at the moment.

I will continue my search.

Thanks again!

Hi AmbersEd,

Not sure if you found a fix for your issue or not.  I added the following registry key to my mailbox servers and rebooted to resolve my issue.  This key sets a threshold to 50GB

HKLM\Software\Microsoft\ExchangeServer\v15\Replay\Parameters\SpaceMonitorLowSpaceThresholdInMB

REG_DWORD c350 (50000)

Another location that works is below but the first worked for me.

HKLM\Software\Microsoft\ExchangeServer\v15\ActiveMonitoring\Parameters

Good Luck!

• Edited by igibason Wednesday, November 12, 2014 4:03 PM
• Marked as answer by AmbersEd Wednesday, November 12, 2014 4:14 PM

Is there any update on this? I too am trying to modify the  LowLogVolumeSpaceMonitor. The error indicates that it is part of the DiskSpace Healthset, but when I run the Get-MonitoringItemIdentity  on the Diskspace healthset, I get no results. When I run the Get-MonitoringItemIdentity  on the DataProtection healthset, I find the LowLogVolumeSpaceMonitor. I cannot change via a Global Override either. Has anyone found a solution to override this Monitor?