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
I have run a test run on a machine, and I am using Telegram as notification service.
Unfortunately, It looks like the amount of docker containers that have been updated (10) was a bit too much for Telegram's message length limit, so Watchtower failed to send the report entirely.
This is the message that has been reported instead in the logs:
watchtower-1 | time="2024-11-26T01:11:47+01:00" level=error msg="Failed to send shoutrrr notification" error="Message exceeds the max length" index=0 notify=no service=telegram
Steps to reproduce
Have Watchtower update enough containers to fill the entire size of a telegram message (4096 characters)
Expected behavior
Watchtower should be able to split the message in enough parts to send the entire message to Telegram's servers.
Screenshots
No response
Environment
OS: Ubuntu 22.04.5 LTS x86_64
Host: KVM/QEMU (Standard PC (Q35 + ICH9, 2009) pc-q35-9.0)
Hi there! 👋🏼 As you're new to this repo, we'd like to suggest that you read our code of conduct as well as our contribution guidelines. Thanks a bunch for opening your first issue! 🙏
In case of using pushover for notifications, the message seems to simply be cut off at the API limitation of 1024 4-byte UTF-8 characters, losing the rest of the notifcations entirely.
Maybe some kind of MAX_NOTIFICATION_SIZE Parameter, to split notifcations into enough calls to get the entire notification across would be an idea. I dont know how much of an undertaking to add that would be, probably not insignificant.
Describe the bug
I have run a test run on a machine, and I am using Telegram as notification service.
Unfortunately, It looks like the amount of docker containers that have been updated (10) was a bit too much for Telegram's message length limit, so Watchtower failed to send the report entirely.
This is the message that has been reported instead in the logs:
Steps to reproduce
Have Watchtower update enough containers to fill the entire size of a telegram message (4096 characters)
Expected behavior
Watchtower should be able to split the message in enough parts to send the entire message to Telegram's servers.
Screenshots
No response
Environment
Your logs
Additional context
No response
The text was updated successfully, but these errors were encountered: