Changelog

All new releases and improvements to Spike

Actionable phone calls fixed

Our vendors providing calls had blocked our account for too many retries for a phone number which was not reachable.

Thankfully, we have been working on getting vendor-agnostic for these tough times. Thus, we have immediately moved to another vendor but this ended in disabling inputs on phone calls for the last 24 hours.

We have now fixed this issue. This means on a phone call, you can continue to take actions like -

press 4 to acknowledge

press 6 to resolve

press 9 to escalate

More about changing incident status 👉

Report incident parsing issue with a single click

spike-incident-parsing-fail-report.gif

After you add an integration, we convert the JSON data of your incident into human-readable text. Sometimes, it fails 🤷‍♀️and you end up ignoring it, perhaps.

We want you to be able to easily communicate these issues, flawlessly. This is why we have built a single click reporting as demonstrated above.

This parsing does NOT affect alerts. You will continue to receive them.

Learn more about parsing fail 👉

Sentry.io integration update

We are working with the amazing team at Sentry to build a native integration. If you have an already existing Sentry integration then we will send you docs on how to upgrade.Until then, no action is needed from you

Below are some of the benefits -

  1. Install Spike.sh from Sentry's settings
  2. You can utilise the new and advanced Alerts feature from Sentry with Spike.sh
  3. Our native integration will be far more reliable in terms of incident reporting

We would encourage you to wait for a few days until Sentry and Spike.sh works this out.

Thank you for your patience, we truly appreciate it.

☎️ We now attempt your call more than once

In an effort to absolutely make sure our calls are reaching you, we took your feedback and expedited our fail-safe feature for phone calls. I am glad to inform you that v1.0 has been enabled on your account.

What does this mean?

This means we will attempt to call you again if one of the below happens -

  1. We failed to connect to your phone
  2. You did not answer our call (will definitely wake you up and break DND settings in emergencies)
  3. Your phone was busy
  4. You decided to cut our call

We would love to hear what you think. Ping us on from your dashboard and share your feedback.

📱 Dashboard, built for Mobile browsers

You don't have to login to your laptop just because you missed an alert from us. Login to our dashboard on your mobile to check open incidents and resolve them

Can't wait for your feedback to roll in 🤞. We have also made it easy by not creating a different URL for mobile. Same dashboard, same link in a different skin for mobile!

mobile view (1).png

Slack notifications to give you a gist 🔥👩‍💻✅

Small enhancements for our Slack app - we now send incident messages in notification previews.

Each emoji in preview represents the state of incident -

🔥 - triggered

👩‍💻 - acknowledged

⏱ - acknowledge timeout

✅ - resolved

We have also fixed a 🐞which was resulting in no notifications if incident message fails to parse.

Fail-safe kicks in and notifications are now flawlessly sent. Below is an example when parsing works and when it fails.

Thank you for reporting this !

Screenshot 2020-08-13 at 1.05.54 PM.png

× Zoomed Image