KennyG
OMVPPaaS CMS Developer Certification
Oct 31, 2022
visibility 3412
star star star star star
(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

error Please login to comment.
Latest blogs
What made Scheduled Jobs faster in Optimizely CMS 13.3.0

A look under the hood at the update that made scheduled jobs faster.

Tomas Hensrud Gulla | Oct 9, 2026 |

New DDS explorer addon for Optimizely CMS

I wanted to be able to manage Dynamic Data Store from within Optimizely CMS, so I created another addon.

Tomas Hensrud Gulla | Oct 8, 2026 |

Queryable or Searchable? How indexing type changes your Optimizely Graph query

The Property Indexing Type on a CMS field decides whether Optimizely Graph will return it, filter it, or run full-text search on it. Default,...

Chirag Khanna | Oct 8, 2026 |

How to Build Optimizely CMS 13 with Visual Builder in .NET

A code-first guide for .NET developers moving from Optimizely CMS 12 to CMS 13, covering Visual Builder: ExperienceData, Sections, Elements, tag...

Andy Blyth | Oct 8, 2026 |