- 1 Welcome to Vunetrix Network Monitor+
- 2 Quick Start Guide+
- 3 Installing the Software+
- 4 Understanding Basic Concepts+
- 5 Ajax Web Interface—Basic Procedures+
- 5.1 Login
- 5.2 SSL Certificate Warning
- 5.3 General Layout
- 5.4 Sensor States
- 5.5 Review Monitoring Data
- 5.6 Compare Sensors
- 5.7 Historic Data Reports
- 5.8 Similar Sensors
- 5.9 Object Settings
- 5.10 Alarms
- 5.11 Logs
- 5.12 Tickets
- 5.13 Working with Table Lists
- 5.14 Object Selector
- 5.15 Priority and Favorites
- 5.16 Pause
- 5.17 Context Menus
- 5.18 Hover Popup
- 5.19 Main Menu Structure
- 6 Ajax Web Interface—Device and Sensor Setup+
- 6.1 Auto-Discovery
- 6.2 Create Objects Manually+
- 6.3 Manage Device Tree
- 6.4 Root Group Settings
- 6.5 Probe Settings
- 6.6 Group Settings
- 6.7 Device Settings
- 6.8 Sensor Settings+
- 6.8.1 List of Available Sensor Types
- 6.8.2 Active Directory Replication Errors Sensor
- 6.8.3 ADO SQL Sensor
- 6.8.4 Amazon CloudWatch Sensor
- 6.8.5 AVM FRITZ!Box WAN Interface Sensor
- 6.8.6 Cisco IP SLA Sensor
- 6.8.7 Citrix XenServer Host Sensor
- 6.8.8 Citrix XenServer Virtual Machine Sensor
- 6.8.9 Cluster Probe Health Sensor
- 6.8.10 Core Health Sensor
- 6.8.11 Dell PowerVault MDi Sensor
- 6.8.12 DHCP Sensor
- 6.8.13 DNS Sensor
- 6.8.14 Enterprise Virtual Array Sensor
- 6.8.15 Event Log (Windows API) Sensor
- 6.8.16 Exchange Backup (Powershell) Sensor
- 6.8.17 Exchange Database (Powershell) Sensor
- 6.8.18 Exchange Mailbox (Powershell) Sensor
- 6.8.19 Exchange Mail Queue (Powershell) Sensor
- 6.8.20 Exchange Public Folder (Powershell) Sensor
- 6.8.21 EXE/Script Sensor
- 6.8.22 EXE/Script Advanced Sensor
- 6.8.23 File Sensor
- 6.8.24 File Content Sensor
- 6.8.25 Folder Sensor
- 6.8.26 FTP Sensor
- 6.8.27 FTP Server File Count Sensor
- 6.8.28 Google Analytics Sensor
- 6.8.29 HTTP Sensor
- 6.8.30 HTTP Advanced Sensor
- 6.8.31 HTTP Apache ModStatus PerfStats Sensor
- 6.8.32 HTTP Apache ModStatus Totals Sensor
- 6.8.33 HTTP Content Sensor
- 6.8.34 HTTP Full Web Page Sensor
- 6.8.35 HTTP Push Count Sensor
- 6.8.36 HTTP Push Data Sensor
- 6.8.37 HTTP Push Data Advanced Sensor
- 6.8.38 HTTP SSL Certificate Expiry Sensor
- 6.8.39 HTTP Transaction Sensor
- 6.8.40 HTTP XML/REST Value Sensor
- 6.8.41 Hyper-V Cluster Shared Volume Disk Free Sensor
- 6.8.42 Hyper-V Host Server Sensor
- 6.8.43 Hyper-V Virtual Machine Sensor
- 6.8.44 Hyper-V Virtual Network Adapter Sensor
- 6.8.45 Hyper-V Virtual Storage Device Sensor
- 6.8.46 IMAP Sensor
- 6.8.47 INI File Content Check Sensor
- 6.8.48 IP on DNS Blacklist Sensor
- 6.8.49 IPFIX Sensor
- 6.8.50 IPFIX (Custom) Sensor
- 6.8.51 jFlow V5 Sensor
- 6.8.52 jFlow V5 (Custom) Sensor
- 6.8.53 LDAP Sensor
- 6.8.54 Microsoft SQL Sensor
- 6.8.55 MySQL Sensor
- 6.8.56 NetFlow V5 Sensor
- 6.8.57 NetFlow V5 (Custom) Sensor
- 6.8.58 NetFlow V9 Sensor
- 6.8.59 NetFlow V9 (Custom) Sensor
- 6.8.60 Oracle SQL Sensor
- 6.8.61 Packet Sniffer Sensor
- 6.8.62 Packet Sniffer (Custom) Sensor
- 6.8.63 Passive Application Performance Sensor
- 6.8.64 PerfCounter Custom Sensor
- 6.8.65 PerfCounter IIS Application Pool Sensor
- 6.8.66 Ping Sensor
- 6.8.67 Ping Jitter Sensor
- 6.8.68 Pingdom Sensor
- 6.8.69 POP3 Sensor
- 6.8.70 POP3 Email Count Sensor
- 6.8.71 Port Sensor
- 6.8.72 Port Range Sensor
- 6.8.73 Probe Health Sensor
- 6.8.74 QoS (Quality of Service) One Way Sensor
- 6.8.75 QoS (Quality of Service) Round Trip Sensor
- 6.8.76 RADIUS Sensor
- 6.8.77 RDP (Remote Desktop) Sensor
- 6.8.78 SCVMM Host Sensor
- 6.8.79 SCVMM Virtual Machine Sensor
- 6.8.80 Sensor Factory Sensor
- 6.8.81 sFlow Sensor
- 6.8.82 sFlow (Custom) Sensor
- 6.8.83 SFTP Secure File Transfer Protocol Sensor
- 6.8.84 Share Disk Free Sensor
- 6.8.85 SIP Options Ping Sensor
- 6.8.86 SMTP Sensor
- 6.8.87 SMTP&IMAP Round Trip Sensor
- 6.8.88 SMTP&POP3 Round Trip Sensor
- 6.8.89 SNMP APC Hardware Sensor
- 6.8.90 SNMP Cisco ADSL Sensor
- 6.8.91 SNMP Cisco ASA VPN Connections Sensor
- 6.8.92 SNMP Cisco ASA VPN Traffic Sensor
- 6.8.93 SNMP Cisco ASA VPN Users Sensor
- 6.8.94 SNMP Cisco CBQoS Sensor
- 6.8.95 SNMP Cisco System Health Sensor
- 6.8.96 SNMP Cisco UCS Chassis Sensor
- 6.8.97 SNMP Cisco UCS Physical Disk Sensor
- 6.8.98 SNMP Cisco UCS System Health Sensor
- 6.8.99 SNMP CPU Load Sensor
- 6.8.100 SNMP Custom Sensor
- 6.8.101 SNMP Custom String Sensor
- 6.8.102 SNMP Dell Hardware Sensor
- 6.8.103 SNMP Dell PowerEdge Physical Disk Sensor
- 6.8.104 SNMP Dell PowerEdge System Health Sensor
- 6.8.105 SNMP Disk Free Sensor
- 6.8.106 SNMP GSA System Health Sensor
- 6.8.107 SNMP Hardware Status Sensor
- 6.8.108 SNMP HP LaserJet Hardware Sensor
- 6.8.109 SNMP HP ProLiant Logical Disk Sensor
- 6.8.110 SNMP HP ProLiant Memory Controller Sensor
- 6.8.111 SNMP HP ProLiant Network Interface Sensor
- 6.8.112 SNMP HP ProLiant Physical Disk Sensor
- 6.8.113 SNMP HP ProLiant System Health Sensor
- 6.8.114 SNMP IBM System X Logical Disk Sensor
- 6.8.115 SNMP IBM System X Physical Disk Sensor
- 6.8.116 SNMP IBM System X Physical Memory Sensor
- 6.8.117 SNMP IBM System X System Health Sensor
- 6.8.118 SNMP interSeptor Pro Environment Sensor
- 6.8.119 SNMP LenovoEMC Physical Disk Sensor
- 6.8.120 SNMP LenovoEMC System Health Sensor
- 6.8.121 SNMP Library Sensor
- 6.8.122 SNMP Linux Disk Free Sensor
- 6.8.123 SNMP Linux Load Average Sensor
- 6.8.124 SNMP Linux Meminfo Sensor
- 6.8.125 SNMP Linux Physical Disk Sensor
- 6.8.126 SNMP Memory Sensor
- 6.8.127 SNMP NetApp Disk Free Sensor
- 6.8.128 SNMP NetApp Enclosure Sensor
- 6.8.129 SNMP NetApp I/O Sensor
- 6.8.130 SNMP NetApp License Sensor
- 6.8.131 SNMP NetApp Logical Unit Sensor
- 6.8.132 SNMP NetApp Network Interface Sensor
- 6.8.133 SNMP NetApp System Health Sensor
- 6.8.134 SNMP Poseidon Environment Sensor
- 6.8.135 SNMP QNAP Logical Disk Sensor
- 6.8.136 SNMP QNAP Physical Disk Sensor
- 6.8.137 SNMP QNAP System Health Sensor
- 6.8.138 SNMP RMON Sensor
- 6.8.139 SNMP SonicWALL System Health Sensor
- 6.8.140 SNMP SonicWALL VPN Traffic Sensor
- 6.8.141 SNMP Synology Logical Disk Sensor
- 6.8.142 SNMP Synology Physical Disk Sensor
- 6.8.143 SNMP Synology System Health Sensor
- 6.8.144 SNMP System Uptime Sensor
- 6.8.145 SNMP Traffic Sensor
- 6.8.146 SNMP Trap Receiver Sensor
- 6.8.147 SNMP Windows Service Sensor
- 6.8.148 SNTP Sensor
- 6.8.149 SSH Disk Free Sensor
- 6.8.150 SSH INodes Free Sensor
- 6.8.151 SSH Load Average Sensor
- 6.8.152 SSH Meminfo Sensor
- 6.8.153 SSH Remote Ping Sensor
- 6.8.154 SSH SAN Logical Disk Sensor
- 6.8.155 SSH SAN Physical Disk Sensor
- 6.8.156 SSH SAN System Health Sensor
- 6.8.157 SSH Script Sensor
- 6.8.158 SSH Script Advanced Sensor
- 6.8.159 SSH VMWare ESX(i) Disk Sensor
- 6.8.160 Syslog Receiver Sensor
- 6.8.161 System Health Sensor
- 6.8.162 TFTP Sensor
- 6.8.163 Traceroute Hop Count Sensor
- 6.8.164 Virtuozzo Container Disk Sensor
- 6.8.165 Virtuozzo Container Network Sensor
- 6.8.166 VMware Host Hardware (WBEM) Sensor
- 6.8.167 VMware Host Hardware Status (SOAP) Sensor
- 6.8.168 VMware Host Performance (SOAP) Sensor
- 6.8.169 VMware Virtual Machine (SOAP) Sensor
- 6.8.170 WBEM Custom Sensor
- 6.8.171 Windows CPU Load Sensor
- 6.8.172 Windows IIS 6.0 SMTP Received Sensor
- 6.8.173 Windows IIS 6.0 SMTP Sent Sensor
- 6.8.174 Windows IIS Application Sensor
- 6.8.175 Windows Last Update Sensor
- 6.8.176 Windows Logged In Users Sensor
- 6.8.177 Windows MSMQ Queue Length Sensor
- 6.8.178 Windows Network Card Sensor
- 6.8.179 Windows Pagefile Sensor
- 6.8.180 Windows Physical Disk Sensor
- 6.8.181 Windows Print Queue Sensor
- 6.8.182 Windows Registry Sensor
- 6.8.183 Windows Scheduled Task Sensor
- 6.8.184 Windows System Uptime Sensor
- 6.8.185 Windows Updates Status (Powershell) Sensor
- 6.8.186 WMI Custom Sensor
- 6.8.187 WMI Custom String Sensor
- 6.8.188 WMI Event Log Sensor
- 6.8.189 WMI Exchange Server Sensor
- 6.8.190 WMI Exchange Transport Queue Sensor
- 6.8.191 WMI File Sensor
- 6.8.192 WMI Free Disk Space (Multi Drive) Sensor
- 6.8.193 WMI HDD Health Sensor
- 6.8.194 WMI Logical Disk Sensor
- 6.8.195 WMI Memory Sensor
- 6.8.196 WMI Microsoft SQL Server 2005 Sensor (Deprecated)
- 6.8.197 WMI Microsoft SQL Server 2008 Sensor
- 6.8.198 WMI Microsoft SQL Server 2012 Sensor
- 6.8.199 WMI Process Sensor
- 6.8.200 WMI Remote Ping Sensor
- 6.8.201 WMI Security Center Sensor
- 6.8.202 WMI Service Sensor
- 6.8.203 WMI Share Sensor
- 6.8.204 WMI SharePoint Process Sensor
- 6.8.205 WMI Terminal Services (Windows 2008) Sensor
- 6.8.206 WMI Terminal Services (Windows XP/Vista/2003) Sensor
- 6.8.207 WMI UTC Time Sensor
- 6.8.208 WMI Vital System Data (V2) Sensor
- 6.8.209 WMI Volume Sensor
- 6.8.210 WMI Volume Fragmentation Sensor
- 6.8.211 WMI Windows Version Sensor
- 6.8.212 WSUS Statistics Sensor
- 6.9 Additional Sensor Types (Custom Sensors)
- 6.10 Sensor Channels Settings
- 6.11 Sensor Notifications Settings
- 7 Ajax Web Interface—Advanced Procedures+
- 7.1 Toplists
- 7.2 Arrange Objects
- 7.3 Clone Object
- 7.4 Multi-Edit
- 7.5 Create Device Template
- 7.6 Geo Maps
- 7.7 Notifications+
- 7.8 Libraries+
- 7.9 Reports+
- 7.10 Maps+
- 7.11 Setup+
- 7.11.1 Account Settings—My Account
- 7.11.2 Account Settings—Notifications
- 7.11.3 Account Settings—Schedules
- 7.11.4 System Administration—User Interface
- 7.11.5 System Administration—Monitoring
- 7.11.6 System Administration—Notification Delivery
- 7.11.7 System Administration—Core & Probes
- 7.11.8 System Administration—User Accounts
- 7.11.9 System Administration—User Groups
- 7.11.10 System Administration—Administrative Tools
- 7.11.11 Vunetrix Status—System Status
- 7.11.12 Vunetrix Status—Auto-Update
- 7.11.13 Vunetrix Status—Activation Status
- 7.11.14 Optional Downloads and Add-Ons
- 7.11.15 Chrome Desktop Notifications
- 7.11.16 Support—Contact Support
- 8 Enterprise Console+
- 9 Other User Interfaces+
- 10 Sensor Technologies+
- 10.1 Monitoring via SNMP
- 10.2 Monitoring via WMI
- 10.3 Monitoring via SSH
- 10.4 Monitoring Bandwidth via Packet Sniffing
- 10.5 Monitoring Bandwidth via Flows
- 10.6 Bandwidth Monitoring Comparison
- 10.7 Monitoring Quality of Service and VoIP
- 10.8 Monitoring Email Round Trip
- 10.9 Monitoring Backups
- 10.10 Monitoring Virtual Environments
- 10.11 Monitoring Databases
- 10.12 Monitoring Syslogs and SNMP Traps
- 11 System Administration Tools+
- 12 Advanced Topics+
- 12.1 Active Directory Integration
- 12.2 Application Programming Interface (API) Definition
- 12.3 Filter Rules for xFlow, IPFIX and Packet Sniffer Sensors
- 12.4 Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
- 12.5 Define IP Ranges
- 12.6 Define Lookups
- 12.7 Regular Expressions
- 12.8 Add Remote Probe+
- 12.9 Data Storage
- 12.10 Using Your Own SSL Certificate with Vunetrix's Web Server
- 12.11 Calculating Percentiles
- 13 Appendix+
Vunetrix Manual: Sensor Notifications Settings
The status or the data of a sensor can trigger notifications. Using this mechanism, you can configure external alerting tailored to you needs.
Example of Notification Trigger Settings
Note: Although the sensors activate a trigger, you can set notification triggers higher in the hierarchy (for example for groups or devices), thus defining triggers for multiple sensors using the inheritance mechanism.
This section describes one of three steps to set up the notification system in Vunetrix. A complete notification setup involves:
- Check and set up the Notification Delivery settings. This will tell Vunetrix how to send messages.
For detailed information, see System Administration—Notification Delivery. - Check and set up several Notifications. This will define the kind of message and its content.
For detailed information, see Account Settings—Notifications. - Check and set up Notification Triggers for objects. These will provoke the defined notifications.
For detailed information, see Sensor Notifications Settings.
For background information, please see Notifications section.
Available Notification Triggers Settings
On an object's detail page, click on the Notifications tab to change sensor notification triggers. The available options are the same for all objects. When defining triggers for probes, groups, or devices, they can be inherited down to sensor level.
Triggers that can be inherited from parent object(s) |
|
---|---|
You see a list of all notification triggers that are defined higher in the hierarchy. The list is empty when there are no triggers defined in groups or devices above the current object. You can see the type and the notifications that are executed once this trigger is activated. |
|
Trigger Inheritance |
Define whether the triggers shown above will be handed on to the current object. Choose between:
This setting is valid for all triggers shown above. It is not possible to only select some of them. |
You can set up one or more of the following triggers, each with different setting options. Which trigger types will be visible depends on the kind of object you're editing:
All notification triggers can be created in a very easy way, forming natural sentences. There are different options for every type.
Define a trigger that is activated when a sensor changes its current status. This is the most common reason to send out notifications. Click on the Add State Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) to be executed.
State Trigger |
|
---|---|
When sensor is... |
Select the condition that will trigger the notification. The trigger will be activated when a sensor enters the selected status. Choose from the drop down menu:
|
...for at least ... seconds |
Define how many seconds will be waited before a notification is provoked. This can avoid false alarms in case a sensor 'flickers' and, for example, changes to a down status for just a few seconds. If the selected condition (i.e. the sensor status) persists after the defined time in seconds, the notification will be triggered. Please enter an integer value. |
...perform... |
Select a notification that will be triggered if the condition (i.e. the sensor status) selected is true and the latency time defined has elapsed. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Settings—Notifications setttings. You can also choose no notification in order to only use other conditions for this trigger. |
When condition continues for at least ... seconds |
Define an escalation latency in seconds. A second notification can be triggered if this number of seconds has passed since the sensor status has entered the defined condition. Use this to automatically escalate a notification in case a problem persists for a longer time. Please enter an integer value. |
...perform... |
Select a (second) notification that will be triggered if the condition (i.e. the sensor status) selected is true and the escalation latency time defined has elapsed. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification in order to only use other conditions for this trigger. |
...and repeat every ... minutes |
Define an interval in minutes in which the escalation notification (defined above) will be sent repeatedly. The second (escalation) notification defined will be resent every x minutes. Please enter an integer value. |
When condition clears perform... |
Select a notification that will be triggered if the condition (i.e. the sensor status) selected is not true any more because the sensor's status has changed again. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Settings—Notifications setttings. You can also choose no notification in order to only use other conditions for this trigger. |
Save |
Click on the Save button to save your settings. |
Delete |
Click on the Delete button next to an existing notification trigger to delete it. |
Define a trigger that is activated when a sensor (for example, a traffic sensor) changes its current speed. Click on the Add Speed Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) to be executed.
Speed Trigger |
|
---|---|
When ... channel |
From the drop down menu, select the channel which's data will be regarded for this comparison. Select Primary to generally use a sensor's primary channel (this can be defined in the sensor's settings) or choose a specific channel name from the list (there are different channels for every sensor type). All following settings for this trigger will be based on the chosen channel. |
...is... |
Select the condition that will trigger the notification. Choose from the drop down menu:
|
[value] |
Define the value the channel's data will be compared with. Please enter an integer value. |
[scale] |
From the drop down menu, select the unit in which you entered the [value] above. [scale] and [time] together define the unit for the given value. If the channel's data is shown in a different unit Vunetrix will automatically convert values internally. Choose between:
|
[time] |
Select the time for the scale (so you create a scale per time designation). Choose from the drop down menu:
[scale] and [time] together define the unit for the given value. If the channel's data is shown in a different unit Vunetrix will automatically convert values internally. |
..for at least ... seconds |
Define how many seconds will be waited before a notification is provoked. This can avoid false alarms in case a channel reaches a limit for just a few moments. If the combined channel condition of [value], [scale], and [time] persists after the defined time span, the notification will be triggered. Please enter an integer value. |
...perform... |
Select a notification that will be triggered if the combined channel condition of [value], [scale], and [time] is true and the latency time defined has elapsed. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification in order to only use other conditions for this trigger. |
When condition clears perform... |
Select a notification that will be triggered if the combined channel condition of [value], [scale], and [time] is not true any more because the channel's value has changed again. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification in order to only use other conditions for this trigger. |
Save |
Click on the Save button to save your settings. |
Delete |
Click on the Delete button next to an existing notification trigger to delete it. |
Note: No escalation notification and no repeat are available for this trigger type.
Define a trigger that is activated when a sensor (for example, a traffic sensor) reaches a certain volume limit in a specified time. Click on the Add Volume Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) to be executed.
Volume Trigger |
|
---|---|
When ... channel |
From the drop down menu, select the channel which's data will be regarded for this comparison. Select Primary to generally use a sensor's primary channel (this can be defined in the sensor's settings) or choose a specific channel name from the list (there are different channels for every sensor type). All following settings for this trigger will be based on the chosen channel. |
...has reached... [value] |
Define the value the channel's data will be compared with. If the channel's data overruns this value, a notification will be triggered. Please enter an integer value. |
[scale] |
From the drop down menu, select the unit in which you entered the [value] above. [scale] and [time] together define the unit for the given value. If the channel's data is shown in a different unit Vunetrix will automatically convert values internally. Choose between:
|
per [time] |
Select the time for the scale (so you create a scale per time designation). Choose from the drop down menu:
[scale] and [time] together define the unit for the given value. If the channel's data is shown in a different unit Vunetrix will automatically convert values internally. |
...perform... |
Select a notification that will be triggered if the [value] in the combined unit of [scale] and [time] is overrun. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification in order to only use other conditions for this trigger. |
Save |
Click on the Save button to save your settings. |
Delete |
Click on the Delete button next to an existing notification trigger to delete it. |
Note: No escalation notification, no repeat, and no notification when condition clears are available for this trigger type.
Define a trigger that is activated when a sensor reaches specific values. Click on the Add Threshold Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) to be executed.
Threshold Trigger |
|
---|---|
When ... channel |
From the drop down menu, select the channel which's data will be regarded for this comparison. Select Primary to generally use a sensor's primary channel (this can be defined in the sensor's settings) or choose a specific channel name from the list (there are different channels for every sensor type). All following settings for this trigger will be based on the chosen channel. |
...is... |
Select the condition that will trigger the notification. Choose from the drop down menu:
|
[value] |
Define the value the channel's data will be compared with. It will be directly compared to the channel's data. Please enter values in the smallest possible (base) unit, for example, in bytes or seconds. Please enter an integer value. |
..for at least ... seconds |
Define how many seconds will be waited before a notification is provoked. This can avoid false alarms in case a channel reaches a limit for just a few moments. If the defined channel condition persists after the defined time span, the notification will be triggered. Please enter an integer value. |
...perform... |
Select a notification that will be triggered if the defined channel condition is true and the latency time defined has elapsed. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification in order to only use other conditions for this trigger. |
When condition clears perform... |
Select a notification that will be triggered if the defined channel condition is not true any more because the channel's value has changed again. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Settings—Notifications settings. You can also choose no notification in order to only use other conditions for this trigger. |
Save |
Click on the Save button to save your settings. |
Delete |
Click on the Delete button next to an existing notification trigger to delete it. |
Note: No escalation notification and no repeat are available for this trigger type.
Define a trigger that is activated by an 'on change' trigger. Some sensors offer the option to send such a trigger whenever sensor values have changed. Click on the Add Change Trigger button to add a new trigger, or click on the Edit button next to an existing notification to change it. Then define settings as described below. Every trigger will provoke one or more notification(s) to be executed.
Change Trigger |
|
---|---|
When sensor changes perform... |
Select a notification that will be triggered whenever a compatible sensor sends a 'change notification'. You can enable this option in the settings of some sensors. The notification trigger will be activated immediately whenever a sensor sends an 'on change' trigger. Choose a notification from the drop down menu. The menu shows all notifications defined in the Account Settings—Notifications settings. |
Note: There are no other options available for this trigger type.
For information about sensor settings, please see the following sections:
- Sensor Settings
- List of Available Sensor Types
- Additional Sensor Types (Custom Sensors)
- Sensor Channels Settings
- Sensor Notifications Settings
Object Settings Overview
For more general information about object settings, please see section Object Settings.
Ajax Web Interface—Device and Sensor Setup—Topics
Other Ajax Web Interface Sections
Related Topics |
---|
Keywords: Change Trigger,Configure,Configure Notification Trigger,Escalation,Latency,Notification,Notification Escalation,Notification Trigger,Off Notification,On Notification,Sensor,Sensor Notification Trigger,Speed Trigger,State Trigger,Threshold Trigger,Trigger,Trigger Change,Trigger Latency,Trigger Speed,Trigger State,Trigger Threshold,Trigger Volume,Volume Trigger