---
title: Testing alerts and alarms
description: Configure and test system alerts and alarms.
component: pingdirectory
version: 9.3
page_id: pingdirectory:pingdatametrics_server_administration_guide:pd_met_test_alerts_alarms
canonical_url: https://docs.pingidentity.com/pingdirectory/9.3/pingdatametrics_server_administration_guide/pd_met_test_alerts_alarms.html
revdate: September 13, 2023
section_ids:
  about-this-task: About this task
  steps: Steps
  example: Example:
  example-2: Example:
---

# Testing alerts and alarms

Configure and test system alerts and alarms.

## About this task

After configuring your alarms and alert handlers, verify that the server takes the appropriate action when an alarm state changes by manually increasing the severity of a gauge. Alarms and alerts can be verified with the `status` tool.

## Steps

1. Configure a gauge with `dsconfig` and set the `override-severity` property to critical.

   ### Example:

   The following example uses the CPU Usage (Percent) gauge.

   ```shell
   $ dsconfig set-gauge-prop \
     --gauge-name "CPU Usage (Percent)" \
     --set override-severity:critical
   ```

2. Run the `status` tool to verify that an alarm was generated with corresponding alerts.

   |   |                                                                                                                           |
   | - | ------------------------------------------------------------------------------------------------------------------------- |
   |   | The status tool provides a summary of the server's current state with key metrics and a list of recent alerts and alarms. |

   ### Example:

   The sample output has been shortened to show just the alarms and alerts information.

   ```shell
   $ bin/status
   ```

   ```
   --- Administrative Alerts ---
   Severity : Time : Message
   ---------:----------------:-----------------------------------------------
   -------
   Error : 11/Aug/2016 : Alarm [CPU Usage (Percent). Gauge CPU Usage
   (Percent)
   						: 15:41:00 -0500 : for Host System has
   						: : a current value of '18.583333333333332'.
   						: : The severity is currently OVERRIDDEN in the
   						: : Gauge's configuration to 'CRITICAL'.
   						: : The actual severity is: The severity is
   						: : currently 'NORMAL', having assumed this
   severity
   						: : Mon Aug 11 15:41:00 CDT 2016. If CPU use is
   high,
   						: : check the server's current workload and make
   any
   						: : needed adjustments. Reducing the load on the
   system
   						: : will lead to better response times.
   						: : Resource='Host System']
   						: : raised with critical severity
   Shown are alerts of severity [Info,Warning,Error,Fatal] from the past 48
   hours
   Use the --maxAlerts and/or --alertSeverity options to filter this list
   						--- Alarms ---
   Severity : Severity : Condition : Resource : Details
   	   : Start Time : : :
   ---------:------------:-----------:-------------:-------------------------
   --
   Critical : 11/Aug/2016: CPU Usage : Host System : Gauge CPU Usage
   (Percent) for
   						: 15:41:00 : (Percent) : : Host System
   						: -0500 : : : has a current value of
   						: : : : '18.785714285714285'.
   						: : : : The severity is
   currently
   						: : : : 'CRITICAL', having
   assumed
   						: : : : this severity Mon Aug 11
   						: : : : 15:49:00 CDT 2016. If
   CPU use
   						: : : : is high, check the
   server's
   						: : : : current workload and
   make any
   						: : : : needed adjustments.
   Reducing
   						: : : : the load on the system
   will
   						: : : : lead to better response
   times
   Shown are alarms of severity [Warning,Minor,Major,Critical
   Use the --alarmSeverity option to filter this list
   ```