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

​
Steps

  1. Start from the project that owns the work.
  2. Check logs for runtime output and operational messages.
  3. Check traces for request and execution paths.
  4. Check errors for failure type, message, and affected resource.
  5. Open run events when the issue belongs to an agent, job, or workflow.

​
Try it with REST

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"

​
API surfaces

SurfaceStart here
RESTLogs, Traces, Errors
GraphQLProject Logs, Project Traces
MCPSearch Project Logs, Search Project Traces

​
Verify

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

​
Choose a signal

SignalUse it for
LogsRuntime output and operational messages.
TracesRequest and execution paths across services.
ErrorsFailure type, message, and affected resource.
Run eventsOrdered execution history.
UsageResource consumption over time.

​
Next

GoalPage
Understand observability signalsObservability
Inspect execution historyRuns and events
Check usage and limitsCheck usage and limits

​
API reference

APIUse
RESTLogs, traces, errors, and runs.
GraphQLRuntime, log, trace, and error views.
MCPLog, trace, error, and run tools.