Closed Chriscbr closed 10 months ago
Thanks for reporting - we have plans to switch from BetterUptime to Sentry, so marking this as p3 for now
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
Hi,
This issue hasn't seen activity in 60 days. Therefore, we are marking this issue as stale for now. It will be closed after 7 days. Feel free to re-open this issue when there's an update or relevant information to be added. Thanks!
@Chriscbr did you see that lately? I'm not sure if we should keep it
I haven't ran into it lately, but I've been avoiding the problem by waiting a few hours before resolving incidents on PagerDuty
Closing for now
Sometimes, a monitoring incident on BetterUptime getting auto-resolved results in a new PagerDuty incident getting created, resulting in a maintainer getting paged.
Example: https://uptime.betterstack.com/team/48207/incidents/416200671 (screenshot from BetterUptime)