Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > ipMonitor > ipMonitor - Knowledgebase Articles > Tokens used in ipMonitor to customize alert notifications

Tokens used in ipMonitor to customize alert notifications

Updated October 9, 2018

Overview

You can customize alerts using ipMonitor tokens to show information about affected monitors. When an alert notification is sent, the tokens are replaced with dynamic content.

Environment

All ipMonitor versions

Detail

Tokens are grouped into three different categories:

  • Monitor-related
  • Alert-related
  • Other

See the tables below for examples of each token type.

For the full list of tokens, see the ipMonitor Administrator Guide.

 

Monitor-related token examples

Token Description Sample Replacement Value
%monitorid% Monitor ID 589478484027
%monitordownlength% Duration of monitor failure 0.80 minutes
%monitortag[contact]% Value of monitor tag 'contact' Brian Smith, cell: 555-9876

Alert-related token examples

Token Description Sample Replacement Value
%actionname% Name of action E-mail Internal Helpdesk
%rfc822date% Date in RFC 822 format Tue, 02 Mar 2004 20:25:28 -0500
%actiontag[emerg_contact]% Value of action tag
'emerg_contact'
Brian Smith, cell: 555-9876

Other token examples

Token Description Sample Replacement Value
%instancename% ipMonitor instance name ipMonitor Server [PRIMARY]
%processavg ipMonitor CPU load 0.40%
%ipmdriveavail% ipMonitor available drive space 26.15 GB
Last modified

Tags

Classifications

Public