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.
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
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.
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 -
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.
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 -
We would love to hear what you think. Ping us on from your dashboard and share your feedback.
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!
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.
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 !
Prometheus and Grafana are the most popular open source solutions out there. We are super proud and excited to have built integrations with them.
Request for an integration and we shall build it
Sematext helps you detect and troubleshoot production and performance issues with logs, metrics, synthetic and real user monitoring (and it helps that their team is quite awesome)
Sematext integrates seamlessly with Spike via custom webhook.