Take the community feedback survey now.

KennyG
Oct 31, 2022
  2116
(1 votes)

Debugging Using The Output Panel? Filter Out That Noise!

This is a quick tip!

If you are making use of the Output window in Visual Studio but can't deal with all the Application Insight "noise", try this!

Say you want to monitor something during a huge import or similar situation so you output some values at a breakpoint but let the program continue running:

But you can't see your custom messages for all the Application Insights output:

I found a handy setting that just affects Visual Studio (not your Azure App Insights instance).

Add TelemetryDebugWriter.IsTracingDisabled to your Startup.cs class and set it to true:

This clears out a lot of the noise so you can find your own output messages!

Got other good VS debugging tips? Let me know in the comments.

References:

Oct 31, 2022

Comments

Please login to comment.
Latest blogs
Going Headless: 3 Ways to Store Custom Data in Optimizely Graph

Welcome to another installment of my  Going Headless  series. Previously, we covered: Going Headless: Making the Right Architectural Choices Going...

Michał Mitas | Nov 3, 2025

A day in the life of an Optimizely OMVP - What's New in Optimizely CMS: A Comprehensive Recap of 2025 Updates

Hello and welcome to another instalment of a day in the life of an Optimizely OMVP. On the back of the presentation I gave in the October 2025 happ...

Graham Carr | Nov 3, 2025

Optimizely CMS Mixed Auth - Okta + ASP.NET Identity

Configuring mixed authentication and authorization in Optimizely CMS using Okta and ASP.NET Identity.

Damian Smutek | Oct 27, 2025 |

Optimizely: Multi-Step Form Creation Through Submission

I have been exploring Optimizely Forms recently and created a multi-step Customer Support Request Form with File Upload Functionality.  Let’s get...

Madhu | Oct 25, 2025 |