AWSXRayRecorder is full framework only. Need .NET Core.

[adamhathcock]

I don't know where to go for this but it is full framework only.

I could probably port the usage to .NET Core but I don't know where the source is.

[adamhathcock]

https://www.nuget.org/packages/AWSXRayRecorder/1.0.1-beta

When being installed the target is just net45

[PavelSafronov]

At the moment the AWSXRayRecorder is only supported on net45. We are looking to porting this functionality to .NET Core, but cannot give an ETA.
Keeping this issue open and will update it with any progress.

[adamhathcock]

Is the code open source? Is all that is needed is to hook into Asp.Net Core middleware instead of a http handler of whatever the System.Web version was called?

I'm interested in helping.

[PavelSafronov]

@the source for AWSXRayRecorder is not open source at this moment, and I cannot provide an ETA of when it will be.

[adamhathcock]

That's disappointing. I was hoping the X-Ray protocol would be open so we could embed the implementation in various applications.

[PavelSafronov]

We are definitely interested in making it as easy as possible for members of the AWS community to implement X-Ray integration in whichever language and framework is best suited to your needs. To that end we are working on documenting the protocol, which should be available in the next few weeks, and will eventually publish the source for the current .NET version to GitHub.

[adamhathcock]

Great! Thank you.

[Caldas]

@PavelSafronov I was looking for AWSXRayRecorder github page, but as I read above I will not found it.

But we are starting using at VTEX and one of the problems I found was that library stuck when working in a test environment without XRay service running. I believe in some point the TracingMessageHandler handler it lock waiting for service response (sorry I don't know)

Since there isn't a public project I hope you can pass my message forwarder ..

PS: Sorry use reply as "email"

[PavelSafronov]

@Caldas , please post your question to the AWX X-Ray forum and the team should be able to help you out.

[yishengl]

@Caldas There is no blocking logic in TracingMessageHandler. It doesn't acquire any locks or waiting for any external components. Actually, there is no direct connection between XRayRecorder and XRay service. The communication is through a daemon on the host using UDP package.

As @PavelSafronov stated, AWS X-Ray Forum is the better place to ask any XRay related questions. Can you post your question there and elaborate more about what you did and what's the problem you see? I would like to help you figure out what went wrong.

[sstevenkang]

Closing this as the discussion seems to be taking place in the forums. Feel free to reopen if I missed anything.

[ollnixon]

@sstevenkang: I would suggest that this issue needs to be re-opened. It was originally opened due to lack of .NET Core support which, as far as I can tell, hasn't been implemented.

cc @adamhathcock

[adamhathcock]

I agree this should be reopened as it was high jacked by an irrelevant question then closed.