Why do you actually send the IP octets in four steps?
curl "http://blah.blah.blah.com:5050/$mac_dash_all?content=<prtg><result><channel>IP-Octet-1</channel><value>$oct1</value></result></prtg>"
sleep 1
curl "http://blah.blah.blah.com:5050/$mac_dash_all?content=<prtg><result><channel>IP-Octet-2</channel><value>$oct2</value></result></prtg>"
sleep 1
curl "http://blah.blah.blah.com:5050/$mac_dash_all?content=<prtg><result><channel>IP-Octet-3</channel><value>$oct3</value></result></prtg>"
sleep 1
curl "http://blah.blah.blah.com:5050/$mac_dash_all?content=<prtg><result><channel>IP-Octet-4</channel><value>$oct4</value></result></prtg>"
sleep 5
it would be easier to do this in one API call.. there are even better ways to do it - but I would recommend to test this for a brief change and validation:
curl "http://blah.blah.blah.com:5050/$mac_dash_all?content=<prtg><result><channel>IP-Octet-1</channel><value>$oct1</value></result><result><channel>IP-Octet-2</channel><value>$oct2</value></result><result><channel>IP-Octet-3</channel><value>$oct3</value></result><result><channel>IP-Octet-4</channel><value>$oct4</value></result></prtg>"
I think you might actually confuse PRTG with those 4x calls - due to the channels not necessarily being fixed in this case and while sending the data in split API calls instead of in one single call..
Can you try and see if this helps?
Add comment