Open mastercactapus opened 9 months ago
A good experience will rely heavily on #3007
Current state reference info
Worth noting that the current operation requires remote monitor to be deployed with a config file with various required settings, it's own twilio number, and be publicly-routable
For next steps:
MVP: minimal API/db additions to allow create alert -> heartbeat using webhook on an EP
+1: auto sync on-call users +1: auto config from production/main instance
+2: "sentinel mode" -- slimmer UI, warning banner, make it obvious an instance is for monitoring another (with link) +3: first time setup /w sentinel
Separate supporting feature ideas:
Implementation thoughts/notes:
What problem would you like to solve? Please describe: There is a need for a feature to facilitate the monitoring of a GoAlert production instance employing distinct installations of GoAlert. While certain elements of this process are partially implemented, they are not documented, complex, and possibly outdated.
Describe the solution you'd like: A new admin page for Remote Monitor to streamline the configuration and operation of these monitoring services. Features required:
Describe alternatives you've considered: The current procedure involves a command, 'monitor', and the 'remotemonitor' package, to create and manage added complexity redundancy measures.
Additional context: This feature request caters primarily to the admins responsible for a GoAlert installation rather than the application's end users.