Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Decrease CPU resource usage when monitors fail

Decrease CPU resource usage when monitors fail

Table of contents
No headers

There is a Global Behavior Modifier which will disable the verification of parent groups. As a result, the Dependency of the parent ID will be the only one verified and Dependencies for groups higher up the branch will not be observed or alerted on.

To enable this:

  • 1. Go to Configuration Tab.
  • 2. Click System Settings.
  • 3. Click Global Behavior Modifiers option.
  • 4. Click Add
  • 5. Enter the following values: Name: alerting.for.depth.enable Value: 0
  • 6. Click OK.

This will disable notifications for Alerts which contain the following:

  • Groups within Groups
  • SmartGroups

Items within Alerts will need to be replaced with one of the following:

  • Devices
  • Groups of Monitors
  • Monitors
  • After completing these steps, CPU usage should remain low when a large amount of Monitors fail.
Last modified

Tags

Classifications

Public