New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Problem creating and applying device template with "Current Disk Queue Length X"

Votes:

0

Your Vote:

Up

Down

I am playing around with creating Device templates and I seem to run in to some problem when I use sensors from "WMI Logical Disk" Specifically the "Current Disk Queue Length X". When creating the template I get a list of sensors that I want to exclude from the template, this is only populated with the sensors listed above the "Current Disk Queue Length X" in the main device sensor list, if I ignore this then the template is created.

But when I apply the template i just creates those sensors listed above "Current Disk Queue Length X" on the original machine and then the auto-discovery sticks at 0%. We are running: PRTG Network Monitor 16.1.22.2252 x64

Below is the log from Auto Discovery Debug Log.log

2016-03-22 15:07:29: Autodiscovery Started; Device ID: 89621
2016-03-22 15:07:29: Device Templates; Device ID: 89621; Selected: 1
2016-03-22 15:07:29: Template Loaded; Device ID: 89621; Name: SQL Workgroup v4
2016-03-22 15:07:37: Template Check; Device ID: 89621; Check ID: ping; FOUND
2016-03-22 15:07:37: Template Assigned; Device ID: 89621; Name: SQL Workgroup v4
2016-03-22 15:07:37: Sensor Created; Device ID: 89621; Create ID: {2B1FA933-5385-44FF-A9B7-E3603329E6E0}; Sensor ID: 91784; Name: Ping
2016-03-22 15:07:53: Template Check; Device ID: 89621; Check ID: wmi; FOUND
2016-03-22 15:07:53: Sensor Created; Device ID: 89621; Create ID: {3C6D3565-3A72-421D-93A3-204FA28FC8E1}; Sensor ID: 91785; Name: Free Disk Space (Multi Drive)
2016-03-22 15:07:59: Sensor Created; Device ID: 89621; Create ID: {0E6F0E28-D0C5-43C3-8DF7-F862D90A7B79}; Sensor ID: 91786; Name: Pagefile Usage
2016-03-22 15:08:06: Sensor Created; Device ID: 89621; Create ID: {567F1DDD-1B36-4372-98B1-BC85BAED4F2F}; Sensor ID: 91787; Name: Memory
2016-03-22 15:08:12: Sensor Created; Device ID: 89621; Create ID: {9FAE99E7-1250-4BC7-B16A-A301076416C8}; Sensor ID: 91788; Name: Windows System Uptime
2016-03-22 15:08:18: Sensor Created; Device ID: 89621; Create ID: {A5F9CCE3-2BE1-425D-ADCF-ABD42A8D2D7E}; Sensor ID: 91789; Name: CPU
2016-03-22 15:23:24: Template Check; Device ID: 89621; Check ID: Win32_PerfRawData_PerfDisk_LogicalDisk_CurrentDiskQueueLength__Total; PROBE TIMEOUT
2016-03-22 15:38:24: Template Check; Device ID: 89621; Check ID: Win32_PerfRawData_PerfDisk_LogicalDisk_CurrentDiskQueueLength_C:; PROBE TIMEOUT

0- auto-discovery device-template logical-disk

Created on Mar 22, 2016 3:42:46 PM by  farthinder (0) 1

Last change on Mar 23, 2016 6:05:12 AM by  Felix Saure [Paessler Support]



1 Reply

Votes:

0

Your Vote:

Up

Down

Hi,
Could you possibly forward us the whole Auto Discovery Log along with the other logs to [email protected]?
Please refer to this thread when doing so.
Best regards

Created on Mar 24, 2016 1:56:32 PM by  Konstantin Wolff [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.