JT

Worth mentioning that OTEL's HttpClient instrumentation already covers a handful of metrics you're looking at collecting: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/src/OpenTelemetry.Instrumentation.Http/README.md A number of these metrics are baked into .NET 8+ as well: https://learn.microsoft.com/en-us/dotnet/core/diagnostics/built-in-metrics-system-net

> if you'd like to assist with the release of version 7, test out an RC and report back how it works in your environment. @lukebakken Just some feedback as...

> https://blog.marcgravell.com/2019/08/prefer-valuetask-to-task-always-and.html?m=1 Worth mentioning that this blog post is out of date. The value task pooling mentioned was a .NET 5 experiment & never shipped as it negatively impacted performance...

- Fix the discrepancy between the timestamp fields on `IBatchEvents` vs normal query events.

All assertions should already include the body per https://github.com/JasperFx/alba/blob/master/src/Alba/ScenarioAssertionException.cs#L57

@andrueastman Would it be possible to get this in pre-2.0 but behind a feature flag? At minimum it'd be good to get the builder properties fixed: 

Would you be able to open a PR with a test that reproduces this? A chunk of code has changed in this space for v8 so we'd need to verify...