Add Telegram downtime/recovery notifications - #19
Open
wittjeff wants to merge 8 commits into
Open
Conversation
Assignees already flag downtime as GitHub issues, but a 3-day production outage (#17) slipped by unseen. Add a Telegram push (token + chatId pulled from repo secrets TELEGRAM_TOKEN / TELEGRAM_CHAT_ID via SECRETS_CONTEXT) so down/up transitions reach a phone directly.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a Telegram notification to
.upptimerc.ymlso downtime/recovery pings a phone directly, on top of the GitHub downtime issue.Why
assignees: wittjeffis already set, yet production issue #17 stayed open ~3 days unnoticed — the GitHub-issue signal alone wasn't loud enough. A Telegram push closes that gap.Secrets required (set before this helps)
The
uptimeworkflow already exposes all secrets to Upptime viaSECRETS_CONTEXT, so no workflow change is needed — just add two repo secrets:TELEGRAM_TOKEN— bot token from @BotfatherTELEGRAM_CHAT_ID— your chat id with that bot (message the bot, thenhttps://api.telegram.org/bot<TOKEN>/getUpdates→result[].message.chat.id, or use @userinfobot)Until both secrets exist the notification is simply skipped; no failures.
Note (separate decision)
Org is on the GitHub Free plan. Flipping this repo private would meter the
*/5uptime cron against the 2,000-min allowance (~8,600+ min/mo needed) and stop monitoring within ~a week, plus take the Pages status site down. Recommend keeping it public, or moving checks to a self-hosted runner if privacy is required.