MissingMethodException: Method not found: 'System.String Amazon.XRay.Recorder.Core.Strategies.SegmentNamingStrategy.GetSegmentName(Microsoft.AspNetCore.Http.HttpRequest)'.
- Dominant language
- C#
- Stars
- 115
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am are trying to integrate XRay into a ASP.NET Core 2.1 Application using full .NET Targeting (.NET Framework 4.6.1) running in Elastic Beanstalk. The reason for full ..NET targeting is integration with legacy services using assemblies only supporting older .net versions.
When registering XRAY using the .NET Core method [Link](https://github.com/aws/aws-xray-sdk-dotnet/tree/master#aspnet-core-framework-net-core--nuget) the following exception occurs:
MissingMethodException: Method not found: 'System.String Amazon.XRay.Recorder.Core.Strategies.SegmentNamingStrategy.GetSegmentName(Microsoft.AspNetCore.Http.HttpRequest)'.
Amazon.XRay.Recorder.Handlers.AspNetCore.Internal.AWSXRayMiddleware.ProcessHTTPRequest(HttpContext context)
Amazon.XRay.Recorder.Handlers.AspNetCore.Internal.AWSXRayMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
It believe a similar issue was raised in issue #36 which has been closed but I don't see any comments on how work around this issue?
Contributor guide
Research direction
Start with the ASP.NET Core integration guidance linked in the issue and inspect AWSXRayMiddleware.ProcessHTTPRequest and Invoke, where the exception is reported. Reproduce the setup on ASP.NET Core 2.1 targeting .NET Framework 4.6.1, then compare the referenced issue #36 for compatibility clues. Done means the middleware runs without the MissingMethodException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, csharp
- Domain
- backend, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100