Skip to content

Audit Activity

The Audit Activity page is the primary view in the kAudit portal. It shows every SQL Server audit event captured by the agent — DML statements, logins, administrative actions, schema changes — in a searchable, filterable grid.

What you'll see

A summary bar at the top shows totals for the current query window:

IndicatorMeaning
Total EventsAll audit events in the selected time range
SuccessfulEvents where the SQL action completed successfully
FailedEvents where the action was denied or caused an error
DatabasesNumber of distinct databases with activity
PrincipalsNumber of distinct SQL logins with activity
LatestTimestamp of the most recent event

Filtering activity

Use the filter form to narrow the event stream:

FilterDescription
Date rangeLimit results to a specific time window
DatabaseFilter to a single database
PrincipalFilter by SQL login name
Action typee.g., SELECT, INSERT, DELETE, DDL, LOGIN
Keyword searchSearch across object names and statements
Tenant(If you have multiple tenants) switch context

Click Apply to run the query. Click Refresh to re-run the current query against the latest data.

Reading the event grid

Each row is one audit event. The columns you'll see most often:

ColumnDescription
TimestampWhen the event occurred (converted to your local time)
ActionThe SQL action type (SL = SELECT, IN = INSERT, etc.)
Status✅ Success or ❌ Failure
PrincipalThe SQL Server login that performed the action
ObjectThe database object accessed or modified
DatabaseThe database the event occurred on
ApplicationThe client application name (if captured)
HostThe client host machine name (if captured)

Click any row to expand it and see the full event detail, including the full statement text if captured.

Understanding action codes

SQL Server uses short codes for audit action types. Common ones:

CodeAction
SLSELECT
ININSERT
UPUPDATE
DLDELETE
EXEXECUTE
CRCREATE
ALALTER
DRDROP
LOLOGIN
LFLOGIN FAILED

Failed events

Events with a Failed status represent SQL Server access denials or errors. A high volume of failed logins from the same principal or host can indicate a misconfiguration or unauthorized access attempt.

Data latency

Audit events typically appear in the portal within 30–60 seconds of occurring on the SQL Server. This is controlled by the agent's polling interval. If you aren't seeing recent events:

  1. Check the agent heartbeat card in the bottom-left of the portal — it shows the last time the agent connected
  2. Confirm the agent service is running on the SQL Server host
  3. Confirm SQL Server Audit is enabled and writing .sqlaudit files

SQL Audit Monitoring, made simple.