Traces

Traces & service map

Send traces via OTLP/HTTP to /v1/traces. The edge extracts service-map edges (caller → callee) and span error rates. The Traces view renders the service map and a per-trace waterfall. Error spans are highlighted automatically.

Ingest

# Direct OTLP/HTTP
curl -X POST https://your-edge/v1/traces \
  -H "Authorization: Bearer $PB_KEY" \
  -H "Content-Type: application/x-protobuf" \
  --data-binary @traces.pb

Tracer SDKs

Use any OpenTelemetry SDK pointed at /v1/traces, or use one of our branded wrappers for one-line bootstrap:

@pulseboard/tracer — Node.js. NODE_OPTIONS=--require @pulseboard/tracer/register for zero-source-change attach.
pulseboard-tracer — Python. One-line from pulseboard_tracer import start; start().
Go & Java — vanilla OTel SDK with our OTEL_* env-var contract.

AWS Step Functions waterfall

Without instrumenting your state machines, PulseBoard turns Step Functions executions into spans:

EventBridge rule on aws.states source.
Kinesis Firehose DirectPut stream delivers to POST /api/aws/firehose.
Execution-status changes become root spans; task-status changes become child spans.
FAILED / TIMED_OUT / ABORTED emit exception span events.
Re-deliveries collapse to the same span via SHA-256-derived IDs.

Service map

Edges are extracted from each span's parentSpanId + service.name. Error rates per edge are computed from span status.code. Hover any edge to see request rate, error rate, latency p50/p95/p99.