I’ve started digging into sensu as a monitoring option. I’m having trouble finding information on device modelling. In the past I’ve worked with tools that used plugins to model devices, pulling facts, enumerating interfaces etc. I’m trying to get a handle on what this looks like in a Sensu context, any pointers would be greatly appreciated.
Does the entity resource specification help with what you are looking for.
In the Sensu Go the running sensu-agent will collect facts from the system and populate/update the associated Sensu entity resource’s system attribute. The agent will create/update the entity resource on first connect to the backend, and as part of its keepalive heartbeat check.
Ahhhh gotcha, thank you. Unfortunately in looking at that I just realised the limitation on the free version.