I'm actually thinking of some kind of "discovery" queue, where a bunch of devices can be added and are then "tested" at the end of each polling cycle to see if they exist. If they do, they're discovered and added, if not, ignored for later.
Putting them directly in to the device table seems messy, especially since we've not verified their authentication information or worked out what OS they are at that point.
adam.On 20/10/2015 14:45:40, Pål Rydningen <paal.rydningen@gmail.com> wrote:
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observiumIts a quick'n'silly workaround but with a job-scheduler -- couldnt you just schedule the appropriate "add_device.php"-commands?The myriad of flavours of task-scheduling should allow all kinds of flexibility here, and its easy to test, easy to log, easy to follow up...
Observium already uses Cron-entries for polling and housekeeping - there is a way in there already.
The other suggestions of adding a device as "ignored" seems good, but it strikes me as a limited use, single-purpose tool.I'd probably end up adding devices and then forgetting about them..
Meaning visualizing and/or keeping track of "idle/pending/ignored/temporary down/in maintainance" would also have to be adressed.Keeping track of too many shades of colour on the Overview-page isnt good either.
/Paal R/
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium