MONITOR_RULE_TYPE_NONE

As an update to my last post, although generally you'll have to remove the association to disable monitoring and re-add the association to re-enable monitoring (and this is true for the pool), you can also theoretically temporarily disable monitoring by disabling the monitor template. For example, from the CLI, you can do this by "bp monitor http instance disable", or with iControl, use the Monitor::set_template_state (DISABLED). This will disable monitoring of all the affected objects that are using the "http" monitor template.

 

 

Or, as an alternative, you can specifically disable certain monitor instances by using the "bp monitor http instance x.x.x.x:y disable" from the CLI, or using the Monitor::set_instance_state ( ).

 

 

Regards,

 

Loc