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


Treat unmapped error codes as error in ScheduledTask2XML sensor

Votes:

0

Your Vote:

Up

Down

Hi,

is there are trick to treat all return codes which are not listed in the value lookup as error for the ScheduledTask2XML sensor? We use this sensor quite extensively and it happed that we missed errors/warnings because the Task Result channel didnt't react on unmapped return codes.

Thanks in advance for your help!

Regards, Moritz

channel-settings scheduled-task scheduledtask2xml

Created on Jan 31, 2017 10:24:47 AM by  Moritz (0) 1



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello Moritz,

This is possible with the current PRTG Versions. It isn't described in PaeValueLookup.xsd because it is an optional parameter. In XML Schemas, attributes are optional by default. Only required attributes have to be explicitly declared in the xsd.

To make the adjustment/change:

You first need to figure which lookup the channel is using. For this, click on the channel and review the "Lookup"'s name.

Head to "C:\Program Files (x86)\PRTG Network Monitor\lookups" (Or the \custom subfolder) and locate the lookup with that name.

Once you've located the lookup, adjust the undefinedState in the second line of the Lookup:

<ValueLookup id="ptf.scheduledtask...." desiredValue="0" undefinedState="Warning">

If the undefinedState="" statemente doesn't exist on the second line, just add it to the end of the line and make sure that you don't violate the XML Syntax.

Once you've performed the required changes, head to Setup > Administrative Tools in PRTG's web-interface and issue a re-load lookups.

More Information about Lookups


Best Regards,
Luciano Lingnau [Paessler Support]

Created on Feb 2, 2017 8:03:26 AM by  Luciano Lingnau [Paessler Support]

Last change on Feb 2, 2017 8:06:54 AM by  Luciano Lingnau [Paessler Support]



4 Replies

Votes:

0

Your Vote:

Up

Down

Hi Moritz,

it is possible to set an "UndefinedState" in the lookup file of the sensor. Simply add undefinedState="Warning" to the lookup and the sensor will change the status to warning if a returning code is unmapped.

An example is also provided in this article.

Best regards, Felix

Created on Feb 1, 2017 12:29:28 PM by  Felix Saure [Paessler Support]

Last change on Feb 2, 2017 7:56:04 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Felix,

when will it be possible? I can't find that attribute defined in PaeValueLookup.xsd

Regards, Moritz

Created on Feb 1, 2017 12:52:08 PM by  Moritz (0) 1



Accepted Answer

Votes:

0

Your Vote:

Up

Down

Hello Moritz,

This is possible with the current PRTG Versions. It isn't described in PaeValueLookup.xsd because it is an optional parameter. In XML Schemas, attributes are optional by default. Only required attributes have to be explicitly declared in the xsd.

To make the adjustment/change:

You first need to figure which lookup the channel is using. For this, click on the channel and review the "Lookup"'s name.

Head to "C:\Program Files (x86)\PRTG Network Monitor\lookups" (Or the \custom subfolder) and locate the lookup with that name.

Once you've located the lookup, adjust the undefinedState in the second line of the Lookup:

<ValueLookup id="ptf.scheduledtask...." desiredValue="0" undefinedState="Warning">

If the undefinedState="" statemente doesn't exist on the second line, just add it to the end of the line and make sure that you don't violate the XML Syntax.

Once you've performed the required changes, head to Setup > Administrative Tools in PRTG's web-interface and issue a re-load lookups.

More Information about Lookups


Best Regards,
Luciano Lingnau [Paessler Support]

Created on Feb 2, 2017 8:03:26 AM by  Luciano Lingnau [Paessler Support]

Last change on Feb 2, 2017 8:06:54 AM by  Luciano Lingnau [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Luciano,

yeah thats what I wanted to do, but since I couldn't find the attribute defined in the PaeValueLookup schema and Felix wrote "will be", I hesitated. I will set the attribute now, even though it's not in the schema.

Thanks for your help!

Regards, Moritz

Created on Feb 2, 2017 8:10:11 AM by  Moritz (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.