Migrating legacy email settings
Last updated
Was this helpful?
Last updated
Was this helpful?
In March 2025, we've reworked the infrastructure behind our email alert source, enabling all common features for an email alert source too. With this, some settings have changed and were replaced by new, even more powerful features. The following will cover the steps needed to achieve the equivalent in settings when migrating from old to new.
Conditions from the legacy email filter are defined in the same way with the alert source's . Using the , more fields and functions to build conditions are now available.
For time-based and no grouping the grouping options with the same name are used. Content-based grouping can be achieved through AI-based similarity grouping, more info .
Previously, only the email subject and body could be used for alert key extraction, the new based definition allows for any of the event's fields plus new functions for extracting an alert key.
Adding rules for resolving an alert is now done by creating a resolve alert rule. They are defined like the event filter using . An improvement over the old design is the ability to create rules for not only resolving, but also creating and accepting alerts.
With the new email alert source, the mail log was replaced in favor of the . But as before all incoming mails plus more data for each received mail is shown there, even if they did not create an alert.
