Monitor coding agent activity in Unity Gateway unified tracing

Use cases

Imagine that you need to audit the usage and performance of coding agents used by developers to understand costs and efficiency. You can:

• Record the use of tools and skills coupled with model requests.
• Store gateway traces and client-side traces in the same Unity Catalog table.
• Investigate coding sessions, commits, and lines of code added or removed.

How to use

In the configuration file of the supported coding agent, add the tracing setting inside the existing config object:

{
  "tracing": {
    "enabled": true
  }
}

What happens in this code:

1. You enable trace collection directly within the agent's configuration file.
2. The developer launches the agent using the Unity Gateway CLI through commands such as ug claude or ug codex.
3. The CLI automatically applies the tracing settings, export endpoint, and authentication.

Limitations and requirements

The unified trace table is in Beta. An account admin must enable the Enhanced Unity Gateway preview from the account console. A metastore admin must create the trace table once in Unity Catalog.

Using it in a pipeline

You can use the data collected in the unified trace table to monitor AI assistant adoption, audit model costs, and analyze agent behavior within development and governance workflows.