- 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: Windows Updates Status (Powershell) Sensor
The Windows Updates Status (Powershell) sensor monitors the status of Windows updates on a computer and counts the available and installed Windows updates—either from Microsoft or from the local Windows Server Update Services (WSUS) server. This sensor can show the time elapsed since the last update, as well as the following numbers:
- Installed Windows updates
- Missing Windows updates
- Installed security updates with low, moderate, important, and critical priority
- Missing security updates with low, moderate, important, and critical priority
You can find the considered updates in Server Manager (WSUS) under Roles | Windows Server Update Services | Update Services | Computers | Reports.
Note: If the sensor cannot determine the Time since last update (for example, because the list of updates is empty), it will show the value -1s and turn into a Warning status.
Note: This sensor type can have a high impact on the performance of your monitoring system. Please use it with care! We recommend using not more than 50 sensors, on each probe, of this type of sensor.
Note: We recommend setting the scanning interval of this sensor to at least 12 hours to limit the load on the server being monitored.
For this sensor type credentials for Windows systems must be defined for the device you want to use the sensor on.
This sensor type requires the Microsoft .NET Framework to be installed on the computer running the Vunetrix probe: Either on the local system (on every node, if on a cluster probe), or on the system running the remote probe. If the framework is missing, you cannot create this sensor. Note: You need to install the exact version required (a higher version will usually not work; an exception applies to .NET 3.5 which comprises .NET 2.0 and .NET 3.0). Generally, it is possible to run several .NET Framework versions on the same machine side-by-side. Please install the latest update available for the required version.
Required .NET version: 4.0 (with latest update).
Requirement: Remote PowerShell
The Windows Updates Status (Powershell) sensor uses PowerShell commands. In order to monitor devices with this sensor, Remote PowerShell access has to be enabled on the target computer. For detailed information, please see More section below.
The Add Sensor dialog appears when adding a new sensor on a device manually. It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Settings tab later.
On the sensor's details page, click on the Settings tab to change settings.
Note: If not set explicitly in a sensor's settings, it will connect to the IP Address or DNS Name defined in the settings of the parent device the sensor is created on.
Basic Sensor Settings |
|
---|---|
Sensor Name |
Enter a meaningful name to identify the sensor. The name will be shown by default in the device tree and in all alarms. |
Tags |
Enter one or more tags, separated by space or comma. You can use tags to group sensors and use tag-filtered views later on. Tags are not case sensitive. We recommend using the default value. You can add additional tags to it, if you like. Other tags are automatically inherited from objects further up in the device tree. Those are not visible here. |
Priority |
Select a priority for the sensor. This setting determines where the sensor will be placed in sensor lists. Top priority will be at the top of a list. You can choose from one star (low priority) to five stars (top priority). |
Sensor Display |
|
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel will always be displayed underneath the sensor's name. The available options depend on what channels are available for this sensor. Note: You can set another primary channel later by clicking on the pin symbol of a channel in the sensor's overview tab. |
Chart Type |
Define how different channels will be shown for this sensor.
|
Stack Unit |
This setting is only available if stacked graphs are selected above. Choose a unit from the list. All channels with this unit will be stacked on top of each other. By default, you cannot exclude single channels from stacking, if they use the selected unit. However, there is an advanced procedure to do so. |
By default, all following settings are inherited from objects higher in the hierarchy and should be changed there, if necessary. Often, best practice is to change them centrally in the Root group's settings. To change a setting for this object, disable inheritance by clicking on the check mark symbol in front of the respective setting name. You will then see the options described below.
Scanning Interval |
|
Scanning Interval |
The scanning interval determines the time the sensor waits between two scans. Select a scanning interval (seconds, minutes, or hours) from the list. You can change the available intervals in the system administration. |
Schedules, Dependencies, and Maintenance Window |
|
---|---|
Note: Inheritance for schedules, dependencies, and maintenance windows cannot be interrupted; the according settings from the parent objects will always be active. However, you can define additional settings here. They will be active in parallel to the parent objects' settings. |
|
Schedule |
Select a schedule from the list. Schedules can be used to monitor for a certain time span (days, hours) throughout the week. With the period list option it is also possible to pause monitoring for a specific time span. You can create new schedules and edit existing ones in the account settings. Note: Schedules are generally inherited. New schedules will be added to existing ones, so all schedules are active. |
Maintenance Window |
Specify if you want to set-up a one-time maintenance window. During a maintenance window this object and all child objects will not be monitored. They will enter a paused state then. Choose between:
|
Maintenance Begins At |
This field is only visible if maintenance window is enabled above. Use the date time picker to enter the start date and time of the maintenance window. |
Maintenance End At |
This field is only visible if maintenance window is enabled above. Use the date time picker to enter the end date and time of the maintenance window. |
Dependency Type |
Define a dependency type. Dependencies can be used to pause monitoring for an object depending on the status of another. You can choose between:
Note: Testing your dependencies is easy! Simply choose Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later all dependent objects should be paused. |
Dependency |
This field is only visible if the select object option is enabled above. Click on the reading-glass symbol and use the object selector to choose an object on which the current sensor will be dependent on. |
Delay (Seconds) |
Define a time span. After the master object for this dependency comes back to an Up status, monitoring of the depending objects will be additionally delayed by the defined time span. This can help avoid false alarms, for example, after a server restart, by giving systems more time for all services to start up. Please enter an integer value in seconds. Note: This setting is not available if you choose this sensor to be the Master object for parent. In this case, please define delays in the parent Device Settings or the superior Group Settings. |
Access Rights |
|
User Group Access |
Define which user group(s) will have access to the object you're editing. A table with user groups and right is shown; it contains all user groups from your setup. For each user group you can choose from the following access rights:
You can create new user groups in the System Administration—User Groups settings. To automatically set all objects further down in the hierarchy to inherit this object's access rights, set a check mark for the Revert children's access rights to inherited option. For more details about access rights, please see section User Access Rights. |
In order to change display settings, spike filter, and limits, please switch to the sensor's Overview tab and click on the gear icon of a specific channel. For detailed information, please see Sensor Channels Settings section.
Click on the Notifications tab to change notification triggers. For detailed information, please see Sensor Notifications Settings section.
For more general information about settings, please see Object Settings section.
For information about sensor settings, please see the following sections:
Keywords: