Do not record streaming measurement for quotes

[jmg-duarte]

Description

With the new streaming measurements we started recording quotes too, this skews the metrics, the PR fixes it.
It also brings back the http_body logging that was lost when moved to the observe crate.

Changes

• Add metrics parameter that enables the metrics recording
• Add the http_body filter to the default log filter

How to test

Grafana

[claude]

Claude finished @jmg-duarte's task in 1m 43s —— View job

---

PR Review: Do not record streaming measurement for quotes

• Read PR changes and understand context
• Review streaming/mod.rs metrics changes
• Review config/arguments changes
• Post review findings

The change is clean and does what it says. The metrics: Option<&'static Metrics> threading is a neat way to gate record_auction_overhead so quotes (via stream_body) no longer skew the serialize_request overhead metric, while real auctions (via stream_body_and_gzip) still record it. The observe::http_body=debug filter addition correctly re-enables the transmission-timing logs — note this applies to quotes too, but that's log-only, not metrics, and appears intended.

One thing worth considering (posted inline): the metric decision is now coupled to the archiving path rather than directly to quote-vs-auction, so disabling archiving would silently drop the auction metric as well. Minor and likely fine in practice.

Nothing blocking. LGTM.

[gemini-code-assist]

Code Review

This pull request updates the default log filter to include observe::http_body=debug in both shared.rs and arguments.rs. Additionally, it refactors the streaming logic in crates/driver/src/infra/solver/streaming/mod.rs by introducing an optional metrics parameter to stream_into. This allows the caller to conditionally record auction overhead metrics, specifically disabling them for quotes while keeping them enabled for proper auctions. I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[MartinquaXD]

I think there is 1 more metric that would be super nice to have.
Feel free to merge as is if you don't want to increase the scope of this PR.

[MartinquaXD]

Could you please also record the total time and measure that for each solver individually?

[jmg-duarte]

Done, please take a look and let me know if it is what you were looking for

[MartinquaXD]

Yeah, that's exactly what I had in mind. This will be very helpful to help individual solvers resolve bottlenecks.