Live capture
Tap a bounded sample of events as they enter a log source's pipeline, before your steps run
Use live capture (the live tap) to inspect incoming events before your processing steps run. A tap captures events as they enter one log source's pipeline on Vector, for a bounded window, and returns them to your browser. It shows what the active configuration receives, not the result of an unpublished draft and not a search of stored data.
Capture input
- Open the pipeline in Ingestion → Pipelines and switch to its tap panel.
- Set the window in seconds and the maximum number of events. Defaults are 30 seconds and 100 events.
- Start the tap and send traffic to that source. The panel counts down while the window is open; cancel to stop early.
- When the tap completes, select an event to inspect it, or use the captured events as preview input to see what your draft does to them.
Live capture requires log_sources:view, search:execute, and access to the source. It is available only where the deployment configures the tap relay; otherwise the panel says it is unavailable and you can load recent events or paste a sample instead. It observes traffic without changing delivery.
Bounds and retention
| Bound | Default | Maximum |
|---|---|---|
| Window | 30 seconds | 60 seconds |
| Events | 100 | 1,000 |
| Bytes per event | 64 KiB | |
| Bytes per capture | 8 MiB |
Vector samples at most 50 events every 500 ms into a tap, so a busy source's tap is a sample, not a complete copy. A tap ends when its window closes, its event or byte limit is reached, or the stream closes early; the panel says which.
You can run one tap at a time, and each API replica runs a limited number at once; a refused tap answers 429 with Retry-After. Fields with credential-like names are removed from captured events before they are returned. Nothing is persisted: captured events live only in your browser memory, and both the start and completion of a tap are audited.
Troubleshoot
Need help with these checks? Contact support with the deployment, request ID and time with timezone.
No events during the window
No traffic means nothing arrived during the window; it does not prove the sender is broken. Check that the sender's token is bound to this source, or that the pull source routes to it, then retry while it is sending.
Live tap is busy or unavailable
Busy means you already have a tap running, or the replica is at its limit: wait and retry. Unavailable means the deployment has no tap relay configured. Source-event permission required means you lack search:execute or access to the source.
Load recent events remains available for already-stored data. It is not live capture.