AI-Analyze Log Entry
Run an AI analysis on a single log entry — the platform feeds the request, response, latency breakdown, hit policies, and headers to the AI gateway and returns a one-paragraph diagnosis. Useful for "why did this 500 happen?" workflows where you want a starting hypothesis before digging into the upstream logs.
Plan-gated: requires the traffic_inspector entitlement. Each call counts toward your AI usage budget. Returns 501 Not Implemented when the AI gateway is not configured on the deployment.
Path parameters
uuid from /traffic/logs.Deprecated: the legacy integer id is still accepted in the path until the sunset, answered with Deprecation and Sunset headers. Use the uuid.
Request body
general, security, performance, or debugging. Defaults to a general explanation when omitted (empty body or {}).Response (200 OK)
When the model answers with JSON instead, that object is returned as-is; its fields depend on analysis_type. The result is cached on the log, so a repeat call for the same analysis_type returns the cached analysis.
Errors
integer_id_unsupported).traffic_inspector entitlement.