Closed fpicot closed 3 years ago
Thanks for the report. You're right. I think this should be removed as well. @clwluvw What's your thoughts on this? Should we log this only if we expected keepalived to provide it?
@mehdy Do you think should we log this warn if state isn't empty in any keepalived versions or just for versions that doesn't support script state?
@clwluvw I think we should warn only if we expected the state to be non-empty (e.g. certain versions of keepalived). So I think it's better to decide based on the version.
@mehdy I think this can be done after #55
Running keepalived-exporter 1.1.0 with keepalived 1.3.5 returns a recurring warning in the logs :
It seems that the exporter tries to get the script state here : https://github.com/cafebazaar/keepalived-exporter/blob/7f70713c5b9d41121339e7e5195f91df9147fb1d/internal/collector/collector.go#L176
However, keepalived 1.3.5 does not expose this information in the data, only the status.
The warning can be safely ignored, but spam the logs with false positives.