Try our conversational search powered by Generative AI!

KennyG
Oct 31, 2022
  1321
(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
Join the Content Recommendations Work Smarter webinar May 8th 16.00-16.45 CET with expert Aidan Swain

Learn more about Content Recommendations, with Optimizely’s very own Senior Solutions consultant, Aidan Swain . He will discuss best practices and...

Karen McDougall | Apr 12, 2024

Plugin for Identifying and Bulk Deleting Orphaned Missing Properties in Optimizely

I am aware that the Optimizely World community has extensively discussed this topic, with numerous solutions and code snippets available to help...

Adnan Zameer | Apr 11, 2024 | Syndicated blog

Enhancing the Authoring Experience: Extending the LinkItem

The LinkItem field is one of the most demanded properties by the community, allowing editors to effortlessly create and manage links across pages a...

Santiago Morla | Apr 10, 2024 | Syndicated blog

The distinctions between Optimizely Web Experimentation and Optimizely Feature Experimentation

This blog is part of the series - Unlocking the Power of Experimentation: A Marketer's Insight. Let’s dive into Optimizely's powerful experimentati...

Holly Quilter | Apr 9, 2024