[BUG] APM agent 1.18.0.0 not working on .NET 6
See original GitHub issueAPM Agent version
The version of the Elastic.Apm
nuget package is 1.18.0.0
Environment
Docker image: mcr.microsoft.com/dotnet/aspnet:6.0
Application target framework to net6.0
Describe the bug
Work correctly with elastic_apm_profiler version 1.18.0.0
Issue Analytics
- State:
- Created 10 months ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Troubleshooting | APM .NET Agent Reference [1.x]
Use the information in this section to troubleshoot common problems and find answers for frequently asked questions. As a first step, ensure your...
Read more >Problems with ssl apm java agent to elastic cloud
I am trying to deploy an application with an APM java agent in GKE that sends data to an APM integration in elastic...
Read more >What's New in APM Agent - Help Aternity
This release contains bug fixes for the APM Agent, including: ... Net 6 app running in an Alpine container; helper library being loaded...
Read more >Manage errors in APM: Collect, ignore, or mark as expected
If you don't want an error to report to our collector, you can ignore the error, and the APM agent discards the error...
Read more >Troubleshoot APM Java Agent Deployment
This error message indicates that the installer tried to issue a request to the OMC server or gateway, but did not receive any...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi z1c0, Yes I have followed the “Zero code change” instruction. I have auto instrumented a .net5.0 application without problems. As soon as possible I will attach the startup logs.
Hi @karpediemnow, since your last comment suggested that the problem is gone and I have not heard back otherwise, I will resolve this issue. Feel free to reopen it, should the problem still persist. Thank you for reaching out!