On this Page
Alerts (also know as Activity Log Notifications or just Notifications) provide a way for Org admins to track changes to alerts within their organization.
Event Types
You can choose from the following event types and assign recipients.
Dist
This is for Snap Packs. For this event type, you must also specify the Recipients.
- Dist override: when there is a change in the Snap Pack asset label.
- Dist change: when there is change in the Snap Pack asset FQID.
ACL
For this event type, you must also specify the Projects to notify and Recipients.
- ACL remove: when permission is removed from an asset
- ACL add: when a permission is added to the asset
Snaplex Node
For this event type, you must specify the Snaplex, the threshold or load value for the target Snaplex, and the recipients.
- Snaplex node memory usage: when the threshold is exceeded.
For the threshold value, enter the value as an integer between 50 and 100. Snaplex node cpu load avg: when the average CPU load is exceeded.
For the load value, enter an integer.A separate alert and email is sent for each JCC node in the Snaplex when a Notification threshold is exceeded. When you remove a Notification while there is an existing alert for it, the Notification is closed shortly thereafter.
- Snaplex node disk usage: when available disk space falls below the threshold value.
Specify Type of Disk Space and Name of Disk Space. For the threshold value, enter the value for free space available. When the free space available falls below this value, the alert notification is triggered.- If the type and name fields are not specified, then the check is done for all mounts, except system mounts: /proc, tmpfs, devtmpfs, rootfs.
- If the type is specified and not the name, the check is done for all the mounts of the given type.
- If the name is specified but not the type, the check is done for all the mounts with that given name and all mount types, except system mounts.
Session
For this event type, you must also specify the Recipients.
- Session end: when a user session ends.
- Session start: when a user session is created.
Asset
For this event type, you must also specify the Projects to notify and Recipients.
- Asset delete: when an asset is deleted.
- Asset owner change: when the owner of an asset is changed.
- Asset rename: when an asset is renamed
- Asset update: when an asset is updated
- Asset create: when an asset is created
- Asset move: when an asset is moved between projects.
API
For this event type, you must also specify the Threshold and Recipients.
- Daily API usage: notifies of daily API usage.
- Concurrent API usage: notifies of concurrent API usage.
Snaplex
For this event type, you must also specify the Recipients.
Group
For this event type, you must also specify the Recipients.
- Group delete: when a group is deleted
- Group update: when a group is updated
- Group create: when a group is created
User
For this event type, you must also specify the Recipients.
- User authentication failure: when user authentication failed.
- Password reset: when a user's password has been reset.
- User unlock: when a user is unlocked.
- User lockout: when a user is locked out.
- User create: when a new user is created.
- User update: when a user is updated.
- Password change: when a user's password is changed.
- User delete: when a user is deleted.
About Alerts
Setting an Alert
You must be an Org admin to set Alerts.
- In SnapLogic Manager, scroll down to Alerts/Activity Log Notifications and click Settings:
The Settings > Notifications page appears. - Click Create Notification; the Create Notification Rule dialog appears.
- In the Create Notification Rule dialog, click Please select an event type to invoke the drop-down menu:
- Select the target Event Type and enter information for the displayed fields, which vary depending on the Event Type.
Viewing Alert Information
- In SnapLogic Manager, click Alerts; a list of all the alerts in the Org are displayed.
- Enter the target Start and End dates to filer the Notifications by time period. You can also filter this information by clicking the specific alert status tab:
- All (default)
- Open
- Closed
- (Optional) Click the icon to download as a CSV file.
Deleting an Alert
- In SnapLogic Manager, click Alerts/Activity Log Notifications.
- Click the icon by the Alert that you want to delete.
Use Alerts to Track Snaplex Congestion
Snaplex alerts are generated in the following situations:
One or more Pipelines have been in the Queued state on a Snaplex for more than 75% of their respective Time To Live (TTL) or the maximum time that SnapLogic attempts to execute a Pipeline. At most, one alert is generated per Snaplex regardless of the number of Pipelines over the threshold. The default Pipeline TTL is 5 minutes.
The daily API usage exceeded is 75% of the limit.
The concurrent API usage exceeded is 75% of the limit.
When a Snaplex congestion Alert is opened, it is worth investigating the cause of that Alert. Seeing the queuing Alert frequently typically indicates that more capacity needs to be added to that Snaplex or that the Pipelines being run need a redesign.
Open Alerts
A scheduled job runs every five minutes to check for Pipelines that are in Queued state. If it detects any Pipeline above the 75% of TTL threshold at that instant, then it generates an Open Alert. However, if an Open Alert already exists for that Snaplex, then a new Alert is not generated. The previous Open Alert remains in the same state.
After an Open Alert has been generated, the next scan by the scheduled job repeats the same check for Pipelines that have been queued for more than 75% of their respective TTLs. If there are no Pipelines above the threshold for that Snaplex, the Alert is resolved and its state changed to Closed.