Debug

Use diagnostic traces when EVERTRUST Support needs a detailed local execution trace to investigate an issue.

Diagnostic traces

Set --trace-file or SERVICE_TRACE_FILE to write a trace file:

event-forwarder \
  --endpoint "https://service.example.com/api/v1/events/search" \
  --api-key "$SERVICE_API_KEY" \
  --state-file "/var/lib/event-forwarder/state.json" \
  --trace-file "./event-forwarder-trace.jsonl"

The generated file uses the OpenTelemetry Protocol JSON file serialization format: one trace export request per line with top-level resourceSpans. It includes spans for CLI execution, daemon polls, state loading and saving, page fetch attempts, HTTP requests, and event processing.

Attach this trace file to the related support ticket when requested. It gives EVERTRUST Support enough local execution detail to provide a more accurate answer and debug the issue from our side.

Each processed event span includes the raw event JSON in event.body, so handle this file like customer log data.