Votes:
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
Votes:
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.
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.
Best Regards,
Luciano Lingnau [Paessler Support]
Created on Feb 2, 2017 8:03:26 AM by
Last change on Feb 2, 2017 8:06:54 AM by
4 Replies
Votes:
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
Last change on Feb 2, 2017 7:56:04 AM by
Votes:
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.
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.
Best Regards,
Luciano Lingnau [Paessler Support]
Created on Feb 2, 2017 8:03:26 AM by
Last change on Feb 2, 2017 8:06:54 AM by
Add comment