-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Email reports/summaries #40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Great idea! I'll work on a mock-up for the content. We can also include deployment-related health notifications in the report. |
Absolutely! Email summaries might be an opportunity to implement more targeted features like Coder Operational Report or Templates Report. I can tackle this problem next sprint. This week (until Friday) we could come up with 2-3 sample emails. Probably, it will be worth implementing a switch to let operators enable/disable these summaries. |
I'm going to write a mini RFC for this 👍 |
Related: #16 (comment)
Deployments with a large user base (100+ users) may be susceptible to spikes in automatic build failures. For instance, if a faulty template version is applied to all workspaces (100+), implementing notifications for automatic build failures sent to template admins could result in a flood of emails (or webhook calls).
An alternative solution is to implement a mechanism that sends a daily summary to template admins, aggregating information on workspace builds and build failures.
Please let me know your thoughts.
cc @stirby
The text was updated successfully, but these errors were encountered: