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

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

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

You can filter connection logs by the following parameters:

The supported filters are:

-`resource_type` - The type of the resource. It can be a workspace, template,

user, etc. You can

[find here](https://pkg.go.dev/github.com/coder/coder/v2/codersdk#ResourceType)

all the resource types that are supported.

-`resource_type` - The type of the resource, such as a workspace, template,

or user. For more resource types, refer to the

[CoderSDK package documentation](https://pkg.go.dev/github.com/coder/coder/v2/codersdk#ResourceType).

-`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

all the actions that are supported.

-`action`- The action applied to a resource, such as`create` or`delete`.

[CoderSDK package documentation](https://pkg.go.dev/github.com/coder/coder/v2/codersdk#AuditAction).

-`username` - The username of the user who triggered the action. You can also

use`me` as a convenient alias for the logged-in user.

-`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`.

-`build_reason` - To be used with`resource_type:workspace_build`, the

[initiator](https://pkg.go.dev/github.com/coder/coder/v2/codersdk#BuildReason)

behind the build start or stop.

-`build_reason` - The reason for the workspace build, if`resource_type` is

`workspace_build`.

Refer to the

[CoderSDK package documentation](https://pkg.go.dev/github.com/coder/coder/v2/codersdk#BuildReason)

for a list of valid build reasons.

In addition to theuser interface, there are multiple ways to consume or query

In addition to theCoder dashboard, there are multiple ways to consume or query

audit trails.

You can retrieve audit logs via the Coder API.

[endpoint documentation](../../reference/api/audit.md#get-audit-logs).

for details.

Audit trails are also dispatched as service logs and can be captured and

categorized using any log management tool such as[Splunk](https://splunk.com).

This feature is only available with a premium license.

[Learn more](../licensing/index.md)

This feature is only available with a[Premium license](../licensing/index.md).