Thanks for your reply!
OK, long story short: SNMP is too complex and lacking relations between counters (which a script can bring into relation). That would explain why so many scripts are available.
The problem I see with plugins, is that most of them only return OK / WARNING / CRITICAL in terms of Icinga2. (At least thats my impression while using the icinga director). For a router I would like the general health status but at the same time, traffic stats would be appreciated.
Do most solve this with a central solution like Icinga2 or in combination with other tools side-by-side?
My current plan is to feed everything into icinga2 and forward counter data to influxdb using the icinga2 master’s plugins. That way I can use the icinga2 cluster stack (which is very very reliable) für remote locations.
I’ve tested a lot of tools like OpenNMS and LibreNMS but they lack stable remote execution. Some depend on direct access to SNMP, some lack secure clustering (like OpenNMS, which is unsuitable for WWW).
The final question is: Is Icinga2 suitable for statistical data in parallel to UP/DOWN/etc.?