Open blogtutor opened 1 year ago
How about we only send the webhook after a certain number (or percentage?) of cache clear failures? So the site only alerts if there's an actual issue, rather than using Zapier to filter...and sending a notice on every hiccup.
We really only care if a site is consistently having cache clear issues.
@blogtutor Is this still an issue?
Welllllllllll.... I've basically disabled these notifications back in September so I don't know if it's still a thing. Probably is.
Since we're not using the notifications anymore, would it be okay to archive this?
Well, the real issue is that the notifications stopped being useful.
We still care if a site is consistently having cache clear issues - and right now we have no way of getting any insight into that. So maybe we need to step back on this one and rethink the underlying issue and potential fix.
Right now if a cache clear times out, we send a webhook to zapier, which then filters/formats and posts to Slack. This is the biggest "task" user in our Zapier account and we need to pare the account usage down by September.
It should be pretty straightforward to send our webhooks directly to Slack instead. https://api.slack.com/messaging/webhooks
BUT we may also want to revisit this completely, since these notifications aren't particularly useful anymore.