Intelligent incident management: Less noise, more control

Intelligent incident management: Less noise, more control

Here’s a new way to keep calm and carry on (in data observability, at least). Metaplane’s upgraded incident management now comes with intelligent incident grouping, so your Slack alerts don’t light up like a disco ball every time a table blinks. For example, if a base table shows an unusual spike in row counts, and its downstream tables follow suit, Metaplane will group these into one tidy incident instead of flooding you with separate alerts.

We've also added powerful incident management features to help your team stay coordinated:

• Assign incident owners and custom labels so everyone knows who’s on call for each incident (think of it like “who’s on first?” but made simple)
• Set auto-resolve rules and failure thresholds to keep your incident list clean and actionable. This way, you won’t be pinged for every little blip that comes and goes.

With these updates, you can focus on the real issues, like tracking down who committed that rogue SQL or figuring out who actually broke the build this time.

Incident ownership made easy

Never wonder who's handling an incident again. Assign owners directly from Slack notifications or the web app, with automatic @mentions when Slack identities are configured. Because nothing says “accountability” like a friendly nudge from Slack.

Learn how to assign incident owners →

Label & track incidents your way

Need to let the team know where an incident stands? Our new custom incident labels are like Post-it Notes for your incidents. Whether you're investigating, waiting on a fix, or need more info, labels make it easy to communicate status. Now, you can filter incidents by label, so you only see the ones that are relevant to you.
Learn about adding labels →

Automatically close those dusty incidents

Is your incident list looking a little stale?  Auto-resolve rules are here to close out those long-running, low-priority issues while preserving labeled incidents and freshness monitors that need special attention. Think of it like spring cleaning for your incident queue—except you don’t have to lift a finger.
Read about incident settings →

Threshold controls for smarter alerts

Not every blip needs attention. Customize failure thresholds per monitor to ensure you only get alerted when issues persist. Configure globally or customize per monitor to match your data's unique behavior patterns.
Learn about configuring monitors →