We have added support for even more integrations! Our newest integrations are Checkly (API monitoring), AppSignal (errors and performance tracking), Stackify (performance monitoring), Scout (performance monitoring), Oh Dear! (uptime monitoring) and Site24x7 (performance monitoring).
Quickly access incidents for your service or integration by adding the Spike.sh badge to your Git repo. You can add the badge to the README file on your Github or Gitlab repo, or to any Markdown file.
You can now archive integrations that you don’t need so they don’t show up on your dashboard. We’ve also added archive support for escalation policies.
Silence alerts for a period of time by setting a vacation mode for your account. When you are ready to resume alerts, just go back and remove the vacation mode. It's that easy.
We couldn’t be happier about this release. A very simple on-call scheduling and rotation with custom options (12 hours, 2 days, etc).
You can add as many people in rotations and you can choose to create multiple schedules too. With the ease of flexible calendar with multi-time zone support, it’s easy for remote teams to get started too.
Issue - Similar incidents would not be suppressed and instead created new ones.
Good - We continued to alert and notify the user, no stopping us there
Bad - It could be annoying to get continuous alerts when you might already be working on fixing it
We will be using the Alert rules you set in Grafana to group and suppress repeated incidents when in the non-resolved state.
💡Auto resolve (action needed from you)
Grafana integration now supports auto-resolve as well. You will need to setup the conditions in Grafana for Ok state.
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 🙏
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 !
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