Viewing access log

Viewing access log

Access logs help you troubleshoot call failures, track request latency, and audit model access behavior. By default, the Neutree stores access logs from the last 30 days in victorialogs, with a storage capacity of 40 GiB. If log data fills this storage space within 30 days, new logs cannot be written.

Note

Requests for querying the list of available models are not written to access logs. For example, the OpenAI-compatible API GET /v1/models and the Anthropic-compatible API GET /anthropic/v1/models.

Prerequisites

• Access log storage has been configured and enabled for the control plane.
• The current user has the access log viewing permission for the corresponding workspace:
  • To view endpoint access logs, the user must have the Endpoint:Access Log Read permission.
  • To view external endpoint access logs, the user must have the External endpoint:Access Log Read permission.

Procedure

1. Log in to the Neutree management interface. In the left navigation pane, click Access Log.

2. Set filter conditions as needed. You can filter access logs by time, endpoint name, endpoint type, HTTP status code, model name, API key, and finish reason. The request count bar chart at the top of the page updates based on the selected time range. The table below displays access logs within the filter range and shows the following information: Time, Endpoint, App, Model, Status, API key, Tokens, Tok/s, Duration, and Finish. Hover over the status code in the Status column to view the description of the HTTP status code. When All workspaces is selected, the list also displays the Workspace column.

   Common values of Finish are as follows:

   Value	Description
   stop	The model normally ends generation, or encounters the stop sequence configured in the request.
   length	Generation stops after the generated content reaches the maximum number of tokens or the context length limit.
   tool_calls	The model stops the current response after returning a tool call request.
   content_filter	The generated content is truncated by the upstream content filtering policy.

3. In the access log list, click the target log to view request details. In addition to the information already displayed in the list, the details include Request model, Response model, Stream, Token prompt, and Token completion. For requests or responses that contain tool calls, tool results, images, or reasoning content, the details page displays detailed information about the corresponding Request body and Response body by content block.