# .NET Agent does not recognize Elasticsearch.NET calls in the timeline **URL:** \ **Category:** APM\ **Tags:** dotnet\ **Created:** [October 2, 2019, 9:28pm UTC](https://discuss.elastic.co/t/net-agent-does-not-recognize-elasticsearch-net-calls-in-the-timeline/202058 "2019-10-02T21:28:15Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jimmy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jimmy/32/55277_2.png) [@Jimmy](https://discuss.elastic.co/u/Jimmy)\ **Post date:** [October 2, 2019, 9:28pm UTC](https://discuss.elastic.co/t/net-agent-does-not-recognize-elasticsearch-net-calls-in-the-timeline/202058/1 "2019-10-02T21:28:15Z")
**Kibana version** : 7.0.1 **Elasticsearch version** : 7.0.1 **APM Server version** : 7.0.1 **APM Agent language and version** : .NET 1.1.0 **Original install method (e.g. download page, yum, deb, from source, etc.) and version**: Download Page **Fresh install or upgraded from other version?** Fresh **Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**: I have 3 projects: - [ASP.NET](http://ASP.NET) Core 2.2 Web API: The main program in which I installed the Elastic.Apm.NetCoreAll, configured the appsettings.json and edited the startup.cs. - .NET Core 2.2 Class Library: Interfaces and Entities - .NET Core 2.2 Class Library: Implementation of interfaces that use [Elasticsearch.NET](https://github.com/elastic/elasticsearch-net) to make requests to my Elasticsearch cluster. The APM is working fine on Kibana however the timeline does not show the detailed transaction with the Elasticsearch call. Taking a look at the [supported technologies](https://www.elastic.co/guide/en/apm/agent/dotnet/current/supported-technologies.html) page I noticed that outgoing HTTP requests should have automatic instrumentation, so I suppose the transaction sample would show the request to my Elasticsearch server. ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/e/eea54fe7ccac8b6715574510310d53df84072d57.png) Is there anything I'm missing here? Thanks! ---
**Author:** ![GregKalapos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregkalapos/32/37205_2.png) [@GregKalapos](https://discuss.elastic.co/u/GregKalapos)\ **Post date:** [October 2, 2019, 10:14pm UTC](https://discuss.elastic.co/t/net-agent-does-not-recognize-elasticsearch-net-calls-in-the-timeline/202058/2 "2019-10-02T22:14:39Z")
Hi @Jimmy, So, currently we don’t have specific support for the [Elasticsearch.NET](http://Elasticsearch.NET) library, but as you correctly state outgoing HTTP requests are supported, and you should be able to see the HTTP requests that [Elasticsearch.NET](http://Elasticsearch.NET) generates - btw. we have an open PR to have specific support for [Elasticsearch.NET](http://Elasticsearch.NET), but that is not merged and released yet, so let’s ignore that case. So, overall this should work. The first thing that came to my mind: did you turn on the agent with the `UseAllElasticApm()` method? There is another one called `UseElasticApm`, but that does not turn on outgoing HTTP monitoring. More details [in the docs](https://www.elastic.co/guide/en/apm/agent/dotnet/current/setup.html#setup-asp-net-core). If that does not help then the next step would be to set the log level to `Trace` and send us the logs. [Here](https://github.com/elastic/apm-agent-dotnet/blob/master/sample/SampleAspNetCoreApp/appsettings.json#L5) is a sample on how to do that - instead of `Error` just put `Trace` there. Hope this helps, Greg ---
**Author:** ![Jimmy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jimmy/32/55277_2.png) [@Jimmy](https://discuss.elastic.co/u/Jimmy)\ **Post date:** [October 3, 2019, 1:16pm UTC](https://discuss.elastic.co/t/net-agent-does-not-recognize-elasticsearch-net-calls-in-the-timeline/202058/3 "2019-10-03T13:16:58Z")
Hi @GregKalapos, That was it! Thanks! I think I missed these details in the docs because I used the [Configuration on ASP.NET Core page](https://www.elastic.co/guide/en/apm/agent/dotnet/1.x/configuration-on-asp-net-core.html), which does not mention anything regarding the **UseAllElasticApm()** method. It might help others to just add to the Note of the page a reminder about this other possibility. Thanks again, Jimmy ---
**Author:** ![GregKalapos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gregkalapos/32/37205_2.png) [@GregKalapos](https://discuss.elastic.co/u/GregKalapos)\ **Post date:** [October 3, 2019, 2:46pm UTC](https://discuss.elastic.co/t/net-agent-does-not-recognize-elasticsearch-net-calls-in-the-timeline/202058/4 "2019-10-03T14:46:22Z")
Thanks @Jimmy, this is useful feedback - I just opened a [PR](https://github.com/elastic/apm-agent-dotnet/pull/531) to add a note about this. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 24, 2019, 10:46am UTC](https://discuss.elastic.co/t/net-agent-does-not-recognize-elasticsearch-net-calls-in-the-timeline/202058/5 "2019-10-24T10:46:22Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.