Migrating your custom SQL monitor alert rules

As mentioned in our recent changelog post, alert routing rules based on custom SQL monitors will be going away. Instead, we suggest you use tag-based alert rules to route your custom SQL monitor alerts to the appropriate Slack, MS Teams, email, or PagerDuty destination. But first, let's talk about what tags in Metaplane are.

Tags in Metaplane

Tags are the best way to organize your data assets in Metaplane. If you use dbt and you tag your models there, we'll pull those tags into Metaplane. Otherwise, you can add a tag to any table or monitor with the tag of your choice, and tables and monitors can have more than one tag.

Tags also have some useful functionality in Metaplane, including being able to view all the associated tables and monitors on a dashboard, organizing incidents, and, yes, routing a set of alerts to a particular alert destination.

Migrating your alert rules

If you have alert rules based on custom SQL monitors, you'll see the following message in your alert settings (Settings > Alerts).

Next to every custom SQL monitor alert rule, you'll see a purple "Migrate" button. When you click on that button, you'll see the ability to select a tag to add to that monitor.

If you don't have any tags, or you want to use a new tag for your alert routing rules, simply type in the name of the tag you want to add, then click "Create new tag."

If you have multiple custom SQL monitor alert rules for a particular alert destination, we'll ask you if you want to apply that new tag to all of them.

Once you click "Migrate", we'll automatically apply those tags and create the appropriate alert rule.

That's all you need to do in order to get your alert rules migrated over. If you run into any issues, don't hesitate to reach out to the Metaplane team for help.