Module capture
Available on crate features
http and inspect and std only.Structs§
- Capture
Config - Capture admission and optional metadata enrichment. Limits count logical serialized record bytes; a storage backend can independently limit physical bytes. HTTP record metadata must fit within 64 KiB; payload bytes stream separately. These are storage limits, not a process RSS limit. Summaries and typed observations are retained separately, bounded in count by connection/exchange admission; custom observers must bound any variable-sized metadata they attach. Payloads belong in storage.
- Capture
Connection Guard - Capture
Details - Capture
Filter - Parsed selectors and substring searches. Text patterns use shared storage; native selectors avoid reparsing or formatting every captured exchange.
- Capture
Http Layer - Capture
Metadata - Distinct ownership scopes for captured protocol observations.
- Capture
Query - A bounded view suitable for an API, native GUI, or TUI. A cursor pages older connections.
- Capture
Selection - A stable selection that retains its storage and can be read one exchange at a time, without materializing every selected body in memory.
- Capture
Snapshot - Capture
Store - Captured
Body Source - Pins the currently committed HTTP body records. Reopening this view always yields the same prefix, even during capture, eviction or clearing the inspector.
- Captured
Record Stream - Typed metadata and a reader over the raw payload. Downloads, exporters and protocol consumers can pipe this reader directly without a decode buffer.
- Connection
Id - Correlates transport metadata across protocol layers on one connection.
- Connection
Query - A human-visible connection number, optionally entered with a leading
#. - Exchange
Capture - Pins an exchange, its observations and storage while an adapter or reader uses it.
- Http
Connection Summary - HTTP observations on a transport connection.
- Http
Exchange Id - Correlates an HTTP exchange with its upgraded protocol adapter.
- Http
Exchange Summary - HTTP exchange data. Connection observations are obtained through
connection_id. - Http
Upgrade Capture Guard - Mark
Protocol Layer - Observe
Connection Layer - Replay
Request
Enums§
- Captured
Body - Filter
Value - A parsed selector. Unknown expressions remain visible without matching data.
- Protocol
Query - Status
Query - Stored
Record
Traits§
- Capture
Observer - Optional enrichment at HTTP head boundaries. Protocol owners supply typed
observations through
CaptureMetadata; no protocol-specific fields are required. - Captured
Record - An adapter-owned record. Metadata must fit in 64 KiB; payloads stay raw and
stream separately. Implementations should return an existing
Byteshandle frompayload, without allocating another payload buffer.