You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some device manufacturers have moved to an API model for some checks of devices
I.e if you want to check the uptime of a device you would query an API usually restful to get the status of the device
Instead of traditional SNMP
Cacti can be adapted to monitor a device purely by API instead of SNMP with the right scripts you can pass for example the device id
Into the script and onto the API to get the data you want to plot but since cacti does not see the device online it will not attempt to run the script server for this device
Maybe this can be a "custom" availability check where you provide a script and it must return 1 for up 0 for down ?
The text was updated successfully, but these errors were encountered:
I'm working on an API for the servcheck plugin. Larry and I talked about it, and if it works, we'll add it later as a new data source directly into cacti. It's more complicated in that there are several ways to authenticate a user (password, oauth token, ...)
TheWitness
changed the title
[Feature Request] - Support API based device availability checks
Support API based device availability checks
Dec 3, 2024
Some device manufacturers have moved to an API model for some checks of devices
I.e if you want to check the uptime of a device you would query an API usually restful to get the status of the device
Instead of traditional SNMP
Cacti can be adapted to monitor a device purely by API instead of SNMP with the right scripts you can pass for example the device id
Into the script and onto the API to get the data you want to plot but since cacti does not see the device online it will not attempt to run the script server for this device
Maybe this can be a "custom" availability check where you provide a script and it must return 1 for up 0 for down ?
The text was updated successfully, but these errors were encountered: