System Events
Get Veza platform events, including notifications and integration logs.
Operation | Syntax |
---|---|
GET /api/preview/events | |
GET /api/preview/events/export |
Event objects represent Veza platform activity, including integration parsing, notification activity, and user logins. You can list events that match a filter (such as a category or severity), or export a continuous list for integration with an external monitoring system,
For logging Veza API activity, see Audit Log API.
List events
Returns an array of Veza platform events
. If a filter
is specified, the endpoint only returns events matching the SCIM filter expression. This can get events with a matching category or severity, for example:
GET /api/preview/events?page_size=10&filter=category+eq+"INTEGRATIONS"+and+timestamp+ge+"2023-04-17T22:29:22.440Z"
Export events
Returns a paginated list of platform events, intended for exporting a continuous log into an external system.
The export endpoint can return the error code ResourceExhaused
. When encountered, wait for one minute before retrying the request.
To capture events when they become available without skipping any entries, first make call with a persisted_at GE "TIMESTAMP"
filter:
Use the next_page_token
in the response to continuously call the next page:
Example response:
Veza event schema
Field | Description | Example Value |
---|---|---|
| Unique identifier for the event | d95ccc9c-9051-4ef7-9147-124a16409baa |
| Timestamp when the event occurred | 2023-05-18T14:23:35.151842912Z |
| Category of the event |
|
| Severity level of the event |
|
| Title of the event | Tagging request failed |
| Descriptive message for the event | Tagging request failed for node test1 |
| Provider data source unique identifier | e88f5d72-6f79-41d1-99e3-8777e1727311 |
| Type of entity related to the event |
|
| Unique identifier for the entity | e88f5d72-6f79-41d1-99e3-8777e1727311 |
| Name of entity related to the event | SYSTEM_resource_managers:500008 |
| Error details | See "error object structure" |
| Type or category of the event | Tagging request failed |
Error object structure:
message
: Error messagemetadata
: Additional metadata for the failed request.reason
: Reason for the errorresolution
: Details to prevent the errorrequest_id
: Unique identifier for the failed request
Event types
Veza events will have one of the following event types:
OUTDATED_AWS_EXTRACTION_POLICY
DATASOURCE_PARSED
DATASOURCE_EXTRACTED
DATASOURCE_REGISTERED
DATASOURCE_REMOVED
DISCOVERY_FAILED
DISCOVERY_SUCCESS
OAA_PUSH
RULE_NOTIFICATION_FAILED
TAGGING_REQUEST_FAILED
EMAIL_NOTIFICATION
USER_LOGIN
USER_LOGOUT
USER_CREATED
USER_DELETED
USER_EMAIL_UPDATED
USER_ROLES_UPDATED
USER_ENABLED
USER_DISABLED
USER_PASSWORD_FORCED_RESET
API_KEY_CREATED
API_KEY_UPDATED
API_KEY_DELETED
API_KEY_REVOKED
API_KEY_REINSTATED
Event retention
Veza retains system events for one month. When requesting events outside that range, the response will have a field error message indicating the oldest valid timestamp:
Pagination
Responses will contain a next_page_token
when more events are available. Include this page_token
in the request query to get the next batch of results.
If no page size is specified, the default is 1,000. The maximum page size is currently 10,000 records.
Last updated