junos_exporter seems like a useful tool for a few reasons:
- Migrate away from Icinga (by replacing the various check_bgp, check_vrrp, check_ospf, etc)
- (In a longtime time) migrate away from LibreNMS (industry is moving to Prometheus like tool)
- Monitor more things, more easily (adding similar features to LibreNMS is quite complex)
- Interface queue statistics
- Better BGP monitoring (eg. for T306649#8728183)
- Alarms T241105: No Juniper alarms in SNMP for MX204
- Routes
- Firewall filters (counters and policers)
- More details on interface errors
- RPKI Sessions
- Overall, leverage Prometheus/Grafana/AlertManager
- Interesting features such as "Custom Label RegEx"
Especially if it's not too complex to deploy it could help with our transition to streaming telemetry (where the industry seems to be going, while still not there yet...) by starting to get data in Prometheus and relying less on SNMP.
The main unknown so far to me is the impact of pulling this data over SSH. Does it keep the session open? Does it open one every minute?
It's moderately maintained, with the latest release in Nov 2022 but some recent patches merged in main.
Debs are provided which we could use at least for testing if not directly in prod.
Feedback welcome but I'd see it as:
- Generate a distinct key pair
- Add the key as read only on some network devices (+ whatever is needed for Firewall filters counters and policers)
- Install the deb to experiment with on netmon1003 (acls already permit this host)
- Test it
- If satisfying, choose on which host to run the exporter (prometheus hosts?), puppetize, etc.
- Write dashboards + alerting