Home
/
Administration
/
Audit Logs

Audit Logs

Enterprise

Audit Logs allows Auditors to monitor user operations in their deployment.

Tracked Events

We track the following resources:

Resource
AuditableGroup
FieldTracked
avatar_urltrue
quota_allowancetrue
memberstrue
idtrue
nametrue
organization_idfalse
Organization
FieldTracked
idtrue
nametrue
descriptiontrue
created_atfalse
updated_atfalse
OrganizationMember
FieldTracked
updated_atfalse
rolestrue
user_idtrue
organization_idtrue
created_atfalse
User
FieldTracked
deletedtrue
idtrue
usernametrue
rbac_rolestrue
login_typefalse
updated_atfalse
hashed_passwordtrue
statustrue
last_seen_atfalse
emailtrue
created_atfalse
avatar_urlfalse
Workspace
FieldTracked
idtrue
template_idtrue
deletedfalse
nametrue
organization_idfalse
owner_idtrue
autostart_scheduletrue
ttltrue
last_used_atfalse
created_atfalse
updated_atfalse
WorkspaceBuild
FieldTracked
created_atfalse
job_idfalse
idfalse
updated_atfalse
template_version_idtrue
initiator_idfalse
deadlinefalse
daily_costfalse
build_numberfalse
provisioner_statefalse
reasonfalse
workspace_idfalse
transitionfalse
GitSSHKey
FieldTracked
created_atfalse
updated_atfalse
private_keytrue
public_keytrue
user_idtrue
Template
FieldTracked
updated_atfalse
provisionertrue
idtrue
default_ttltrue
organization_idfalse
icontrue
min_autostart_intervaltrue
deletedfalse
display_nametrue
group_acltrue
nametrue
created_atfalse
created_bytrue
user_acltrue
is_privatetrue
active_version_idtrue
allow_user_cancel_workspace_jobstrue
descriptiontrue
TemplateVersion
FieldTracked
idtrue
template_idtrue
nametrue
created_atfalse
updated_atfalse
readmetrue
job_idfalse
created_bytrue
organization_idfalse

Filtering logs

In the Coder UI you can filter your audit logs using the pre-defined filter or by using the Coder's filter query like the examples below:

  • resource_type:workspace action:delete to find deleted workspaces
  • resource_type:template action:create to find created templates

The supported filters are:

  • resource_type - The type of the resource. It can be a workspace, template, user, etc. You can find here all the resource types that are supported.
  • resource_id - The ID of the resource.
  • resource_target - The name of the resource. Can be used instead of resource_id.
  • action- The action applied to a resource. You can find here all the actions that are supported.
  • username - The username of the user who triggered the action.
  • email - The email of the user who triggered the action.
  • date_from - The inclusive start date with format YYYY-MM-DD.
  • date_to - the inclusive end date with format YYYY-MM-DD.

Enabling this feature

This feature is only available with an enterprise license. Learn more

See an opportunity to improve our docs? Make an edit.