# After updating Apm Agent from 1.1.2 to 1.2 transactions are empty

**URL:** <https://discuss.elastic.co/t/after-updating-apm-agent-from-1-1-2-to-1-2-transactions-are-empty/211081>\
**Category:** APM\
**Tags:** dotnet\
**Created:** [December 9, 2019, 9:31am UTC](https://discuss.elastic.co/t/after-updating-apm-agent-from-1-1-2-to-1-2-transactions-are-empty/211081 "2019-12-09T09:31:16Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Sergey\_Kleyman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sergey_kleyman/32/39333_2.png) [@Sergey\_Kleyman](https://discuss.elastic.co/u/Sergey_Kleyman)\
**Post date:** [December 9, 2019, 5:55pm UTC](https://discuss.elastic.co/t/after-updating-apm-agent-from-1-1-2-to-1-2-transactions-are-empty/211081/6 "2019-12-09T17:55:29Z")

</div>

By default .NET Agent writes its log to standard output (AKA console) so you can redirect application's standard output to a file.  
Also the log has higher chance of helping us if we increase the log level (preferably to `Trace`). You can configure Agent's log level either via [`ELASTIC_APM_LOG_LEVEL` environment variable](https://www.elastic.co/guide/en/apm/agent/dotnet/current/config-supportability.html#config-log-level) which works for any .NET application or if you cannot use environment variables you configure via one of the methods specific to the application framework. At the moment we have alternative configuration sources for applications built using [ASP.NET](https://www.elastic.co/guide/en/apm/agent/dotnet/current/configuration-on-asp-net.html) or [ASP.NET Core](https://www.elastic.co/guide/en/apm/agent/dotnet/current/configuration-on-asp-net-core.html).

---

_[View the full topic](https://discuss.elastic.co/t/after-updating-apm-agent-from-1-1-2-to-1-2-transactions-are-empty/211081)._