Labs Overview
Each lab focuses on a specific debugging workflow. The sidebar links route directly to detailed guides.
Capture lab
Section titled “Capture lab”Use disposable webhook endpoints to inspect incoming requests in realtime. LinkPeek captures headers, payload bodies, GeoIP lookups, and timeline metadata. Export entire sessions as NDJSON to replay in QA environments or share with vendors.
Key resources: Capture lab guide
Payload lab
Section titled “Payload lab”Upload artefacts once and generate multiple delivery variants: inline HTML, attachment mode, chained redirects, corrupt chunks, MIME switches, and more. Share generated URLs with clients, then monitor the dedicated payload activity tile to verify fetch behaviour.
Key resources: Payload lab guide
Retry lab
Section titled “Retry lab”Stress retry logic by hitting controlled failure scenarios. The lab exposes endpoints for slow responses, truncated bodies, checksum mismatches, and alternating success/failure patterns. Pair the visual dashboard with the /api/retrylab/stats endpoint to automate resilience tests.
Key resources: Retry lab guide
Scanner
Section titled “Scanner”Schedule HTTP jobs with custom payloads, headers, and cron-like intervals. LinkPeek preserves every response so you can diff body changes and latency trends over time. Manual reruns and pause/resume controls support incident investigations.
Key resources: Scanner guide
Tunnel monitor
Section titled “Tunnel monitor”Observe Cloudflared Quick Tunnel state directly inside LinkPeek. The monitor surfaces the hostname, restart history, warnings for shared ingress, and the live log tile dedicated to tunnel traffic.
Key resources: Tunnel guide
Realtime fabric
Section titled “Realtime fabric”LinkPeek’s WebSocket hub powers snapshot delivery and fanout for all labs. Clients subscribe to topics (payload.list, log.event, tunnel.status, etc.) to stay synchronized without polling.
Key resources: Realtime fabric guide