A short guide to receiving LinkVion gateway alarms on Telegram. The full guide with screenshots is on our Naver café (Korean).
Applies from the release after 0.1.0.24. Up to 0.1.0.24, settings entered on screen could fail to take effect or be lost on restart, and the Mac package had no Telegram module.
1. Create a bot in Telegram
- Open a chat with BotFather in Telegram and send
/newbot. It costs nothing. - Keep the bot token BotFather gives you private.
- The person who will receive notices (or a group the bot was added to) sends the bot one message. A bot can only message chats that spoke to it first.
- Open
https://api.telegram.org/bot<bot token>/getUpdatesand find the number in"chat":{"id": …}. That is the Chat ID (groups and channels start with-100).
The gateway must be able to reach api.telegram.org over HTTPS. Notices cannot be sent from an isolated network.
2. Enter it in the gateway
- Under Monitoring › Alarms › Notification settings, turn on Telegram, enter the bot token and Chat ID, and save. Saving applies at once, with no restart.
- Only administrators (admin) can change these settings. Other accounts can send a test message.
- A saved token is never shown again on screen or in settings exports; it appears masked.
- To keep it after a restart, save the project as well (Telegram settings live in the project).
3. Send a test
Send test sends one test message. If it fails, the reason Telegram returned is shown as is — for example 401 Unauthorized means a wrong token, and chat not found means a wrong Chat ID or nobody has messaged the bot yet.
4. Choose Telegram on alarm rules
Each rule must have Telegram selected as a notification channel. New rules default to on-screen only. Messages are sent only when an alarm is raised, not on clear or acknowledge.
The default message is [{severity}] {tagId} = {value} ({condition} {threshold}), which can be changed in the message template. Scripts can send Telegram messages too.
If you get stuck, send us the status-line text by email or on the café.