KennyG
Oct 31, 2022
  2804
(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
Why Optimizely's MCP Servers Offering Matters

MCP (Model Context Protocol) is what enables, connecting AI agents directly to enterprise tools. With Optimizely OPAL and Optimizely MCP servers,...

K Khan | Jun 9, 2026

A day in the life of an Optimizely OMVP: Managing Graph search: the native portal and the community plugin

Optimizely Graph has quietly become the search engine sitting underneath most new Optimizely builds. It ships with CMS 13, it's the answer to "what...

Graham Carr | Jun 9, 2026

Extending SelectMany for Multi-Column Checkbox Layouts in Optimizely CMS 12

By default, a SelectMany property is rendered as a vertical checkbox list in the CMS editor. While this works well for a small number of options,...

Sanjay Kumar | Jun 9, 2026

Optimizely CMS (SaaS) MCP Basics

What just shipped Optimizely quietly dropped something significant: a hosted Model Context Protocol (MCP) server for CMS (SaaS). This means your...

Kiran Patil | Jun 9, 2026 |