This post highlights the workflow for using Incinga2 as a task runner and exporting results to Influxdb for reporting. There are some network devices that use none standard MIBs and O.I.Ds. While it is possible to simply poll a given O.I.D using the ISO format, for example 188.8.131.52.4.1.68184.108.40.206.220.127.116.11. This works great except it simply doesn’t scale beyond a few devices, i.e 1-5 device is fine 70+ devices == extreme pain. My solution for this was to combine a few technologies that are readily available and most importantly are free. I started with Icinga2 with the api, director and influx modules enabled. I created the standard host and service group constructs. Then created each O.I.D as a separate check that is then assigned to a service group and eventually to a host group. Icinga does what it does best, which is to schedule and execute lots of checks, then evaluate the result. This result can then be further processed to do things like trigger some sort of alert. In this case since the check returns a value ( integer) Icinga exports the results to an InfluxDB database. This data is in turn consumed by Chronograf for creating dashboard and allows for ad-hoc reporting.