Skip to content

docs: get Urbex's alerts on Telegram, Discord or a webhook - #100

Open
Teg79 wants to merge 1 commit into
mainfrom
docs/alerts-telegram-discord
Open

Teg79 wants to merge 1 commit into
mainfrom
docs/alerts-telegram-discord

Conversation

@Teg79

@Teg79 Teg79 commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

The docs for urbforge/urbex-cli#131, Urbex's alerts to Telegram, Discord or a webhook:

  • docs/cookbook.md: Get the alerts on Telegram or Discord:

    • the bot from BotFather, and the chat id with getUpdates;
    • Discord's webhook;
    • urbex-op set, the YAML, urbex bootstrap, then urbex doctor --test-alerts;
    • what a message looks like, grouping and repeat;
    • that Urbex then owns Grafana's notification policies.

    The disk recipe points to it.

  • docs/reference/platform-config.md: observability.alerts.telegram.chatId, .discord, .webhook.

  • docs/reference/credentials.md: Required with alert channels, with the three keys, and the summary table.

  • docs/reference/cli.md: urbex doctor --test-alerts, and the alerts group.

  • docs/known-limitations.md, docs/status.md: the alerts notify through a channel now; the policies are Urbex's once it has one.

  • CHANGELOG.md: a Docs line.

Depends on urbforge/urbex-cli#131.

Why

urbforge/urbex-cli#95.

Tests I ran

  • Relative links and anchors of the changed pages resolve. tests/plugin-scripts.sh passes.
  • The steps followed on the lab with a test bot (see the CLI PR).

Checklist before review

  • Linked issue, Conventional Commit title
  • No secrets, tokens or private addresses

Part of urbforge/urbex-cli#95.

🤖 Generated with Claude Code

https://claude.ai/code/session_0182yxsfwRowwnxCfgrQwjnA

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.

2 participants