Sorry, no results found for "".
If the Audit log functionality is enabled in a project, logged events can be queried using SQL-like language and fetched in full detail so that they can be exported or analyzed.
Must be exactly "audit_log_event".
The actual action performed
"items.publish"
The actor who performed the action
{ type: "user", id: "3845289", name: "mark@acme.com" }
The type of actor (can be account, user, sso_user or access_token)
"user"
The ID of the actor
"3845289"
An human representation of the actor (name/email/username depending on the type of actor)
"mark@acme.com"
The role of the actor at the time the action was performed
{ id: "455281", name: "Editor" }
The name of the role
"Editor"
The ID of the role
"455281"
The environment inside of which the action was performed
{ id: "main", primary: true }
The ID of the environment
"main"
Whether the environment was the primary one at the time the action was performed
The actual request being performed
{
id: "894f9f6c-a693-4f93-a3fb-452454b41313",
method: "PUT",
path: "/items/37823421/publish",
payload: {},
}
The full path of the request
"/items/37823421/publish"
The HTTP method of the request
"PUT"
The X-Request-ID header of the request
"894f9f6c-a693-4f93-a3fb-452454b41313"
The full HTTP body of the request
{}
The actual response being returned by DatoCMS
{ status: 200, payload: {} }
The HTTP status code of the response
"200"
The full HTTP body of the response
"PUT"
The date of the event
"2016-09-20T18:50:24.914Z"