ApplicationInsights TelemetryClient is very slow at initializing when in Debug

Question

I have a problem with Microsoft.ApplicationInsights objects. Every time the code hits one of those objects for the first time, the time to initialize is ridiculously long (sometimes even around 40 seconds).

Example 1:

Example 2:

What is the cause of this long first time load? How can I fix this?

Leo · Accepted Answer · 2018-04-06T13:34:12.187

6

Why don't you just disable ApplicationInsight when in debug using a web.config transform?

<?xml version="1.0"?>
<configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform">
  <system.web>
      <httpModules>
        <add xdt:Transform="Remove" xdt:Locator="Match(name)" name="ApplicationInsightsWebTracking" />
      </httpModules>
  </system.web>
  <system.webServer>
    <modules>
      <add xdt:Transform="Remove" xdt:Locator="Match(name)" name="ApplicationInsightsWebTracking"  />
    </modules>
  </system.webServer>
</configuration>

I had similar issues and the answer to this question explained to me how to go about using this snippet in my dev environment (ie. not in the publishing pipeline).

edited Apr 06 '18 at 13:34

answered Apr 06 '18 at 13:26

Leo

5,013
1
28
65

2

Thanks, I've just disabled it - my app starts a lot faster. – SteppingRazor Apr 10 '18 at 10:20
I doubt that during a normal debug session the transform is triggered?! – Falco Alexander Jan 21 '20 at 10:30
@FalcoAlexander - try... it does. – Leo Jan 22 '20 at 11:00
I tried, it still fires Insight events. even though I had to add: ` ` – Falco Alexander Jan 23 '20 at 09:33
also had to add ` `...now it's quiet :) @LeonardoSeccia what about adding that to you answer? – Falco Alexander Jan 23 '20 at 09:40

ApplicationInsights TelemetryClient is very slow at initializing when in Debug

1 Answers1