Agentic Data Plane

Review the Audit Log

Use the audit log to find out who performed an action, on which resource, from where, and whether Redpanda Agentic Data Plane allowed it. The log records authorization decisions for management actions, such as configuration changes. It also covers the calls agents make to Model Context Protocol (MCP) tools and large language model (LLM) providers. Read it in Agentic Data Plane or from the command line.

After reading this page, you will be able to:

  • Filter authorization events with the search bar, the Fields panel, and the time range

  • Inspect the actor, operation, resource, source, and policy behind an authorization decision

  • Choose the audit log or a transcript for an investigation

The audit log appears for every Agentic Data Plane environment. Two independent conditions govern what you see. Your account needs the permission listed in the Prerequisites section, and the deployment needs audit recording enabled.

Because they are independent, a deployment can show the page with no recorded events. If the table is empty for a period you know had activity, see Troubleshoot the audit log.

Prerequisites

Your account needs the dataplane_adp_auditlog_list permission to open the audit log and view event details. Without the Admin role, you can get it from a built-in template, such as Read only. An access policy naming Action::"AuditLog.list" grants it too. See Audit log permissions.

Audit events can include user identities, resource names, network information, configuration changes, and captured request or response data. Grant audit log access only to people who need it, and review events before sharing them.

Open the audit log

  1. Open Audit log under Observability in the sidebar.

  2. Review the most recent events. The default time range is Last 24 hours, and the newest event is first.

  3. Click a row to expand it, then click Open event details.

By default, the table shows these columns:

Column Description

Time

When the decision occurred, as an RFC 3339 timestamp in UTC.

Actor

The identity that made the call. When an agent made the call, the cell shows the agent’s name and the identity accountable for it, such as the user it acted for. The Actor type field in the Fields panel classifies the actor as User, Service account, or Agent. It reads Unknown when an older event or a configuration change carries no actor type and names no agent.

Subsystem

The part of Agentic Data Plane that handled the action, such as MCP Gateway, LLM proxy, A2A proxy, Agents, Access control, Budgets, or Spending. An event from a service that doesn’t declare a subsystem shows Management API (legacy). Budget changes recorded before budgets had their own subsystem show Spending, so include both values when you search a budget’s history.

Action

The operation the caller invoked, such as tools/call for an MCP tool call or the request path of an LLM call.

Resource name

The name of the affected resource. When one call decided on more than one resource, the cell shows a count, such as Multiple resources (3). To see each resource and its decision, open the event and click View individual decisions. See Review one call’s individual decisions.

Outcome

Whether the decision allowed the action, masked part of its content, or denied it. A call that decided on more than one resource and allowed only some of them shows Partial. When an access policy allows a call but a guardrail or data policy then stops it, the outcome shows Denied. When one of them masks content, the outcome shows Masked. For a call that decided on a single resource, hover over the outcome to see the policy that decided it. A Partial call’s tooltip reports how many of its resources the call allowed. The policy behind each one is on that resource’s individual decision.

The log records agent calls to MCP tools and LLM providers even when an access policy denied them. The log also records every agent-to-agent (A2A) request that invokes an agent through the gateway. When an agent’s call bypasses policy evaluation, the event’s status detail reads allowed by internal-caller exemption; no policy evaluated.

The audit log records an MCP session’s setup and keep-alive calls only when they fail or a policy refuses them. These include initialize, tools/list, ping, and notification messages. As a result, the log shows the tool calls a session makes rather than every message it exchanges.

Choose columns

Use the Fields panel to show, hide, reorder, and resize columns, or to reset them to the defaults. The browser remembers your choice, but it isn’t part of the page URL, so a link you share shows the recipient’s columns, not yours.

Beyond the default columns, the panel offers fields such as Actor type, Groups, Agent, Invoked by, Parent, Policy, Status detail, and Source IP. Parent and Parent type name the MCP server behind a tool call or the agent behind a credential. Groups holds the actor’s recorded group memberships (see Groups on an event).

Activity and Event class come from the event’s Open Cybersecurity Schema Framework (OCSF) classification. Activity is Create, Read, Update, Delete, or Other, and an invocation such as a tool call reads Other. Event class is API Activity for an authorization decision or Entity Management for a configuration change.

Groups on an event

The Groups field records the groups the actor belonged to when Agentic Data Plane authorized the call. Show it as a column from the Fields panel, or read it on an event in the expanded row and the detail pane. Use it to answer questions about a team rather than an individual, such as which groups reached a resource over the last day.

Groups records the identity the call ran as, not the identity that started it. When a service account acts on behalf of a user, the field holds the user’s memberships. It stays empty when that user has none, rather than falling back to the service account’s own groups. The Actor and Invoked by fields report the two identities themselves.

Read an empty Groups field as no memberships recorded, not as an actor with no groups. Events from before Agentic Data Plane began recording memberships carry none. When a membership list is incomplete or too long to record in full, the event’s Status detail says so.

To filter on a group, type actor_groups=<group-name> in the search bar to include matching events, or actor_groups!=<group-name> to exclude them. Two details differ from other fields:

  • The Fields panel doesn’t list common values for Groups, so type the group name in full.

  • Group names are exact identifiers, and Agentic Data Plane preserves any spaces in them, so enter the name exactly as your directory spells it.

A filter matches the memberships recorded on each event. It doesn’t re-evaluate the actor’s current memberships, so a filter over a past time range reports the groups as they stood then.

Filter events

The search bar, the Fields panel, and the time range work together. Every filter is part of the page URL, so a narrowed view is shareable.

As you type in the search bar, it suggests fields and their most common values. Each filter you enter becomes a chip in the bar:

  • Type a word or phrase and press Enter to match it against the event message. Matching is case-insensitive and applies to the whole history in the time range, not only the rows on screen. The audit log keeps one phrase at a time, so a second phrase replaces the first.

  • Type <field>=<value> to show only events where the field has that value, for example, subsystem=mcp-gateway, actor_type=Agent, or outcome=denied.

  • Type <field>!=<value> to exclude events with that value. An exclusion chip shows the field and value joined by a not-equal sign.

  • Type sort=<field> to reorder the table from the bar, or sort=<field> desc for descending order.

In these filters, <field> is the field’s key, and <value> is a value the field takes, such as one listed in the Fields panel. Some keys differ from the column label, such as operation for Action, deciding_policy for Policy, and operation_status for Status. The outcome key takes allowed, masked, partial, or denied.

To remove one chip, close it in the bar. Clear all removes every chip.

Chips on different fields narrow the match, so an event must match all of them. Chips on the same field widen the match. With outcome=denied and outcome=partial, an event matches if it has either value.

Browse values in the Fields panel

To browse instead of typing, expand a field in the Fields panel. It lists the field’s most common values for the current time range and filters, with each value’s call count and share of calls. A value with denied calls also shows the denied count. To filter from the list:

  • Click a value to filter to it. Click it again to remove the filter.

  • Use a value’s exclude action to hide its events instead.

The list shows only the most common values. To reach one it leaves out, add another filter or type the value in full in the search bar. Activity, Event class, Status, All policies, and Groups have no value list and take a typed value.

Set the time range

Click the range control to choose a preset, from Last 15 minutes to Last 14 days. For a longer or past window, select Custom range, set the start and end times, and click Apply. Times are in UTC by default, and you can switch the picker to your local time zone.

The timeline shows event volume across the range, with the total count and the denied percentage, which counts partial calls as denied. Click a bar or drag across the timeline to zoom in, and click Zoom out to return.

For example, to investigate recent MCP authorization failures, type outcome=denied and subsystem=mcp-gateway in the search bar and choose Last hour.

Sort events

Click a column header to sort by that column. Click it again to reverse the order, and a third time to return to the default. The table sorts by Time by default, most recent first. You can sort every field except All policies and Groups, which each hold more than one value per event. Outcome orders allowed events first, then masked, partial, and denied events, so a descending sort brings denied events to the top. The order is part of the page URL.

Inspect an event

Click a row to expand it. The expanded row repeats the selected columns for that event. Each filterable value offers filter and exclude actions, so you can narrow the table to that actor or resource in one click. Click Open event details to read the event.

The Event section identifies who made the call and for whom, what they did, to which resource, and from where. It also shows the event’s status detail and correlation ID. An agent, MCP server, LLM provider, or access policy in the event links to its page. An MCP tool links to its server’s page. A role binding has no page to link to. The Groups row reads No groups recorded when the event carries none.

For a call that decided on more than one resource, the pane shows only the Event section and a View individual decisions link. It leaves out Status detail. The Policies, Configuration change, Request, and Response sections described next belong to each individual decision. See Review one call’s individual decisions.

The Policies section lists the policies that took part in the decision, in the order they ran:

  • Access: The access policy or role binding, and whether it returned Permit or Deny. An access policy links to its edit page.

  • Guardrail: The guardrail on an LLM call, and whether it returned Blocked or Masked. The guardrail links to its page.

  • Data policy: The data policy on the MCP server behind a tool call, and whether it returned Blocked, Masked, or Passed. The data policy links to the Data Policies tab of its MCP server.

A guardrail appears here only when AI Gateway evaluated it itself. The audit log doesn’t attribute a guardrail that Bedrock enforces as part of the model call. See Review blocked requests.

When a guardrail or data policy took part, a note states the combined result. For example, the access policy allowed the call, but the data policy stopped it.

Depending on the action, the pane also shows:

  • A Configuration change section with the versions before and after. For a deleted budget, it can show the budget as it was before the deletion, so the event still records the scope and limit that the deletion removed.

  • A Request section with the captured request data

  • A Response section with the status, code, error, and captured response data

The page URL carries the open event, so a link you share opens the audit log on that event. After you follow a link from the pane, use the back button on that page to return to the same place in the audit log.

Agentic Data Plane might redact, truncate, or leave out captured values. A redacted value reads [REDACTED], and Agentic Data Plane cuts a captured request or response body at 16 KiB. An empty field does not mean that no activity occurred. Use the event’s outcome and policy as the primary record of the authorization decision.

Review one call’s individual decisions

A call that decided on more than one resource records one decision per resource. Those decisions open in the table rather than in the pane.

  1. Click the call, then click Open event details.

  2. Click View individual decisions.

The table then lists only that call’s decisions, denied first, under a bar that names the call and carries Clear call filter. While the call filter is on:

  • The table covers the call’s whole recorded history rather than the selected time range.

  • Sorting is off, because the decisions already come denied first.

  • The Fields panel counts values by call rather than by decision, so type <field>=<value> in the search bar to narrow the decisions.

  • An outcome=partial filter describes a call rather than one decision, so filter by allowed, denied, or masked instead.

Click a decision to read it in the pane. Hover over its outcome to see the policy that decided that resource. Click Clear call filter to return to the events you came from, with the same time range, rows, and open event.

Read the audit log from the CLI

The same events are available from the command line with rpk ai auditlog. Use it for scripted reviews and to pull a window of events into a file. Reading the audit log is itself an audited action, so your own reads appear in later listings. To hide them, add --operation '!ListAuditLogEntries'.

The list and get commands need the same dataplane_adp_auditlog_list permission as the UI. If rpk ai auditlog isn’t recognized, update the plugin with rpk ai upgrade.

To search the log, use list. One row is one API call. A call that decided on more than one resource is a single grouped row, and its resource count reports how many:

rpk ai auditlog list --since 1h --denied

The --denied flag is shorthand for any call that contains a refusal, fully and partly denied alike. Filtering on --outcome denied alone leaves out the partly denied calls.

The window defaults to the last 24 hours. Pass --since an RFC 3339 timestamp, a duration such as 15m, 24h, 7d, or 2w, or all for no lower bound. Pass --until to close the window. Scanning the whole archive with all can exceed the server’s query timeout, so use a bounded window.

Each remaining filter flag matches one field. Flags combine the same way the chips in the UI do. Several values on one flag widen the match, and different flags narrow it. Repeat a flag or separate its values with commas, and prefix a value with ! to exclude it:

rpk ai auditlog list --actor alice@example.com --subsystem '!llm-proxy' -o json

Quote a negated value, because ! starts history expansion in an interactive shell.

The flags that name a resource, a parent, a policy, or an operation status match a call when any one of its resources matches. They return the whole call rather than the single matching decision. To see one grouped call broken out into one row per resource, filter on its correlation ID:

rpk ai auditlog list --correlation-id <correlation-id> -o wide

The default table shows a lean set of columns. The wide, json, yaml, and markdown formats add the decision and delegation fields. The --fields flag selects exactly the fields you want and also sets the table’s columns. See Format command output.

To read one event with every field, use get with the event’s ID. That includes the captured request body and the before and after states of a configuration change, which list leaves out. YAML is the readable format for those longer values:

rpk ai auditlog get <event-id> -o yaml

The get command reads a single event rather than a grouped call, so run list --correlation-id <correlation-id> first to get the member events of a grouped call. Each member’s ID works with get.

A listing prints at most 50 entries by default. Pass --limit 0 to return everything. When entries remain beyond the limit, the command still exits 0 and writes the flags that continue the listing to standard error. They include a page token. When the window was relative, such as the 24-hour default or a duration, they also include the window’s resolved start and end. The next page then covers the same window instead of one that has moved on. Rerun with those flags and the same filters.

In a script, check the exit code. Exit code 0 means the command succeeded, including when nothing matched. Exit code 1 means any other failure. Exit code 3 means you are not authenticated or your account lacks dataplane_adp_auditlog_list. See Check exit codes in scripts.

Audit log compared to transcripts

Use the audit log for access and accountability questions:

  • Who attempted an action?

  • Which resource and subsystem did it touch?

  • Was the action allowed or denied?

  • Which policy made the decision?

  • Did a guardrail or data policy stop or mask the call?

Use transcripts for execution questions about an agent conversation, including model turns, tool calls, errors, timing, and token usage. An investigation might need both views. Start with the audit log to find an authorization decision, then inspect the related agent activity for execution details.

Troubleshoot the audit log

Issue What to do

Audit log is missing from the sidebar

Either you haven’t selected an Agentic Data Plane environment yet, or your account doesn’t have dataplane_adp_auditlog_list. Select an environment first. If the entry still doesn’t appear, ask an administrator to grant the permission. They can grant it through the Admin role, a built-in template such as Read only, or an access policy naming Action::"AuditLog.list".

You opened the audit log by URL and the page reports that it is not available

The page hides the sidebar entry and the route for the same missing permission. Ask an administrator to grant dataplane_adp_auditlog_list.

No events match

Remove the chips with Clear all, then widen the time range. The default view includes only the last 24 hours. If the table stays empty, the deployment might not have audit recording enabled yet. Agentic Data Plane gates page access and recording independently.

The page dropped a filter from a shared link

The page names the filter it dropped and the reason, such as a field that does not exist. Retype the filter in the search bar and pick the field from the suggestion list.

The Fields panel is not visible

In a narrow window, or when the detail pane is open on a mid-sized window, the panel collapses to a strip. Expand the panel from the strip.

A call shows Denied although the caller has access

Open the event and read the Policies section. Check whether the Access row reads Permit while the Guardrail row or the Data policy row reads Blocked. If so, the access policy allowed the call, and the check that ran after it stopped the call. Follow the link in that row to review the guardrail or the server’s data policies.

An event has no request, response, or configuration details

Not every event includes these fields. Use the event’s actor, action, resource, outcome, and time to continue the investigation.