Opsera provides audit logging for key operations in the platform. These logs can be accessed via the Opsera API.
Table of Contents |
---|
...
Audit Scope
The following actions are logged:
ScopeEvents | Event / Action | ID (type) |
---|---|---|
User Authentication | All login events for a given user. |
|
Pipeline Actions |
|
|
Access Token Usage | All uses of a given token are logged | n/a |
...
The following API’s are available for consuming the audit logs. All Opsera API’s require a valid Access Token.
API Server:
URL | METHOD | DESCRIPTION | DATA | RESPONSE | ||
---|---|---|---|---|---|---|
| GET | Gets the User Activity Logs for the system. This is a route limited to Site Admins and Power users and requires a token of either API scope or Security Logs scope. If no date parameter is passed, the last 7 days of logs will be returned (up to a max of 1000 records) | Optional Query Parameters:
|
| ||
| GET | Gets the Personal Access Tokens' Activity Logs. This is a route limited to Site Admins and Power users and requires a token of either API scope or Security Logs scope. If no date parameter is passed, the last 7 days will be returned.(up to a max of 1000 records) | Optional Query Parameters:
|
|
Data Model
Two data models exist for the Audit Logs: Actions and Tokens. Details on what the fields mean are listed below:
...
Code Block |
---|
{
"user_id": Opsera User ID,
"user_email": Email Address associated with Opsera Account,
"type": Maps to the area of Opsera the record is from (see above table),
"action": Action being logged (see above table),
"target_id": Opsera ID of object aciton is taken on, maps to type,
"createdAt": Date action occured,
} |
...
Code Block |
---|
{
"token_id": Opsera ID of token used,
"scope": Scope of token,
"target": Relative URL target of API call,
"user_id": Opsera User ID,
"createdAt": Date action occured,
} |