Inspect logs and traces

Find recent errors for a project, then use request, trace, or run IDs to follow the affected execution. Replace support-assistant with the project that owns the work. Use an API credential with access to its observability data.

1. Find error log entries

List error log entries with GET /projects/{project_reference}/logs:

list-log-entries.sh

curl "https://api.veryfront.com/projects/support-assistant/logs?level=error&limit=50" \
  -H "Authorization: Bearer $VERYFRONT_API_KEY"

The response has the log entries in data and the page cursors in page_info. This excerpt leaves out deprecated fields. See List log entries for the full shape.

log-entries.json

{
  "data": [
    {
      "timestamp": "2026-10-12T09:14:03.218Z",
      "level": "error",
      "message": "Upstream request failed",
      "service": "veryfront-server",
      "trace_id": "4bf92f3577b34da6a3ce929d0e0e4736",
      "run_id": "run_01JABCDEF"
    }
  ],
  "page_info": {
    "self": null,
    "first": null,
    "next": "eyJ0IjoiMjAyNi0xMC0xMlQwOToxNDowMy4yMThaIn0",
    "prev": null
  },
  "stats": {"bytes_processed": 18234, "lines_processed": 412, "query_time_ms": 37}
}

Pass page_info.next as cursor to read the next page, and keep the same filters:

list-more-log-entries.sh

NEXT_CURSOR="eyJ0IjoiMjAyNi0xMC0xMlQwOToxNDowMy4yMThaIn0" # page_info.next
curl "https://api.veryfront.com/projects/support-assistant/logs?level=error&limit=50&cursor=$NEXT_CURSOR" \
  -H "Authorization: Bearer $VERYFRONT_API_KEY"

A page can hold fewer than limit log entries, or none, and still have page_info.next. Stop when page_info.next is null. List traces with GET /projects/{project_reference}/traces:

query-traces.sh

curl "https://api.veryfront.com/projects/support-assistant/traces?limit=50" \
  -H "Authorization: Bearer $VERYFRONT_API_KEY"

Add start and end to limit the time window. If you have a run ID, add run_id to the trace query instead of searching unrelated activity.

Verify the result

Match the record’s project, timestamp, and identifiers to the failing execution. A nearby error is not necessarily the cause of the request you are investigating. Log entries describe individual messages. Traces connect timed operations. Run events record execution progress and output; they complement the trace.

Evaluate an agent: Check a change against repeatable evaluation cases.

Interface	Operations
REST	List log entries · Query traces · Read run events
GraphQL	Project logs · Project traces
MCP	List log entries · Query traces

Get started

APIs

REST API

GraphQL API

MCP API

Inspect logs and traces

1. Find error log entries

Verify the result

Next

​1. Find error log entries

​2. Find the related trace

​Verify the result

​Next

​Related

1. Find error log entries

2. Find the related trace

Verify the result

Next

Related