Export incident data using our Singer tap

Incident data can be incredibly powerful - helping you to improve your processes, minimise recurring issues, and ultimately build better products for your customers.

We provide insights within our dashboard but we understand that joining incident data alongside your own can help to improve your understanding even more.

Previously the main method for extracting your incident data was to query our API. We provide endpoints for things like incidents, roles, severities, and much more.

Often though you will want to take that data regularly and store it in a data warehouse such as BigQuery, Redshift, or Snowflake. Doing so can take time to build, test, and maintain. To save you that effort we have now released a Singer tap which you can easily install and run on your own infrastructure.

We’ve built an integration with Singer (an open-source specification) to easily extract your data. The great part about Singer is that a lot of people have already built taps and targets for you - allowing you to simply put the parts together that you need.

To get started using our Singer tap see the project documentation here

We’ve also applied to have our tap approved by Stitch (a platform to run and manage your data-pipelines) who support running Singer taps and targets.

Fallbacks in expressions

You can now add fallbacks to queries in your expressions!

Often when building an expression for a custom field there is a worry that the query might return nothing. This is no longer the case! You can now easily choose what to do should the query return no result.

We use this ourselves when defining the Affected Team in an incident allowing us to safely fallback to the more general “Engineering” when we are unsure which team to involve.

Custom post-mortem names by incident type

Post-mortems come by many names whether it’s debrief, action-review, or learning document - whatever you want to call them you can define that name globally within the post-mortem settings.

Sometimes though, depending on the type of incident that’s occurred, you may want a different name entirely.

You now have the ability to customise the post-mortem name for an incident type within the incident types settings - give it a go!

🚀 What else we’ve shipped