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


EXE/Script Advanced sensor incorrect error message

Votes:

0

Your Vote:

Up

Down

I have a custom sensor returning a couple of channels. For a clearer image, the structure of a channel is the following: <result> <channel>server0</channel> <value>100</value> <Unit>Percent</Unit> <LimitMinWarning>80</LimitMinWarning> <LimitMinError>60</LimitMinError> <LimitWarningMsg>Process is in maintenance or starting.</LimitWarningMsg> <LimitErrorMsg>Process is stopped or in an unknown state</LimitErrorMsg> <LimitMode>1</LimitMode> </result>

At some point, one of the channels returned a value of 0, leading to a red status for the whole sensor(as expected), the message was the following: "(bootstrap) is below the error limit of 60% in bootstrap. Process is stopped or in an unknown state."

The issue starts when common changes in the monitored environment lead to channels receiving no data from one point forward. This is expected behavior, and no data for a couple of channels is fine. However, we encountered an issue in which another channel received a value of 0, but the error message remained identical("bootstrap" instead of the channel name that is actually down.)

All the channels have a static structure, thresholds are not changed at any point. Restarting the sensor leads to no improvement. Recreating the sensor works correctly, but it is not a solution, considering our client's monitored environment size would mean a lot of unnecessary manual labor for fixing this issue. Even more, the loss of historical data is a deal-breaker from their point of view.

Any clarifications are of great help.

custom-sensor error-messages sensor-channels

Created on Dec 6, 2017 3:19:40 PM by  barabas_a (0) 2



5 Replies

Votes:

0

Your Vote:

Up

Down

Hi there,

Unfortunately, it is not possible to change the thresholds which are set for a Custom Sensor. We have many reasons for this, but the main reason is that should we allow this, then this could cause strange errors when the values change randomly. This is why we decided to keep them static after the initial scan.

Best regards.

Created on Dec 7, 2017 5:03:37 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello, I know that thresholds are not changeable after the initial set values. The issue at hand, summarised is: I have a channel with no received data, the error message of the sensor states that that very channel is under the threshold. When actually another channel has values under the threshold. Neither of the channels are set as being primary for the sensor.

Created on Dec 7, 2017 5:13:58 PM by  barabas_a (0) 2



Votes:

0

Your Vote:

Up

Down

Hi there,

Unfortunately, we are unable to reproduce this. In a test with a Custom Script Sensor with multiple channels and limits, when one of the channels gets no data, then the value 0 is used. But we get the message for both sensors where the values are blow the limits.

What version of PRTG are you currently using?

Best regards.

Created on Dec 8, 2017 10:42:50 AM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi, the version is 17.2.31.2153. The channel simply has "no data", not 0.

Just to make sure that I pictured all the details correctly:

After creating the sensor, the output is the following (the rest of the channels are removed for clarity):

Day 1:

<?xml version="1.0" encoding="UTF-8" ?>
<prtg>
        <result>
                <channel>gwrd</channel>
                <value>0</value>
                <Unit>Percent</Unit>
                <LimitMinWarning>80</LimitMinWarning>
                <LimitWarningMsg>Process has a yellow status code</LimitWarningMsg>
                <LimitErrorMsg>Process has a status of gray/red</LimitErrorMsg>
                <LimitMode>1</LimitMode>
                <ShowTable>0</ShowTable>
        </result>

        <result>
                <channel>icman</channel>
                <value>100</value>
                <Unit>Percent</Unit>
                <LimitMinWarning>80</LimitMinWarning>
                <LimitWarningMsg>Process has a yellow status code</LimitWarningMsg>
                <LimitErrorMsg>Process has a status of gray/red</LimitErrorMsg>
                <LimitMode>1</LimitMode>
                <ShowTable>0</ShowTable>
        </result>
</prtg>

The sensor is in an error state with the message [...] (gwrd) is below the error limit of 60% in gwrd. Process is stopped or in an unknown state.

This behaviour is correct so far.

Day 2:

<?xml version="1.0" encoding="UTF-8" ?>
<prtg>
        <result>
                <channel>icman</channel>
                <value>0</value>
                <Unit>Percent</Unit>
                <LimitMinWarning>80</LimitMinWarning>
                <LimitWarningMsg>Process has a yellow status code</LimitWarningMsg>
                <LimitErrorMsg>Process has a status of gray/red</LimitErrorMsg>
                <LimitMode>1</LimitMode>
                <ShowTable>0</ShowTable>
        </result>
</prtg>

The sensor does not return any data for gwrd, as the process does not exist anymore on the monitored server. (the gwrd channel still exists, but with no data message, which is correct).

The remaining channel (icman) has a value below the minimum error threshold, so the sensor should be in an error state.

However, the error message is still: [...] (gwrd) is below the error limit of 60% in gwrd. Process is stopped or in an unknown state.

To summarize: in day 2, the error message should not contain gwrd, as the channel is orphaned.

Created on Dec 8, 2017 11:46:12 AM by  barabas_a (0) 2

Last change on Dec 8, 2017 12:56:23 PM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi there,

That's where the confusion came from. I assumed that you were missing the sensor message of another channel due to the missing channel.

However, this is intended as PRTG uses the last value of the sensor when the channel does not offer any new data. This is why the message of the missing channel is still appearing.

Best regards.

Created on Dec 8, 2017 3:26:43 PM by  Dariusz Gorka [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.