Improve setup of snmp-exporter
Summary
snmp-exporter's current configuration can be improved
related references
Details
The list of improvements that we identified as needed for the config:
- improve security of the credentials by using secrets (as opposed to the current clear text credentials passed as `snmp.yaml` content atm)
- have the list of hardware devices be taken automatically from the platform configuration
- create groups of SNMP devices / use same credentials per group instead of per entire platform
- separate OID's as a distinct file to be used in building the final
snmp.yaml
file. This will separate a large block of fixed text in order to have a clearer manner of constructing the finalsnmp.yaml
config file. - trim OIDs files to have strictly only the metrics needed by the dashboards -- to be decided whether it is needed and how to decide on the cleanup
- improve resiliency settings (type of kube deployment, number of replicas, etc) -- use smth like
max(.Values.cluster.control_plane_replicas, 3)
- fix templating in order not to have unnecessary newlines which atm are at the beginning of each block module. The templating should result in a clean config. This may need to be needed for more elaborate templating which we may need to have in the future; we do not want to have a blocker in the templating solution we have atm in place.
- Check security settings / eventually improve this part
- Try to get rid of
fullname-override
setting -- the unit's name should be simply determined by Sylva in a predictable way. - Adjust constraints for group name -- need to determine the exact form accepted by
snmp-exporter
Edited by Emil Furniga