You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We’re running our own Docker registry which is on scheduled maintenance during the night. During this time, when Watchtower cannot access the registry, our Slack channels will be flooded with messages:
Describe the solution you'd like
An ideal solution, though obviously quite narrow to our use case, would be, that errors about an unreachable registry are only propagated after x failed attempts, or y minutes.
Describe alternatives you've considered
Alternatively, completely turning off notifications about unreachable registries might work for us as well -- while retaining other info and error notifications. (doesn’t seem to be possible with the current log levels, as the mentioned message is logged with info)
Additional context
I understand that this is probably a quite “special” case, so I’m not expecting a feature like this. However, I’d like to hear how/if others are dealing with this situation.
The text was updated successfully, but these errors were encountered:
We already have a suggestion in place for implementing per container maintenance windows. Seems like that would solve your use case as well. Closing this issue in favor of #97
Is your feature request related to a problem? Please describe.
We’re running our own Docker registry which is on scheduled maintenance during the night. During this time, when Watchtower cannot access the registry, our Slack channels will be flooded with messages:
Describe the solution you'd like
An ideal solution, though obviously quite narrow to our use case, would be, that errors about an unreachable registry are only propagated after x failed attempts, or y minutes.
Describe alternatives you've considered
Alternatively, completely turning off notifications about unreachable registries might work for us as well -- while retaining other info and error notifications. (doesn’t seem to be possible with the current log levels, as the mentioned message is logged with
info
)Additional context
I understand that this is probably a quite “special” case, so I’m not expecting a feature like this. However, I’d like to hear how/if others are dealing with this situation.
The text was updated successfully, but these errors were encountered: