-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add config_changed log for cachecheck #165
Comments
When it is updating it has only seen the cached version, so lets also read from the db when it is about to update. This does two things:
|
Also not sure about config_log, maybe just error_log is enough. This will spam the config log daily |
matthewhilton
added a commit
that referenced
this issue
Nov 17, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 17, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 17, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 19, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 19, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 20, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 20, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 20, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 20, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 20, 2023
matthewhilton
added a commit
that referenced
this issue
Nov 20, 2023
brendanheywood
pushed a commit
that referenced
this issue
Nov 20, 2023
matthewhilton
added a commit
that referenced
this issue
Jan 22, 2024
brendanheywood
pushed a commit
that referenced
this issue
Jan 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whenever the cachecheck re-pings, it should log a config change
This is so we can see the history of what updated the value and at what time
The text was updated successfully, but these errors were encountered: