Device associated URL monitors -- problems with maintenance
I have a couple development / testing servers which each have about 9 URL monitors listed under them.
I have reocurring maintenance downtime scheduled for Wednesdays at 4:45am on those devices. Today the maintenance was performed 2 minutes early, so we received several "service down" notifications for the URLs, which btw, on the notification profile URL category is not checked.
So once the maintenance cycle came into effect the device was unmanaged during this period. The maintenance completed at 8am. However once that maintenance cycle was complete, the alarms for all of those URLs never cleared.
Suggestion --- Because the URL monitoring under the devices has proven to be difficult to manage because of all of the other dependant logic taking place in OpManager, could you instead create a device dependancy option on the infrastructure-URL category. That way if a URL is found to be unresponsive, opmanager could check to see if the device it is associated with is "down", and not send out redundant notification?
If that is not possible, how about a service dependancy. So for instance if WWW service is shut off on this development server, I won't have to get 9 notifications for the URLs that are taken down with that service.
I have reocurring maintenance downtime scheduled for Wednesdays at 4:45am on those devices. Today the maintenance was performed 2 minutes early, so we received several "service down" notifications for the URLs, which btw, on the notification profile URL category is not checked.
So once the maintenance cycle came into effect the device was unmanaged during this period. The maintenance completed at 8am. However once that maintenance cycle was complete, the alarms for all of those URLs never cleared.
Suggestion --- Because the URL monitoring under the devices has proven to be difficult to manage because of all of the other dependant logic taking place in OpManager, could you instead create a device dependancy option on the infrastructure-URL category. That way if a URL is found to be unresponsive, opmanager could check to see if the device it is associated with is "down", and not send out redundant notification?
If that is not possible, how about a service dependancy. So for instance if WWW service is shut off on this development server, I won't have to get 9 notifications for the URLs that are taken down with that service.