New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.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


Have a custom sensor and all tables go red forever when error occurs

Votes:

0

Your Vote:

Up

Down

I have written an advanced sensor that passed XML formatted channels back based on health states of a set of items. It uses custom lookups to translate integer values back to textual for the dashboard. The PS Script is querying a remote device via REST which requires authentication. The channels include content for custom lookups and define maximum warning and error values.

My issue is that it seems occasionally the authentication fails generating an error condition response for the sensor. This is not an issue for the sensors I have written without a custom lookup as it will re-attempt and all is then ok and the dashboard tables all display correctly. With the sensors that are using custom lookups though the dials display all red instead of the green, orange and red sections of the normal defined limits even once the channel is back to reporting healthy.

My questions are 1) why do the dials still display all red even though the condition is reported back to OK only for custom lookups 2) how can I reset the dials programatically or is there logic that I am possibly missing in my channel/sensor reporting?

Below is a copy of a channel from one of the sensors I am having issues with.

<Result> <Channel>Controller 1</Channel> <Value>0</Value> <unit>Count</unit> <Float>0</Float> <volumeSize>One</volumeSize> <DecimalMode>0</DecimalMode> <ValueLookup>prtg.standardlookups.mycustom.hardwarestatus</ValueLookup> <LimitMaxWarning>2</LimitMaxWarning> <LimitMaxError>8</LimitMaxError> <LimitMode>1</LimitMode> </Result>

Any help would be appreciated as have been banging my head on this one!

advanced custom-sensor powershell

Created on Sep 21, 2017 10:12:04 PM by  davlloyd (0) 1



1 Reply

Votes:

0

Your Vote:

Up

Down

Actually sorted it out in the end. As I had defined both states within the lookup files and limits in the channels a conflict was occurring. I removed the limits from the channels and all is now working as expected.

Created on Sep 22, 2017 4:28:50 AM by  davlloyd (0) 1



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.