Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Database Performance Analyzer (DPA) > Instance availability alert does not trigger

Instance availability alert does not trigger

Created by Jamin Walters, last modified by Rodim Suarez on Mar 08, 2017

Views: 44 Votes: 0 Revisions: 4

Updated March 8, 2017

Overview

The database instance availability alert is configured for a short interval such as 1 minute. When the instance goes down, the alert is not firing or does not trigger for a while after the instance is not connected. 

Environment

All DPA versions

Cause 

This alert had a history of alerting and giving a false positive. It is based on us simply connecting to the instance but a few things have to be true for it to fire.

The monitor has to be on but, connection to the server is not working.

Then we also have a tolerance in the code where we sample every 90 seconds by default and if we have 3 attempts that fail 90 seconds apart we alert.

Resolution

This alert is configurable. You can set the interval that we pull as well as the number of fails for a pull.

Go to Options > Administration tab > Advanced Options > DB instance Options tab > select the instance you want to change from the drop down menu.

ALERT_CONNECTION_INTERVAL - default is 90 
ALERT_CONNECTION_ATTEMPTS - default is 3

Tune these settings to find the level of alert that works for your environment. This about finding the balance between false alerts and not alerting soon enough.

 

 

Last modified
19:00, 7 Mar 2017

Tags

Classifications

Public