Unable to configure Elastic APM on .NET 4.8

Elastic Stack Elastic Agent
1

Dear All,

We are trying to setup Elastic APM on one of our application running on the .NET 4.8. And completed the below configuration on the application side.
But the service is still not showing on the ELK APM dashboard. Kindly suggest.

Webconfig :-

    <add key="ElasticApm:ServerUrls" value="http://<ip-address>:8200" />
    <add key="ElasticApm:ServiceName" value="TAD-portal" />
    <add key="ElasticApm:Environment" value="Production" />
    <add key="ElasticApm:SecretToken" value="UAT" />
    <add key="ElasticApm:TransactionSampleRate" value="1.0" />

gloabl.aspx :-

using Elastic.Apm;using Elastic.Apm.AspNetFullFramework;

protected void Application_Start()
{
Agent.Setup(new AgentComponents());
}

2

Hi @rahulsamsung,

Welcome! Which version of the .NET agent and Elasticsearch are you using?

Can you confirm that you are using supported technologies in your app? Do you see any errors or warnings from the agent in the application logs, and any logs in the Discover screen?

Let us know!

3

Hey @carly.richmond

Thanks for your response.
We are using ELK 8.15.5 and .NET 4.8. which should be supported according to the supported technologies. We didn't find any error or warning message as such.

4

Ok, did you try specifying the debug log level as covered in the docs? Hopefully that shoukld give you some additional diagnostics to figure out why the agent isn't sending.

5

Hi @carly.richmond
We are still not able find any logs but we can see the traffic of agent on ELK server. Please provide your assistance.
Also, Is there any other way to configure the APM? Without making the changes in code?
Kindly suggest.

6

@rahulsamsung looking at the documentation here it looks like zero code instrumentation support is available for .NET 5 or later, so you would need to manually instrument for .NET 4.8:

On .NET Core 3.0+ or .NET 5+ , the agent supports auto instrumentation without any code change and without any recompilation of your projects. See Zero code change setup on .NET Core for more details.

To confirm, you are seeing traffic going through the Elastic APM server? Is this a custom dashboard that you have built or one of the Observability screens in Kibana? If you could share a screenshot of what you see and your configuration we can try to help.

7

We are checking the default observability APM dashboard to see the services. The traffic we captured on ELK server is using the tcpdump.

8

Ok, but tcpdump is a command line utility. How does that relate to the .NET APM agent and the signals you're not seeing from that? Are there 2 sources that you are not seeing coming through?

Can you share a screenshot of the dashboard within APM that you're not seeing any data, along with the APM configuration for your application? It might also be a good idea to enable global file logging at DEBUG level to see if any errors are being triggered on the agent side as per the troubleshooting docs.

Let us know!