Backfilling of Incidents continues to ramp up with new exciting additions to its feature list, and a new important feature added to its arsenal is the backfill of incidents.

As we all know, Locale helps create incidents based on an alert trigger, that runs periodically on the data source. Every time a new row of data matches the trigger condition, an incident is created. However, users now can create incidents for all the earlier existing rows in the data source, that match the trigger conditions as well, ensuring that previous rows of data can also now be set as incidents on Locale, maintaining thus a repository of all incidents within Locale.

Alert Creation with Backfilling of Incidents

Step 1: In the alert creation process, choose the data source that you would need to set up the alert and create the query.

Step 2: Once the data is set up, configure the incident details.

Step 3: Assign the incident to a stakeholder, either manually via the drop-down or through dynamic assignment.

Step 4: Add a notification stream to alert stakeholders once an incident is triggered and click on “Publish Alert” to finish setting up the alert!

Step 5: Immediately after the alert is published, users will be able to see an option to backfill incidents that are present in the data source which matches the trigger conditions, and can create them as incidents on

Points to keep in mind

  1. Backfilling will only happen if there are earlier rows of data that match the alert triggers.
  2. The backfill option will only be available until a new row of data that matches the trigger is identified. Hence the backfill must be completed immediately after alert creation.
  3. The notifications for the backfilled incidents work the same way as normal incidents. Notifications can be sent via the channels set up and grouping will also take place if the count of incidents created is greater than 5.