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

Article Comments

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


Feb, 2017 - Permalink

Hi Felix,

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

Regards, Moritz


Feb, 2017 - Permalink

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]


Feb, 2017 - Permalink

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


Feb, 2017 - Permalink