Dynamic Routing of Alerts

When creating an alert, you can define to dynamically route the alert according to specific dimension values. This can be especially useful for routing alerts to specific users, for example, account managers of a specific country or region.

To dynamically route an alert:

1. When defining alert notifications for an alert, select the Use Dynamic Routing for this alert checkbox.
   
2. From the Select Dimension dropdown list, select the relevant dimension. The dimensions displayed are relevant for the metrics defined for the alert; for example, Country.
3. Click the Attach a Routing Table button to select a dynamic routing table already uploaded into the Anodot system.
4. Click Select Table to attach the dynamic routing table to the alert. The alert, when triggered, will now be routed to the relevant users.

Notes:

• • You can select an existing dynamic routing table as your routing instructions, or upload a new one.
  • The dynamic routing table must be in CSV format, and consist of three columns with a maximum of 10,000 rows.
  • The values in the left column (the input column) must be unique.
  • The Anodot API can also be used to upload and edit dynamic routing tables.
    
  • Up until August 2022, Anodot only supported dynamic routing via emails, so you may find some dynamic routing files still using the old two-column format. 

Dynamic Routing Tables

Dynamic routing tables are CSV based files which contain three columns

• The dimension (or tag) value by which the routing is done
• The channel name to which the alert will be sent
• The channel type.

Please note:

1. Header line is mandatory (as opposed to previous versions of dynamic routing tables).
2. Important - The channel has to exist before uploading the file. If you attempt to upload a file referring to a channel name which hasn't been created yet - the upload will fail.
3. Possible channel types: 

   • email

   • webhook

   • slackapp

   • slack

   • mattermost

   • pagerduty

   • sns

   • jira

   • opsgenie

   • msteams

   • tamtam

   • telegram

   • servicenow

   • email address
     
     

4. The difference between email and email address - the first is an email channel (as defined in the channels management page) and the second is a specific email address. You may use several emails separated by a semi-colon (;). 
   
   Attached to this article are sample CSV files where the dimension is country and according to the country, the alert is routed to a channel. The first one (multiple channels.csv) uses multiple channels types and the second uses (histbycountrymultiple.csv) multiple mails per dimension value.