Event Type | Event Type Specific Parameters | Suggested Action for Recipients |
|---|
ACL | ACL add | Projects to notify: Select the Projects from the drop-down list to which this event applies. | Consult your Org admin if you have received this notification. Your access to a project might have changed. |
ACL remove |
API | Concurrent API usage | Threshold: Enter the limit as a percentage of usage allowed.
Recipients: Enter the email addresses of the intended recipients of the event. | Monitor your usage of APIs. Consult your Org admin if the percentage needs to be increased. |
Daily API usage |
Apim | Pending subscription | API/Proxy to notify: Select a published API
Email: Enter the email addresses of the recipients
Slack > Channel(s): List the Slack channels Slack > Direct Messag(es): List the Slack recipients. | API admin: Select to receive notifications when the APIs you publish on your Org’s Developer Portal have pending subscriptions. When API consumers on the Developer Portal request access to your API for use in their application, you receive the notification at the email or Slack Channe/recipient entered in the notification. |
Asset | Asset create | Projects to notify: Select the Projects from the drop-down list to which this event applies. | Consult your Org admin if your assets have been deleted moved, renamed, or if ownership has changed without your knowledge. |
Asset delete |
Asset move |
Asset owner change |
Asset rename |
Asset update |
Dist | Dist change | N/A | None: Informational |
Dist override |
Dist subscribe |
Group | Group create | N/A
| None: Informational
|
Group create provisioned |
Group delete |
Group update |
Session | Session start | N/A | None: Informational The notification indicates which user (by user email) started or ended a session and the following details about the user: |
Session end |
Sso session start |
Snaplex | Auto scale config update | N/A | Choose another Snaplex from which to run your Pipelines. |
Snaplex congestion |
Snaplex node add |
Snaplex node connection rejected |
Snaplex node crash |
Snaplex node enter maintenance mode |
Snaplex node leave maintenance mode |
Snaplex node restart |
Snaplex version update |
Snaplex Node | Snaplex node cpu load avg
| CPU utilization: Enter the target threshold for CPU utilization as an integer value. When the CPU usage exceeds this value, a notification is sent. The threshold value setting depends on the server host for the node and might require adjustment. The following example values are based on internal testing. Snaplex: Select the target Snaplex from the drop-down list. Email Addresses: Specify the email address of the intended recipients of the event. | Run your Pipelines on another Snaplex until more resources are allocated to the Snaplex or activity by other users decreases. |
Snaplex node disk usage | Threshold: Enter this value as the remaining amount of disk space. Make sure you specify the capacity size in GB, MB, KB. When the free space available falls below this value, the alert notification is sent.
Snaplex: Select the target Snaplex from the drop-down list.
Type of the disk space: Enter the filesystem type (NFS, CIFS, TMP).
Name of the disk space: User given name for the space, if any. UsageIf 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.
| Run your Pipelines on another Snaplex until more resources are allocated to the Snaplex or activity by other users decreases. |
Snaplex node memory usage | Threshold: Enter the threshold as a percentage of the amount of memory the user is limited to. Snaplex: Select the target Snaplex from the drop-down list. | Run your Pipelines on another Snaplex until more resources are allocated to the Snaplex or activity by other users decreases. |
Task | Task execution duration - percentage of normal | Threshold: Enter the threshold as a percentage based on the 30-day historical executions. | Investigate the following potential issues that could prevent the Task execution from completion:
The Snaplex is running low on resources, such as CPU, memory, or network bandwidth.
The endpoint that the Pipeline is connecting to is congested or not available.
The Pipeline is processing an unusually large number of documents or large-sized documents.
|
Task execution duration - time limit | Threshold: Enter the threshold in minutes.
Apply to: Select one of the following options. |
User | Password change | N/A | Consult your Org admin about your sign-on access. |
Password reset |
Password reset link |
User authentication failure |
User create |
User delete |
User lockout |
User unlock |
User update |
