Since we released the new alerting earlier this year, there was not really a way to easily manage your alerts. While alerts were now more flexible than ever, we made them harder to manage: you had to configure them for every individual monitor or server by hand.
Previously, we had tags. But those were removed in favour of the new alerting. But now, to solve all these complaints and to make Spectate even more efficient to use, we're introducing Projects in this month's changelog.
What's new?
- Projects are here
You can now create multiple projects in your team and organise monitors and servers. This way, you no longer have to define alert and metric condition policies for every monitor individually. - Added a Microsoft Teams integration for alerts.
Improvements
- We no longer send "No data received from host" alerts if our ingest queue is delayed.
This is just an extra safety net in case of an incident on our side. - Improved status page responses by adding the reasons of e.g. a 404 or 403 in the body.
- We have added an option to inherit alert policies from the monitor's project
Other changes
- Fixed an issue with Discord notifications not being sent when fields contain a number.
- Fixed an issue where sometimes a host metric incident does not resolve correctly.
- Fixed an issue with rate limits being hit too frequently for status pages.
- Fixed an issue where you could not remove alert policies in the UI.