Fix

Issue - Not all Slack channels were displayed in the drop down in escalations policy.

This happened primarily with customers having more than 50 channels. We have upgraded our Slack app to omit the soon-to-be-deprecated methods and now list 1,500 channels.

Thank you for reporting this 🙏

New feature

We recently built and deploy Librato integration. If you are on Solarwinds stack, this is a nifty addition. Read the guide and let us know if you have questions !

How to integrate Spike.sh with Librato 👉

New feature

We are bringing in a more granular control over sharing incidents publicly. You can now choose to share incidents with your team members, embed them in documents and more.

Don't want to share? That's cool - you can also disable sharing of all incidents on the new organisation settings.

Learn more about sharing 👉

Fix

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 👉

Improvement

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 👉

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.

New feature

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.

New feature

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!

New feature

We are happy to have auto resolution built into Prometheus. Each prometheus alerts usually have a fingerprint which is used to identify already existing incident which is then automatically resolved.

Improvement

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 !