Closed bjcone closed 6 years ago
Thanks for reporting this, this is definitely an issue with the plugin. I'll update you once I've fixed it 😃
I am also facing the same issue. Is this issue fixed? If yes, then what I have to do to send notification to telegram bot successfully.
I have restarted the graylog server after that when I send test notification I receive this error
WARN [TelegramAlert] Error removing old webhook
INFO [TelegramAlert] Alert was initialized successfully
WARN [TelegramAlert] Error sending message
Thanks, Nishit Shah
Awaiting your response.
Any news? Why this plugin requires webhook?
Hi,
I fixed the issue with the release v2.0.0. I also restructured and updated the plugin to be able to make use of the template engine. As this is a breaking change you'll have to delete the old Telegram Alert notification(s) and create a new one (but this is only a matter of seconds so there's nothing to worry about).
Let me know what you think about the new version, suggestions are welcome.
We're using this in our logging cluster to send alerts to different channels in Telegram. After about a month of running, the logs on our Graylog instance are filled with:
ERROR: Telegram Bots Api - BOTSESSION org.telegram.telegrambots.exceptions.TelegramApiRequestException: Error getting updates at org.telegram.telegrambots.api.methods.updates.GetUpdates.deserializeResponse(GetUpdates.java:119) ~[telegram-alert.jar:?] at org.telegram.telegrambots.updatesreceivers.DefaultBotSession$ReaderThread.getUpdatesFromServer(DefaultBotSession.java:256) ~[telegram-alert.jar:?] at org.telegram.telegrambots.updatesreceivers.DefaultBotSession$ReaderThread.run(DefaultBotSession.java:187) [telegram-alert.jar:?]
Is this a configuration issue, environment issue, or an issue with the plugin?