KennyG
OMVPPaaS CMS Developer Certification
Oct 31, 2022
visibility 3508
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
New logo and login page in Optimizely CMS 13.5

CMS 13.5.0 quietly ships a new logo and a redesigned login page.

Tomas Hensrud Gulla | Oct 30, 2026 |

Is your website agent-ready? Using Cloudflare's readiness tool to assess your website

One of my friends and fellow MVPs, Minesh Shah recently blogged about optimising one of his websites for full AX and agent readiness https://www.li...

Scott Reed | Oct 29, 2026

Visual Builder without Next.js, Part 1: What Astro Has to Rebuild on CMS 13 PaaS

Series: Part 1: What Astro Has to Rebuild on CMS 13 PaaS · Part 2: Does It Survive DXP? (Redis-backed ISR, Graph webhooks, Cloudflare and preview a...

Piotr | Oct 29, 2026

Visual Builder without Next.js, Part 1: What Astro Has to Rebuild on CMS 13 PaaS

A field report on the framework-neutral CMS SDK 3.1 beta: Visual Builder, the content model and live preview in Astro, on a real CMS 13.

Piotr | Oct 29, 2026 |