Skip to content

Telegram /subscribe self-service for monitoring bot#27

Merged
TaprootFreak merged 1 commit into
developfrom
feat/telegram-subscribe-pattern
Apr 30, 2026
Merged

Telegram /subscribe self-service for monitoring bot#27
TaprootFreak merged 1 commit into
developfrom
feat/telegram-subscribe-pattern

Conversation

@TaprootFreak

Copy link
Copy Markdown
Contributor

Summary

Mirrors d-EURO/monitoring. Same self-service /subscribe pattern, Citreascan explorer link instead of Etherscan.

Test plan

  • npm run build clean
  • /start subscribes, /unsubscribe removes, /help lists commands
  • Critical alert delivered to every subscriber on jdm + jdt stacks

Mirrors d-EURO/monitoring: replaces the single-recipient hardcoded
TELEGRAM_CHAT_ID with the same self-service /subscribe pattern that
the api bot already uses, so each operator opens a private chat with
the bot, sends /start (or /subscribe), and is appended to a persisted
subscriber list. /unsubscribe removes them; /help lists the commands.

- Adds node-telegram-bot-api with polling.
- Replaces TELEGRAM_CHAT_ID with TELEGRAM_GROUPS_JSON pointing at
  /app/.monitoring/telegram.groups.json (mounted as a docker volume).
- broadcast() iterates over every subscriber sequentially.
- Citreascan explorer link instead of Etherscan; otherwise byte-
  identical to d-EURO/monitoring.
@TaprootFreak TaprootFreak marked this pull request as ready for review April 30, 2026 12:46
@TaprootFreak TaprootFreak merged commit aacb060 into develop Apr 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant