This issue talks about On-call, UI and UX change with more reliability from our end.
On-call management v0.1 is here
We couldn’t be happier about this release. A very simple on-call scheduling and rotation with custom options. 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. Learn more
Librato integration is here
Improved Grafana integration for better grouping and suppressing alerts
Webhook integrations now support auto-resolve
Our integrations microservice is more robust with parsing JSON to Human-readable text so when the alert reaches your phone, you know exactly what it is
We have now alerted for over a million incidents, thanks to you !
Escalations will now be repeated no more than 5 times
Better control over privacy to enable/disable public sharing of incidents
You can now alert your team members to verify their email and phone number
Incident details are now far more elaborate and easier to read
You can now also reply to email alert with @ack and @res to take actions on an incident
Recently the team I work with completed a project to allow Shopify to run in
multiple datacenters. This project
was a refactoring project in disguise. When you undertake large refactoring of a
code-base with 100s of developers and 100,000s of lines of code, you can’t align
by sending an email. The merge-conflicts a single pull request would entail
makes me shiver. When deprecating in a large code-base the only way to reliably
avoid new deprecated behaviour is a failing test that tells you what to do.
Otherwise the pace that new deprecated code is introduced can easily outpace the
speed at which you can remove them, or be a massive source of frustration.
We are working on adding resources to help you make better use of Spike.sh. If you are interested in collaborating on content or read through before we hit publish then let us know. Any form of collaboration is appreciated 😊