This widget doesn't bounce anymore
Improvement
First, one person complained about the bouncy changelog animation and then many of the others did ๐
So, from now on this changelog doesn't bounce anymore.
Sorry and thanks for the feedback.
First, one person complained about the bouncy changelog animation and then many of the others did ๐
So, from now on this changelog doesn't bounce anymore.
Sorry and thanks for the feedback.
New integrations alert ๐ฃ
Thanks to Divyansh, our new member on our tiny team for building these integrations. More integrations releasing soon
Don't see an integration you want? Head over to our integrations page and fill out your request. Most of these integrations were actually requests from either visitors and our customers.

Thanks to our user for reporting an error in changing phone number section under settings. An edge case which ended in failure to set new phone number has now been fixed.
Some P3 incidents like basic CPU monitoring, auto-scaling alerts could repeat on for a while. In a case like that, mute these incidents alerts immediately.
Our previous update caused a few issues notably with our persistent storage for scheduled unmuting. We are now using the same persistent storage but optimised with a better engine.

Our new dashboard reflects our importance and weightage to ease of managing incidents with clutter free UI focusing back on Simplicity.
To our customers, thank you so much for your support.
Google Cloud integration previously was via Stackdriver which has now changed. We have updated our docs to reflect them.
Check them here ๐ https://docs.spike.sh/integrations-guideline/integrate-google-cloud-with-spike
Not every incident needs a phone call. For all those P3 incidents, use an SMS alert instead ๐

Issue - Single-step escalation policies were getting repeated alerts.
This has been fixed ๐
Some incidents are just info, they are good to know. For such incidents, we support single-step escalation policies where in the info incident will be alerted once.
Best to use our Slack app to get these info alerts
Example escalation policy -


If you are busy fixing the incident or say you are planning on fixing it in the next release cycle then mute the incident alerts.
It will still create incident but you won't be alerted next time.

If an incident has repeated itself then we group them and give you some great insights. You don't have to look at a graph and learn to ignore it with your human-readable insights

PS: No actions needed from your side. Automatically enabled and grouped all previous repeated incidents for all accounts.