Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make log message topics more consistent #895

Closed
mountaindude opened this issue Dec 7, 2023 · 0 comments · Fixed by #894
Closed

Make log message topics more consistent #895

mountaindude opened this issue Dec 7, 2023 · 0 comments · Fixed by #894

Comments

@mountaindude
Copy link
Collaborator

mountaindude commented Dec 7, 2023

Over the years more and more refined log messages have been used in Butler.

For example, log entries related to the recent addition of writing successful reload data to InfluxDb are prefixed with RELOAD TASK SUCCESS INFLUXDB.

This is better than the older webhook notification feature, where log messages are prefixed with WEBHOOKOUTFAILED.

Review log entry prefixes and make them more consistent across the entire Butler code base.
As a general rule of thumb, place the destination system first, for example INFLUXDB RELOAD TASK SUCCESS rather than RELOAD TASK SUCCESS INFLUXDB

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant