Inspect logs and traces

Inspect logs and traces when runtime work fails, slows down, or needs audit context.

Steps

Search recent error logs: GET /projects/{project_reference}/logs?level=error&limit=50

Terminal

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

Search traces for a request or run: GET /projects/{project_reference}/traces?limit=50

Terminal

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

Surface	Start here
REST	Logs, Traces, Errors
GraphQL	Project Logs, Project Traces
MCP	Search Project Logs, Search Project Traces

Open the newest matching log or trace. Follow the related run, deployment, or request ID to the owning resource.

Signal	Use it for
Logs	Runtime output and operational messages.
Traces	Request and execution paths across services.
Errors	Failure type, message, and affected resource.
Run events	Ordered execution history.
Usage	Resource consumption over time.

Goal	Page
Understand observability signals	Observability
Inspect execution history	Runs and events
Check usage and limits	Check usage and limits

API	Use
REST	Logs, traces, errors, and runs.
GraphQL	Runtime, log, trace, and error views.
MCP	Log, trace, error, and run tools.