Default timezones

When you’re a distributed organization, it can be tricky making sure that everyone’s on the same page time-wise when responding to incidents. To make this easier, we’ve built support for default timezones, so everyone in your organization can view times in the same timezone. No more trying to convert timezones in your head in the middle of an incident!

When your organization has a default timezone configured, times in the dashboard will be displayed in that timezone. The times will also be displayed in your local time when you hover over them. Inputting times will also be interpreted in the default timezone. Your default timezone will also apply in Slack.

If this is a feature that you could benefit from, please contact your Customer Success Manager or help@incident.io.

Required alert attributes

You can now mark alert attributes as 'required,' which means that you expect them to be set on every alert. This is useful for ensuring that attributes used for alert routing will always have a value and that important attributes are consistently set across alert sources.

This will help organizations with vast amounts of alert sources to feel more confident that their alert configuration is set-up correctly. When an attribute is required, we will:

• Warn you if your alert sources are misconfigured, i.e. not setting the required attribute
• Optionally notify you via email or Slack when we receive an alert that is missing a value for a required attribute
• Clearly signal alerts which are missing required attribute values in the dashboard

If you’d like to view more details please see our help doc here.

Custom HTTP alert source

We've rolled out an update to our HTTP alert source, which adds a custom type that allows us to accept any payload using a JavaScript expression to turn it into an alert.

If you’d like to see how this can work, please see our public docs.

What else we’ve shipped