Changelog

All new releases and improvements to Spike

Flexible On-calls

You can now build flexible on-call schedules with On-call Layers!

Create different layers to handle weekday/weekend schedules, assign team members for Follow-the-sun model and create overrides. You can also use slots to create on-call shifts for specific parts of the day or week.

ch-on-call-layers.png

Learn more ๐Ÿ‘‰

Request an integration with ease

request-integration.gif

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.

A native Sentry integration

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.

Learn more ๐Ÿ‘‰

Sentry-with-spike.png

Badges for your Git repository

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.

Screenshot 2021-02-08 at 6.13.20 PM.png

Auto-resolve and better suppressing for Grafana integration

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.

Alert rules on Grafana ๐Ÿ‘‰

How to integrate Grafana with Spike.sh ๐Ÿ‘‰

ร— Zoomed Image