Skip to content
Prev Previous commit
Next Next commit
update changelog
  • Loading branch information
Vishwesh Bankwar committed Oct 21, 2022
commit 63bf9d9d5b51e96c6071dd49bb3a9e61bf66e90d
15 changes: 14 additions & 1 deletion src/OpenTelemetry.Instrumentation.Http/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,20 @@

## Unreleased

* **Placeholder**.
* *Breaking change** The `Enrich` callback option has been removed. For better
usability, it has been replaced by three separate options: In case of
`HttpClient` the new options are `EnrichWithHttpRequestMessage`,
`EnrichWithHttpResponseMessage` and `EnrichWithException` and in case of
`HttpWebRequest` the new options are `EnrichWithHttpWebRequest`,
`EnrichWithHttpWebResponse` and `EnrichWithException`. Previously, the single
`Enrich` callback required the consumer to detect which event triggered the
callback to be invoked (e.g., request start, response end, or an exception)
and then cast the object received to the appropriate type:
`HttpRequestMessage`, `HttpResponsemessage`, or `Exception` in case of
`HttpClient` and `HttpWebRequest`,`HttpWebResponse` and `Exception` in case of
`HttpWebRequest`. The separate callbacks make it clear what event triggers
them and there is no longer the need to cast the argument to the expected
type.
([#3792](https://github.com/open-telemetry/opentelemetry-dotnet/pull/3792))

* Added back `netstandard2.0` target.
Expand Down