Is it possible to have sensors for VMs that have moved to another host be deleted? Currently the sensors never delete and they stay there with an error of: "The object has already been deleted or has not been completely created"
Article Comments
Dear tkudela
Do you want PRTG to delete sensors which are pointing to deleted VMs? This is not possible. PRTG will not delete any sensor by itself.
You can use this API call to get all sensors with a particular last message:
/api/table.csv?id=0&content=sensors&columns=objid,name&count=*&filter_message=The%20object%20has%20already%20been%20deleted%20or%20has%20not%20been%20completely%20created
This can help to quickly find sensors with that message. This example provides the actual call. To generate a complete API call, please have a look at PRTG, menu Setup / PRTG API, tab "HTTP API".
Feb, 2015 - Permalink
Arne,
Thank you for the reply. That answered my question. I can see which sensors are looking for deleted objects since they present an error state. I'll see if I can discover a way to do it.
Thanks,
Tim
Feb, 2015 - Permalink
Dear tkudela
Do you want PRTG to delete sensors which are pointing to deleted VMs? This is not possible. PRTG will not delete any sensor by itself.
You can use this API call to get all sensors with a particular last message:
/api/table.csv?id=0&content=sensors&columns=objid,name&count=*&filter_message=The%20object%20has%20already%20been%20deleted%20or%20has%20not%20been%20completely%20created
This can help to quickly find sensors with that message. This example provides the actual call. To generate a complete API call, please have a look at PRTG, menu Setup / PRTG API, tab "HTTP API".
Feb, 2015 - Permalink