none
Монитор StorageLogicalDriveSpaceMonitor в состояние Degraded RRS feed

  • Вопрос

  • Добрый день коллеги.

    На Exchange сервер монитор StorageLogicalDriveSpaceMonitor находится в состоянии в состояние Degraded

    Хотя свободного пространства 46 Гб, из 99 Гб.

    Как правильно изменить пороговое значение для данного монитора? 

    Использовать Add-GlobalMonitoringOverride не вариант потому как он задает пороговое значение на время, и не понятно какая размерность параметра.

    Add-GlobalMonitoringOverride -Identity MailboxSpace\StorageLogicalDriveSpaceMonitor -PropertyName MonitoringThreshold -PropertyValue XX -Duration XX.XX:XX:XX




    <a href="http://www.techdays.in.ua/speaker/141957.html">Мои видео доклады</a><br/> <a href="http://eugenpavlenko.wordpress.com">Мой блог</a>

    1 августа 2013 г. 7:41

Ответы

  • I hope you are able to understand English:

    We also had this error after CU2 in our test environment, to resolve this we ran this to set an override on the server for 60 Days, to set the limit to be 50GB (instead of 100GB default)

    Add-ServerMonitoringOverride -Duration 60.00:00:00 -Identity MailboxSpace\StorageLogicalDriveSpaceMonitor\E: -ItemType Monitor -PropertyName MonitoringThreshold -PropertyValue '50,000.00' -Server servername

    to find the related monitor we used

    Get-MonitoringItemIdentity MailboxSpace -Server servername

    and to see the options that we could set we used

    Get-MonitoringItemHelp -Server servername -Identity MailboxSpace\StorageLogicalDriveSpaceMonitor\E: |fl *

    We were not able to find any documentation that defines how to set the property value, so it was a bit of trial and error. In the end we used the same value format that was in the related performance counter (shown in the event log entry / scom notification) - we will assume that this will be the same for other performance counter related monitors

    Alert description: Database drive E: is below critical threshold on space for last 00:15:00. Threshold: 100GB Error: The performance counter '\\servername\LogicalDisk(E:)\Free Megabytes' sustained a value of '55,169.00', for the '15' minute(s) interval starting at '7/31/2013 5:17:00 PM'. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger. Instance:e:

    • Изменено Kevin Rowlands 2 августа 2013 г. 7:57 loss of formating
    • Помечено в качестве ответа Eugen Pavlenko 5 августа 2013 г. 6:54
    2 августа 2013 г. 7:55

Все ответы

  • I hope you are able to understand English:

    We also had this error after CU2 in our test environment, to resolve this we ran this to set an override on the server for 60 Days, to set the limit to be 50GB (instead of 100GB default)

    Add-ServerMonitoringOverride -Duration 60.00:00:00 -Identity MailboxSpace\StorageLogicalDriveSpaceMonitor\E: -ItemType Monitor -PropertyName MonitoringThreshold -PropertyValue '50,000.00' -Server servername

    to find the related monitor we used

    Get-MonitoringItemIdentity MailboxSpace -Server servername

    and to see the options that we could set we used

    Get-MonitoringItemHelp -Server servername -Identity MailboxSpace\StorageLogicalDriveSpaceMonitor\E: |fl *

    We were not able to find any documentation that defines how to set the property value, so it was a bit of trial and error. In the end we used the same value format that was in the related performance counter (shown in the event log entry / scom notification) - we will assume that this will be the same for other performance counter related monitors

    Alert description: Database drive E: is below critical threshold on space for last 00:15:00. Threshold: 100GB Error: The performance counter '\\servername\LogicalDisk(E:)\Free Megabytes' sustained a value of '55,169.00', for the '15' minute(s) interval starting at '7/31/2013 5:17:00 PM'. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger. Instance:e:

    • Изменено Kevin Rowlands 2 августа 2013 г. 7:57 loss of formating
    • Помечено в качестве ответа Eugen Pavlenko 5 августа 2013 г. 6:54
    2 августа 2013 г. 7:55
  • Здравствуйте Eugen Pavlenko!
    Вам удалось решить проблему с помощью вышеуказанного совета? 
    Kevin, thanks for providing your solution!


    Уважаемые участники форума. У меня к Вам просьба: если какой-нибудь из ответов помог Вам решить Вашу проблему, пожалуйста, не забывайте отмечать его. Таким образом, Вы поможете и другим пользователям, у которых возникла схожая проблема! Спасибо!

    5 августа 2013 г. 6:12
    Модератор
  • I hope you are able to understand English:

    We also had this error after CU2 in our test environment, to resolve this we ran this to set an override on the server for 60 Days, to set the limit to be 50GB (instead of 100GB default)

    Add-ServerMonitoringOverride -Duration 60.00:00:00 -Identity MailboxSpace\StorageLogicalDriveSpaceMonitor\E: -ItemType Monitor -PropertyName MonitoringThreshold -PropertyValue '50,000.00' -Server servername

    to find the related monitor we used

    Get-MonitoringItemIdentity MailboxSpace -Server servername

    and to see the options that we could set we used

    Get-MonitoringItemHelp -Server servername -Identity MailboxSpace\StorageLogicalDriveSpaceMonitor\E: |fl *

    We were not able to find any documentation that defines how to set the property value, so it was a bit of trial and error. In the end we used the same value format that was in the related performance counter (shown in the event log entry / scom notification) - we will assume that this will be the same for other performance counter related monitors

    Alert description: Database drive E: is below critical threshold on space for last 00:15:00. Threshold: 100GB Error: The performance counter '\\servername\LogicalDisk(E:)\Free Megabytes' sustained a value of '55,169.00', for the '15' minute(s) interval starting at '7/31/2013 5:17:00 PM'. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger. Instance:e:

    Thx for this solution. 

    <a href="http://www.techdays.in.ua/speaker/141957.html">Мои видео доклады</a><br/> <a href="http://eugenpavlenko.wordpress.com">Мой блог</a>

    5 августа 2013 г. 6:54