Guillaume Delahaye
Guillaume Delahaye
As a further step it might be worth investigating integrating [TestContainers](https://dotnet.testcontainers.org/). Looking at their list of [modules](https://dotnet.testcontainers.org/modules/),they have nuget packages for [Kafka](https://www.nuget.org/packages/Testcontainers.Kafka) and [RabbitMq](https://www.nuget.org/packages/Testcontainers.RabbitMq). That's probably a project in it's...
### GitHub Username @g7ed6e ### Requirements - [x] I have reviewed the community membership guidelines (https://github.com/open-telemetry/community/blob/main/community-membership.md) - [x] I have enabled 2FA on my GitHub account. See https://github.com/settings/security - [x]...
> I do still think we could do more to help connect traces when consuming ([#1493 (comment)](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/1493#discussion_r1640199079)) but LGTM that could be done as follow-up work. @CodeBlanch I missed that...
Resolves #1932 @CodeBlanch : I adapted a bit the API you suggested. @lmolkova : Can you confirm that's OK to output both a receive and a process span for a...
Fixes # Design discussion issue # ## Changes Please provide a brief description of the changes here. ## Merge requirement checklist * [ ] [CONTRIBUTING](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/main/CONTRIBUTING.md) guidelines followed (license requirements, nullable...
It would be good to link the example from here. or have some basic examples on how to configure the instrumentation. (Not a blocker - can be a follow up...
Looks good to me overall. Left couple minor comments that can be addressed in the follow up. I do have the same concern as @CodeBlanch noted in https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/1493#issuecomment-2189854737 about the...
## Description Add OTEL messaging semantic conventions to `Aspire.ConfluentKafka` component/integration. Fixes # (issue) ## Checklist - Is this feature complete? - [x] Yes. Ready to ship. - [ ] No....
@mconnew As discussed this a first naive implementation to handle BinaryFormatter deprecation coming with .NET9.
It could also be that the contract lives in a separate assembly from the main application assembly and generation of the invoker wasn't enabled in that other assembly. I think...