cancel
Showing results for 
Search instead for 
Did you mean: 

Maintenance Mode - Best Practice

Anon
Community Manager

Maintenance Mode - Best Practice

We have at times needed to stop the email alerting from prognosis from sending us a ton of email when we are updating servers.. what is the best practice method for configuring a maintenance mode. We don't have a standardized start / stop date. For us, a best method would be a start / stop button. even if this is per collector.
3 REPLIES 3
Shoaib_Dilawar
12 Sherpa

Re: Maintenance Mode - Best Practice

Hi Jon,

most customers have their own best practices around maintenance mode. From what you mentioned, we can come up with a solution that can stop/start individual collector from WebUI or can remove (and backup) entries from a running configuration to make it empty and restore it after maintenance window is over. We may also configure it such that it takes in a list of collectors/configurations to have a 1 click button into and out of maintenance window. A couple of mock ups attached.

This is something you would benefit from? We can set time to discuss further.status01.png

status02.png


If my reply answered your question please click on the 'Accept as Solution' button to help others find the answer.
Thanks,
Shoaib
Shoaib_Dilawar
12 Sherpa

Re: Maintenance Mode - Best Practice

 

If my reply answered your question please click on the 'Accept as Solution' button to help others find the answer.
Thanks,
Shoaib
KabiramKulasin
05 Base Camper

Re: Maintenance Mode - Best Practice

HI Jon, as Shoaib mentions there are different ways to achieve what you are looking for. Two quick options you have out of the box would be:


---------------------------------------------------------------------------------------------------------------------------------------------
1) Start an Empty DISPMAN Config - this will disable email alerting globally per monitoring node.
---------------------------------------------------------------------------------------------------------------------------------------------
1) From the Thick Client, open the DISPMAN config up and save a backup *** VERY IMPORTANT ***
2) From the Thick Client, create a new Configuration document of type DISPMAN and keep it empty & save it
- You just have to create this once and reuse it for next time
3) From the Thick Client, start the empty DISPMAN config you created when you are ready for maintenance
- All email alerting from now on will be aborted & you will not receive emails (alerts will still show in the Prognosis Alert Central Dashboards)
4) After maintenance, start the backup DISPMAN from step 1.
- Any new alerts generated will use the correct DISPMAN settings now and you will get email alerts again.



---------------------------------------------------------------------------------------------------------------------------------------------
2) Stop & Start Thresholds
---------------------------------------------------------------------------------------------------------------------------------------------
1) From the WebUI Admin Page there is a 'Thresholds' section with option to 'STOP' a ruining threshold.
- This will disable alerting for all devices that the threshold is monitoring
2) After Maintenance, from the same WebUI Admin Page there is the 'START' option next to the threshold you can use to enable the threshold again

You don't have a lot of control from the above two methods but they are quick to do & work out of box.

Hope that helps!