Notifications, Errors and Warnings

NOTIFICATIONS EXPLAINED

Notifications are the platform's way of telling you that something has either completed successfully (Notification), or has gone wrong (Error) or is not performing optimally (Warning) and is need of your attention.

Firstly, there are the notifications. These simply notify you when and if data has been imported correctly to any given destination (DB or file storage).

Errors are flagged when the platform encounters a ‘fatal error’ situation, in which some problem has prevented any data being delivered to the Destination. A Datastream will not function until an error has been fixed.

Warnings are advisories, the process in question has still pushed data to a destination, but there was a non-fatal error during the process that may compromise the quality of the data extract produced.

Notifications, errors and warnings are divided into 5 main subject topics:

Authentication - Notification / Warning / Error

• Notifications are sent to let you know of a successful new user authorization, or the reauthorization of existing credentials.
• Errors and warnings are caused by the change or expiry of the credentials used to authorize a Datastream's Connection. Expired tokens need to be refreshed to re-enable Datastream fetches.

Datastream and Transformation  - Notification / Warning / Error

This will be anything relating to the querying of the API itself and the ‘processing’ of your extract once it has been collected into Datatap.

• Anything that prevents the API query from happening will retrieve and present the error message that came from the API (this will prevent the collection of the data itself).
• Any script that generates an error (this could be missing values or incorrect data types e.g. a string format instead of float, attempting to perform invalid calculations)
• Any error handling that you have set up yourself via scripting, for example:
  • IF statements
  • Flagging duplicates when ‘joining’ Datastreams based on Unique Keys.
• If you need more comprehensive error reports, the mailto: transformation script goes a step further, and is able to collect “sub-tables” of incorrect rows in your data and send them via email.

Import  - Notification / Warning / Error

These are errors that can happen when pushing data to a destination database or file storage. Examples include:

• Errors regarding Unique Key or Unique Index variables
• Exceeding allowed characters
• Primary key is not unique.
  • Solution: Set a key column.
• Primary key too long (MySQL only)
  • Solution: Reduce key string length.
• Column value has too many characters (default size: 200char).
  • Solution: Reduce key string length.
  • Errors encountered during mapping operations. 

Mapping - Notification

Mapping notifications record the successful application of new mapping entries, and include a list of the new field entries along with the Datastream being processed and the stack on which it resides.

Daily Import Status - Notification

Daily Import notifications occur once per day at ~10am CET, and summarize your daily import statistics from all of your active Datastreams on that stack.

CREATING AND EDITING EMAIL NOTIFICATION SETTINGS

1. From the Connect, Enrich or Transfer Elements, open the  Workspace Picker > Administration > then under the Notifications heading of the left-hand menu, click on Email.
2. You will see a list of all existing email addresses that have notifications of some form enabled in this Workspace. Click the email address to edit existing settings, or click +Add to create notifications for a new email address.

You have the following settings options:

• User
  Select the user account that authorizes these notifications.
• Email
  The email address to which notifications will be sent.
• Topics
  Use the drop-down list to select any combination of the 5 topics (explained above) that this email address should be notified of.
• Enabled
  Enable/Disable sending of notifications to this address
• Notify About Empty Extracts
  A separate rule, if ticked emails will additionally be sent to notify the user of any extracts created which contain no actual data.
• Workspaces
  If creating notifications at the Workspace Group level, use the drop-down to select specific Workspaces to receive notifications about. If left blank, notifications will be sent regarding all Workspaces within the parent Workspace Group.
• Datastreams
  Filter notifications to display only those regarding specific Datastreams. If left blank, notifications will be sent regarding all Datastreams within the parent Workspace / Workspace Group.

CREATING AND EDITING SLACK NOTIFICATION SETTINGS

Before enabling Adverity Slack notifications, there are some pre-requisites to be completed within Slack:

1. Create a Slack Channel to which you want all notifications sent.
2. Add an Incoming Webhook App to that channel.

Once the Slack channel is prepared, in the Adverity platform:

1. From the Connect, Enrich or Transfer Elements, open the  Workspace Picker > Administration > then under the Notifications heading of the left-hand menu, click on Slack.
2. You will see a list of all existing Slack subscriptions that have notifications of some form enabled in this Workspace. Click the subscription URL to edit existing settings, or click +Add to create notifications for a new Slack channel.

You have the following settings options:

• User
  Select the user account that authorizes these notifications.
• Webhook URL
  As provided by Slack after following the steps outlined above.
• Channel
  The name of the channel you've created in Slack, to which notifications should be sent e.g. "Adverity [Your Workspace] Notifications".
• Topics
  Use the drop-down list to select any combination of the 5 topics (explained above) that this Slack channel should be notified of.
• Enabled
  Enable/Disable sending of notifications to this channel.
• Notify About Empty Extracts
  A separate rule, if ticked emails will additionally be sent to notify the user of any extracts created which contain no actual data.
• Workspaces
  If creating notifications at the Workspace Group level, use the drop-down to select specific Workspaces to receive notifications about. If left blank, notifications will be sent regarding all Workspaces within the parent Workspace Group.
• Datastreams
  Filter notifications to display only those regarding specific Datastreams. If left blank, notifications will be sent regarding all Datastreams within the parent Workspace / Workspace Group.

CREATING AND EDITING MICROSOFT TEAMS NOTIFICATION SETTINGS

Before enabling Adverity MS Teams notifications, there are some pre-requisites to be completed within MS Teams:

1. Create a Microsoft Teams internal Webhook to allow Adverity to send Notifications to MS Teams.
2. Be sure to take a copy of the Webhook subscription URL, you'll need to paste this into your Adverity Notification settings.

Once the Teams webhook is prepared, in the Adverity platform:

1. From the Connect, Enrich or Transfer Elements, open the  Workspace Picker > Administration > then under the Notifications heading of the left-hand menu, click on Microsoft Teams.
2. You will see a list of all existing MS Teams subscriptions that have notifications of some form enabled in this Workspace. Click the subscription URL to edit existing settings, or click +Add to create notifications for a new MS Teams webhook.

You have the following settings options:

• User
  Select the user account that authorizes these notifications.
• Webhook URL
  As provided by MS Teams after following the steps outlined above.
• Channel
  The name of the channel you've created in MS Teams, to which notifications should be sent e.g. "Adverity [Your Workspace] Notifications".
• Topics
  Use the drop-down list to select any combination of the 5 topics (explained above) that this MS Teams channel should be notified of.
• Enabled
  Enable/Disable sending of notifications to this channel.
• Notify About Empty Extracts
  A separate rule, if ticked emails will additionally be sent to notify the user of any extracts created which contain no actual data.
• Workspaces
  If creating notifications at the Workspace Group level, use the drop-down to select specific Workspaces to receive notifications about. If left blank, notifications will be sent regarding all Workspaces within the parent Workspace Group.
• Datastreams
  Filter notifications to display only those regarding specific Datastreams. If left blank, notifications will be sent regarding all Datastreams within the parent Workspace / Workspace Group.