Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

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

Updated September 21, 2018

Overview

There is a global behavior modifier that 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.

This article describes how to disable notifications for some alerts replace items within alerts with new options.

Environment

All ipMonitor versions

Steps

After completing these steps, CPU usage should remain low when a large amount of Monitors fail.

  1. Log in to ipMonitor.
  2. Click the Configuration Tab.
  3. Click System Settings.
  4. Click the Global Behavior Modifiers option.
  5. Click Add.
  6. Enter the following values:
    Name: alerting.for.depth.enable Value: 0
  7. 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
Last modified

Tags

Classifications

Public