Notification Settings
This article explains the settings and operations associated with different types of notifications provided by Nexla for data monitoring. For more information about the types of notifications that Nexla provides, see Nexla Notification Types.
1. What are Notifications in Nexla?
Nexla maintains and provides detailed monitoring information for all resources within the platform. Users can be alerted of this information via notifications that provide information about resource functions and history, as well as full resource audit logs. Notifications typically correspond to events or status changes associated with a particular resource. The monitoring endpoints corresponding to notifications can also be used as Nexla sources for automating data flows based on monitoring events.
2. View All Unread Notifications within Nexla
Click the
icon in the top right corner of the screen to view all unread Nexla notifications in a dropdown menu.
The number displayed on the icon indicates the number of unread notifications.
Optional: To mark a single notification as read, click the
symbol to the right of it.
Optional: To mark all notifications as read, click
in the top right corner of the menu.
3. View All Notifications for a Single Data Source, Nexset, Data Flow, or Destination
Select the desired data source, Nexset, data flow, or destination to open an interaction window on the right.
Select the
tab to view all notifications associated with the selection.
Some notifications include links to additional items, such as Nexsets. These links can be clicked to interact with the indicated item.
Optional: Use the "Sort By" dropdown menu on the left to select whether notifications shown in order from newest to oldest or oldest to newest.
Optional: Use the "Items Per Page" dropdown menu on the right to select the number of notifications that Nexla will show in each page. To navigate to a particular page, enter the page number in the "Page" field to the left of the dropdown menu.
Optional: To delete a notification, click the
button to the right of it.
4. Configure Notification Settings
Hover over
on the menu on the left side of the screen.
Select "Notification Management" from the dropdown menu that appears to the access notification settings page.
In the "Configure Notification Settings" panel, select the
,
, or
tab to access settings for notifications in the corresponding category.
The Platform Activity tab provides access to settings for platform-level activity notifications, e.g., Nexset sharing, account creation, etc.
The System Alerts tab provides access to settings for user data system-level notifications, e.g., Nexset creation, schema changes, etc.
The Data Alerts tab provides access to settings for data-level notifications, e.g., data volume changes, data source reads, etc.
For a complete listing and definitions of Nexla's notifications, see Nexla Notification Types.
In line with each notification type, a box is listed to the right under the delivery method categories
,
,
, and
. To receive a listed notification type by one of these methods, check the corresponding box under the desired delivery method category:
– This notifies the user of the corresponding changes within the app, as indicated in step 2.
– This notifies the user of the corresponding changes by email.
– This notifies the user of the corresponding changes via Slack messages.
– This sends notifications of the corresponding changes to other apps via webhooks.
Nexla can be configured to deliver each notification type by any number of the listed methods. Users can select as many or as few notification delivery methods as desired by checking the appropriate box(es).
Once a
is displayed under a delivery method category for a particular notification type, the user will receive notifications of this type by the indicated method.
To prevent Nexla from providing a particular type of notification, ensure that no delivery method boxes are checked for that notification type.
5. Email Delivery Configuration
To input and/or change information related to the notification delivery channels to be used by Nexla, scroll to the bottom of the Notification Management page to view the "Configure Channels" panel.
Select the
tab to specify or change the email address to which Nexla should send notifications according to the selections described in Section 4.
Enter the desired email address(es) in the the "Emails to be Notified" field. Use a semicolon followed by a single space to separate multiple email addresses.
Nexla will now deliver notification types for which the email delivery method has been selected to the specified address(es).
6. Slack Delivery Configuration
To input and/or change information related to the notification delivery channels to be used by Nexla, scroll to the bottom of the Notification Management page to view the "Configure Channels" panel.
Select the
tab to specify a Slack channel to which Nexla should send notifications according to the selections described in Section 4.
Nexla delivers notifications to Slack through an incoming webhook.
Click
to open a new tab on the Slack website, and follow the instructions provided to create and copy an incoming webhook for the Slack channel where notifications should be posted.
Return to Nexla, and paste the generated webhook into the "Slack Webhook URL" field that appears below the button used in the previous step.
Nexla will now deliver notification types for which the Slack delivery method has been selected to the Slack channel corresponding to the entered webhook.
7. Webhook Delivery Configuration
To input and/or change information related to the notification delivery channels to be used by Nexla, scroll to the bottom of the Notification Management page to view the "Configure Channels" panel.
Select the
tab to input an incoming webhook that Nexla should use to deliver notifications to another app according to the selections described in Section 4.
Create an incoming webhook for the desired app, and paste the URL into the "Webhook URL" field.
Nexla will now deliver notification types for which the webhook delivery method has been selected to another app using the entered webhook.