Skip to main content

Monitor IDE AI Usage

When IDE assistants route through the Verdictan gateway, use the public evidence path for application traffic. Preserve request IDs. Query runtime Events with verdictan events or GET /v1/events with the mandatory since. If a different team must have a durable artifact, create an export. If history capture is enabled, History adds captured session context. The capture mode and platform retention policy also control context availability.

Start with live event visibility​

Use verdictan events tail while developers reproduce the applicable IDE workflow.

# Recent IDE-related event activity
verdictan events tail --since 10m

# Follow new events as they arrive
verdictan events tail --since 10m --follow

# Show blocked decisions
verdictan events tail --since 10m --event-type decision --verdict blocked --json

# Show one gateway
verdictan events tail --since 30m --gateway-id gw_123 --json

If a different tool or script must use the event payload, use the JSON form.

Review a request​

Use the live tail for confirmation. Then use these customer review surfaces:

  • Use the matching verdictan events tail result or Events API response for the request outcome and cause code.
  • In that result, examine the config version and delivered policy details.
  • If capture is enabled, use History.
  • Use it for session metadata or content permitted by the capture mode and retention policy.
  • If chronology or evidence packaging is necessary, use Trail.
  • If the request created an escalation or approval item, use Inbox.

Do not rely on Notifications for ordinary IDE policy decisions, gateway health, configuration reloads, export completion, or budget thresholds. Notification producers apply to workflows such as escalation lifecycle, disposable-token lifecycle, conversation sharing, and managed broadcasts. See Notifications.

Export evidence for audits or handoff​

For small exports, use verdictan events export directly:

# Last 7 days as CSV
verdictan events export --since 7d --format csv > ide-events-7d.csv

# Last 24 hours as structured JSON
verdictan events export --since 24h --format json > ide-events-24h.json

For asynchronous exports or evidence handoffs, use export jobs:

verdictan export-jobs create --since 30d --format csv
verdictan export-jobs list --json
verdictan export-jobs download --job-id <job-id> > ide-audit.csv

Items to examine​

QuestionPublic surface
Is the gateway receiving IDE traffic?verdictan events tail
Which requests did a policy block or redact?Use verdictan events tail --verdict ... and the matching request IDs. Add History only for captured session context.
Is a durable artifact for a different team necessary?verdictan events export or verdictan export-jobs
Is cost or budget context necessary for follow-up?verdictan spend and Usage Costs and Budgets

Practical guidance​

  • Keep the live tail narrow with --since, --event-type, --verdict, and --gateway-id.
  • Export only the necessary window so reviewers do not receive oversized evidence bundles.
  • Pair each export with the request IDs, escalation IDs, or incident references that show its purpose.
  • Use verdictan events, the Events API, public exports, and capture-enabled History as the evidence sources for this workflow.

Next steps​