-
Notifications
You must be signed in to change notification settings - Fork 854
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
Additional notification options #264
Comments
I like it, just wish Pushover were higher. 😇 I can help test that and Webhooks when the time comes. Also for Webhooks please consider header support if possible, for Bearer authentication. |
Lets move it up a bit then :) |
These will be solved by replacing the current notification implementation with another project I'm working on; containrrr/shoutrrrr. Whether or not this will be in 0.4.0 or in a later release is not yet written in stone and depends a lot on whether im doing it by myself or with help. 😄 |
Discord, telegram, slack and pushover are all implemented in shoutrrr as of 5314ee954ba8dbc1c6eb6cbde310af695c8ae1da. Will implement a couple more before i'll even attempt integrating it. |
FWIW... I'm no Go expert, but I did made a little test run using a Pushover URL in Shoutrrr and it worked fine. :) |
Just to say, HTTP webhook is a killer feature imo. |
Neat, so we should wait until the shoutrrr code is in watchtower to use Telegram notifications? |
Yeah. Feel free to help out though if you want it to happen sooner rather than later! :-) |
Just to be sure: would it be possible to integrate more than one service with shoutrrr? |
yeah, that's our thought exactly! 👍 we've not really decided on how to do this in the case of watchtower, but yes - that will be possible in a general. |
Just voicing my interest in the Telegram notifications. From the comments above it seems the wait is due to shoutrrr not being used in watchtower just yet. What's the progress on that? |
#405 should be taken into consideration when migrating to shoutrrr. |
Hey guys, maybe like for temporary solution |
Are there updates for notifications on Telegram? |
Unfortunately not. I've not had any time to work on switching the current notification module to shoutrrr. |
@simskij how much work to you suspect this will be? I haven't looked at the code at all, but are also craving for telegram and webhook support. |
Telegram's Bot API are very simple to use, but I don't know how to implement it since I don't know Go For example to send a message (It also works with POST): |
@davtur19 Telegram seems to be implemented already. containrrr/shoutrrr#2 |
@mbrandau yes, but has not yet been implemented/documented in |
@davtur19 the problem is that watchtower needs to move to use shoutrrr and that's not been done yet. |
I will try to add shoutrrr as another notification type. WIP PR coming in soon. I have no experience in Go though 🙃 |
No better time to learn a new programming language than during quarantine! 😅 |
One feature I’m missing while testing the new notifications on latest-dev is to disable the timestamps. Since I think most of the services show timestamps anyway, I think there should be an option to disable and/or format them in watchtower. |
Agree, @mbrandau. The combination of timestamp, level and message doesn't really help on readability. Maybe an environment variable with a template string to use? |
Shoutrrr support will be included in the next release. It's already been merged to master, so I will go ahead and close this issue now. 🎉 Thank you so much everyone for your contributions! |
To avoid important communication to get lost in a closed issues no one monitors, I'll go ahead and lock this issue. If you want to continue the discussion, please open a new issue. Thank you! 🙏🏼 |
Moving this discussion to a issue in shoutrrr.
Thanks for understanding! 🙏
The text was updated successfully, but these errors were encountered: