search

eosnetworkfoundation / engineering

A workspace for documentation by Engineering primarily regarding process
MIT License
0 stars 0 forks source link

Create EVM Mainnet Alert Channel Using Telegram Service Account #64

Closed kj4ezj closed 1 year ago

kj4ezj commented 1 year ago

Following engineering issue 57, this ticket is to use the Automation Telegram service account to provision and integrate notification channels for the EVM mainnet infrastructure alerting.

See Also

engineering issue 68 - EVM Monitoring and Alerting - Phase 1

  1. eos-evm issue 602 - Funnel EVM Health Checks into CloudWatch
  2. engineering issue 48 - Collaborate with Operations on Unified Dashboarding Solution
  3. engineering issue 49 - Create Bot to Alert via IM on Specific Metrics
  4. eos-evm issue 603 - SMS Alerting for EVM Infrastructure Health Checks
  5. engineering issue 65 - Email Alerting for EVM Infrastructure Health Checks
  6. telegram-bot issue 1 - Open-Source This Repo
  7. engineering issue 57 - Create Telegram Service Account
  8. engineering issue 58 - Create EVM Testnet Alert Channel Using Telegram Service Account
  9. engineering issue 64 - Create EVM Mainnet Alert Channel Using Telegram Service Account
  10. engineering issue 66 - Fix EVM CloudWatch Alerts
  11. telegram-bot issue 2 - Human-Friendly Alerts
  12. engineering issue 71 - EVM Alerts for APAC Infrastructure
  13. telegram-bot issue 3 - Alert Bot Maintainer via Telegram on Errors
kj4ezj commented 1 year ago

Done. The EVM team was invited to this channel, and the channel has been documented in our internal "ENF Communication Channels" document.

Technically I made a group, not a channel. This will enable subscribers to collaborate on alerts directly in this group instead of having to go somewhere else.