Magicians never share their secrets. But we do. Sign up for our Ruby Magic email series and receive deep insights about garbage collection, memory allocation, concurrency and much more.
The Incident page for errors and performance incidents is one of the most used pages in our application. It is where you land from a notification. Often, that doesn’t mean good things.
Today, we are launching two improvements to that page:
More context for each incident
The ability to add notes to incidents
The context for incidents shows you what’s going on at the time of the faulty request. We already showed host metrics, but we are now adding:
Did any (other) errors occur?
What performance issues were happening?
Were any Anomaly Detection Alerts active at the same time?
With these, it is easier to see if the root cause for an Incident could lie somewhere else, or if multiple Incidents are related.
We understand that for many issues, it’s the combination of technical and historical knowledge that enables you to solve them. When you visit an Error or Performance incident, you can now leave a note for your colleagues or future you.
The incident notes make it easy to add information to an error or performance incident. With relevant knowledge stored right at the place where you’re looking when fixing an issue, you can save others (and yourself) from starting from zero again in the future. E.g., leave a note about how to solve the incident, or note the steps you took to prevent it from happening again.
Though we don’t wish any incidents upon you, we can’t wait to hear how you are using this, and how you’d like us to continue improving it.