View profile

#2 - Introducing Support member role, improved escalations and optimized Mute feature

Thanks for reading our second changelog and updates edition. Let us know if you have any feedback. We
#2 - Introducing Support member role, improved escalations and optimized Mute feature
By Team at Spike.sh • Issue #2 • View online
Thanks for reading our second changelog and updates edition. Let us know if you have any feedback. We also post updates on Twitter.

Add your support members
We are happy to introduce Support member role. Anyone with Support role can be added in escalation policies to send alerts so they are notified of issues when customers get affected.
Support member role cannot change the status of an incident. Read more..
Improved escalations
  • We have fixed a number of issues and optimised the way escalations works.
  • We have started migrating from using Redis mechanism for escalations to a persistent scheduler

Mute alerts for incidents
Muting alerts is now more stable as we moved to the persistent scheduler which will scale easily for us.
Would you like to mute alerts when you get a phone call? Let us know by replying.

More security updates
You could never be more secure, this is a thing right?
After the last incident wherein scammers signed up and looted us off $875 (link to article), we have been staying up to date with all patches, however little. Screenshot from Needle.sh doing the good deed of blocking scanners and unnecessary bots for us.
Blocking all scanners and bots
Blocking all scanners and bots
—-
What we are writing 📝
What we are reading 👓
Did you enjoy this issue?
Team at Spike.sh

Building a 'Simple' incident management platform is NOT that simple.

Subscribe to learn, track our progress and get updates with our newsletter - which mainly consists of changelogs and some resources we like to share 🤷‍♀️

If you don't want these updates anymore, please unsubscribe here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue