Thanks to all your requests, we have now built over 25 integrations. This is great considering we laucnhed with 5 🙂
In an effort to encourage you to request more of them, we have added an effortless way for you to reach out to us with your integration requests.
Using a tool like DigitalOcean, Linode or Pulseway who doesn't support webhook??!
No problem, use our email integration which will give you a unique email address. Any email sent to this address will create an incident.
Pro tip: You can also setup automatic forwarding from your inbox to our email integration to create incidents.
We are very excited to announce our native integration with Sentry.io. Visit Sentry.io > settings > integrations and you will find us on the page. Install it 2 easy steps and you are ready to get alerts from us for all the application errors and track metrics around it.
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 🙏