Hi everyone,

I'm currently building Lens, an open-source Rust tool for visualizing application traffic during local development.

One of the biggest architectural decisions has been choosing how to observe network traffic.

After considering packet capture, instrumentation, and eBPF, I decided to build Lens around a transparent proxy architecture.

The current goals are:

• Decode multiple application protocols
• Build request flow graphs
• Measure latency
• Redact sensitive information
• Support Linux, macOS, and Windows

Before implementing additional protocol support, I'd appreciate feedback from anyone who has built networking software in Rust.

Some questions I'm thinking about:

• Have you built a proxy-based networking tool?
• What problems did you run into?
• Are there crates or projects I should study?
• Are there architectural pitfalls I should consider before the implementation grows further?

Repository:

I'd appreciate contributions to the repository.

1 post - 1 participant

Read full topic