AI Request Logs
View, search, and export logs for every AI request processed through the Cencori gateway.
AI request logs capture every AI request processed through the Cencori gateway. Each log entry includes the full request and response details — model, tokens, cost, latency, provider, status, and security metadata.
This page covers AI request/response logs (what your users sent and received). For organization-level change tracking (who modified settings, keys, or rules), see Audit Logs.
What Gets Logged
Request Information
- Prompt text and messages
- Model and parameters (temperature, max_tokens)
- API key used
- User/session identifier
- Timestamp (millisecond precision)
- IP address and geolocation
Response Information
- AI-generated content
- Token usage (input/output/total)
- Cost calculation (provider cost and Cencori charge)
- Latency metrics
- Provider used (including failover details)
- Status code (success/error)
Blocked requests
- When PII protection is on and blocks a request, it is logged with the Filtered status.
With PII protection off (default), requests still log with model, tokens, cost, and latency.
Viewing Logs in the Dashboard
- Open your project in the dashboard
- Go to AI Gateway → Logs
- Narrow the results with the filters:
- Status (Success, Fallback Used, Filtered, Blocked, Error, Rate Limited)
- Model
- Time range
- API key
- Search
- Click any log entry to view full details
Searching Logs
Search through logs using full-text search to:
- Find specific keywords in prompts
- Identify all requests from a specific user
- Locate expensive queries (high token usage)
- Debug failed requests by error message
Exporting Logs
Click Export on the Logs page. The export uses the filters you have applied.
- CSV — request metadata (time, status, model, tokens, cost, latency, errors), without prompt or response text. Up to 10,000 rows.
- JSON — the same fields plus the full request and response payloads. Up to 1,000 rows.
How Far Back You Can View
Your plan sets how far back logs can be viewed and exported:
If you pick a longer range than your plan allows, Logs shows the longest range your plan includes.
Best Practices
- Export logs monthly for long-term archival
- Use search to identify expensive or slow queries
- Review error logs weekly to catch issues early
- Set up alerts for unusual patterns (cost spikes, error rate increases)
- Document your log retention policy for compliance
- Redact sensitive data before sharing logs with third parties
Related
- Audit Logs — organization-level change tracking (who modified what)
- Usage and analytics — charts on the AI Gateway overview
- PII Protection — opt-in blocking of requests that contain personal data