osproxy-capture 1.0.0

The traffic-capture seam: a Capture trait an external recorder (e.g. a Kafka writer) implements, with composable redaction. No broker dependency.
Documentation
  • Coverage
  • 100%
    30 out of 30 items documented0 out of 13 items with examples
  • Size
  • Source code size: 13.97 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 672.03 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 6s Average build duration of successful builds.
  • all releases: 7s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • huyz0/opensearch-proxy
    1 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • huyz0

Full-fidelity traffic capture (tenant-agnostic).

A capture proxy forwards each request to the upstream while recording the raw request and response to a durable stream, so a replayer can later apply that stream to another cluster (the OpenSearch Migration Assistant capture proxy). This crate is the seam: [Capture] receives each exchange; a queue writer (the osproxy-kafka crate), a file recorder, or the in-memory [MemoryCapture] implement it. It pulls in no broker dependency, so the seam is implementable from a leaf crate without dragging a Kafka client into the default build.

This is not the shape-only telemetry. Everything else osproxy records is shapes/ids/names and safe to expose by construction. A capture record carries the raw bodies and header values, tenant data, and any credential a redaction layer did not strip. The capture stream is a privileged channel: secure it (encryption, access control), and enable it deliberately, never by default. Redaction is composed in via [RedactingCapture] rather than baked into every recorder.