Skip to content
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

[Feedback]: Telegram Notification #1991

Open
JZ-SmartThings opened this issue Mar 9, 2024 · 2 comments
Open

[Feedback]: Telegram Notification #1991

JZ-SmartThings opened this issue Mar 9, 2024 · 2 comments
Labels

Comments

@JZ-SmartThings
Copy link

Doc Page link

https://learn.netdata.cloud/docs/alerts-&-notifications/notifications/agent-dispatched-notifications/telegram

Description

Please remove the minus sign from the Chat ID numbers. It didn't work at all for me with HTTP 400 error until I just removed the minus sign. Then it worked flawlessly. Thank you!

@Ancairon
Copy link
Member

Hey @JZ-SmartThings what type of chat you got? In our docs it mentions Group IDs start with a hyphen, supergroup IDs start with -100

@JZ-SmartThings
Copy link
Author

JZ-SmartThings commented Mar 12, 2024

In the BotFather I just did /newbot then joined it, then wrote an initial message so that it shows up at this URL:

https://api.telegram.org/botXXX:YYY/getUpdates

After getting that, it's just a number without any dashes. It would be the chat.id field of the json. Once I took out the dash which I obviously saw in your instructions, it finally worked. With a dash it did not, said couldn't find chat ID.

Thanks!

UPDATE: it's this field that is documented:
DEFAULT_RECIPIENT_TELEGRAM="-49999333876"

This page shows a good example: https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants