Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

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

Tokens used in ipMonitor to customize alert notifications

Table of contents

Overview

You can customize alerts using ipMonitor tokens to show information on 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

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

 

Examples of monitor-related tokens:

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

Examples of alert-related tokens:

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

Examples of other tokens:

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
02:33, 16 Mar 2017

Tags

Classifications

Public