PRTG custom script returns valid XML but dashboard complains -
i have prtg custom script in exexml directory has been configured within prtg dashboard.
when run manually, following output which, far i'm aware, valid:
<prtg> <result> <channel>maxcpuwl1</channel> <value>113</value> </result> <text>ok</text> </prtg>
in fact, have another script pretty generates same format, including identical cr/lf
sequences @ end of lines:
<prtg> <result> <channel>item age</channel> <value>14</value> </result> <text>april 15, 2015</text> </prtg>
i've checked in detail output of both ensure haven't done stupid, use channe1
(with one) instead of channel
(with l
).
and yet, first one, keep getting in dashboard:
xml: returned xml not match expected schema. (code: pe233) -- json: returned json not match expected structure (invalid json.). (code: pe231)
what causing problem?
if edit properties of sensor, can capture output of executable under conditions:
o discard exe result o write exe result disk o write exe result disk in case of error
a way see custom sensor doing set middle option (normally first set) , go , file result of sensor xxxx.txt
(where xxxx
sensor id) in sensor logs directory, such as:
c:\programdata\paessler\prtg network monitor\logs (sensors)
that should show errors occurring in script, or @ least output confusing prtg sensor output analysis.
in particular case, having trouble running pscp
command go out , retrieve file remote server, approach should able evaluate , fix wide variety of problems.
Comments
Post a Comment