Unsupported stat info messages should be a lower log level
These log statements are, in my opinion, not relevant enough to warrant being INFO level:
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: v4-allocation-fail-no-pools
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: v4-allocation-fail-subnet
INFO[2022-09-26 21:45:51] promkeaexporter.go:680 Encountered unsupported stat: v4-reservation-conflicts
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: declined-addresses
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: reclaimed-leases
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: reclaimed-declined-addresses
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: v4-allocation-fail
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: v4-reservation-conflicts
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: v4-allocation-fail-shared-network
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: v4-allocation-fail-classes
INFO[2022-09-26 21:45:51] promkeaexporter.go:683 Encountered unsupported stat: cumulative-assigned-addresses
INFO[2022-09-26 21:45:51] promkeaexporter.go:680 Encountered unsupported stat: v4-reservation-conflicts
...
I propose that they be moved to DEBUG log level. Adding support for an unsupported stat is not something expected of a normal system administrator.
See #839 (closed).