Auth logs & sessions

Every authentication attempt becomes an auth log entry: which agent, which method, the trust it reached, the page, and — when it failed — the exact reason. In the Agentronics console they power the Logs, Agents and Sessions views and your monthly active agent count.

What an entry contains

{
  "type": "auth.identity_presented",
  "outcome": "success",
  "agent": { "class": "crawler", "trust": "verified", "vendor": "OpenAI" },
  "metadata": {
    "protocol": "web-bot-auth",
    "subject": "https://chatgpt.com",
    "page": "/products"
  }
}

Sending server-side results

Turn each result into a log entry with toTraceEvent() and ship it with the dashboard exporter — see Stream auth events to the console:

import { agentronicsMiddleware } from '@agentronics/sdk/next'
import { toTraceEvent } from '@agentronics/sdk/server'
 
export default agentronicsMiddleware({
  onResult: ({ result, request }) => {
    const event = toTraceEvent(result, { siteId: 'shop', request })
    if (event) exporter.export([event])
  },
})

Plain human traffic produces no entry.

Browser-side results

The browser SDK emits the same auth.identity_presented events for in-page agents whenever authenticate(), presentIdentity() or detection changes the identity, so both halves land in one log.

Sessions

A session groups one agent's activity: its verified id plus the pages and methods it used. In the console you can see active sessions per agent and when each agent was last seen.

Retention

Raw log entries are kept for your plan's retention window — 7 days on Free, 30 on Pro, 90 on Business, custom on Enterprise. Daily roll-ups behind the charts are kept longer. On Business and above, logs can be exported for audit — see Data export.