Subscriptions
A Subscription connects event routing logic to one or more Targets within Event Channels. A subscription defines which events match, and the targets define where those events are delivered.
Event Types
Subscriptions can match a specific set of event types or all event types. When no event types are selected, the subscription matches every event that passes through the channel. When specific types are selected, only those types are delivered.
Available event types:
| Category | Event Type | Description |
|---|---|---|
| User Security | User Lockout | A user account is locked after too many failed login attempts |
| Client Logs | Client Log: Success, Failure, Partial Failure, Skipped | A Files Connect or CLI client app uploads activity logs to your site |
| SSO | LDAP Sync: Success, Failure, Partial Failure, Skipped | An LDAP directory sync runs to provision users or update group membership |
| SSO | LDAP Login: Success, Failure, Partial Failure, Skipped | A user attempts to authenticate using LDAP credentials |
| SSO | SAML Login: Success, Failure, Partial Failure, Skipped | A user attempts to authenticate via SAML SSO |
| Pending Work | Pending Work: Success, Failure, Partial Failure, Skipped | A background GPG encryption or decryption job processes a file |
| SIEM | SIEM: Success, Failure, Partial Failure, Skipped | An event is delivered to your configured SIEM integration |
| Sync | Sync: Success, Failure, Partial Failure, Skipped | A file sync runs between your site and a remote server |
| Automation | Automation: Success, Failure, Partial Failure, Skipped, Failure Will Retry, Partial Failure Will Retry | An Automation rule runs on files or folders |
| Expectations | Expectation Evaluation: Success, Late, Missing, Invalid | An Expectation is evaluated: a monitored file arrived on time, arrived late, did not arrive, or arrived with an invalid condition |
| Expectations | Expectation Incident: Open, Acknowledged, Snoozed, Resolved | An Expectation incident changes state |
For Automation runs, the Failure Will Retry and Partial Failure Will Retry types fire when a run fails but will be retried automatically. The broad admin email alert for Automation failures only covers terminal failures after all retries are exhausted. Subscribe to these types explicitly if you want alerts for retryable failures.
For Expectation evaluations, the broad admin email alert covers Missing and Invalid only. Late evaluations are available only through an explicit subscription.
Filters
A subscription can include an optional filter to narrow which events are delivered beyond event type alone. Leave the filter blank to match all events of the selected types. When a filter is set, only events whose fields match the filter conditions are delivered.
Common filter fields include Severity, Status, Sync ID, Sync Name, Automation ID, and Expectation ID. A Custom Field option is also available for filtering on any other field in the event payload.
Targets
A subscription routes matched events to one or more targets. The same target can be used across multiple subscriptions.