{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/", "slug": "dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting", "url": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/" }, "title": "Decide which caught exceptions deserve explicit Application Insights reporting", "summary": "Review handled failures that automatic instrumentation may not report.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "cyber-defense", "label": "Cyber defense", "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-17T16:34:53+00:00", "modified_at": "2026-09-17T16:35:03+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 199, "potentially_affected": "Use this review for a particular handled-error path in an instrumented application. Identify the language, instrumentation already installed, intended telemetry destination and the operational question that the exception should help answer. A handled exception alone does not establish a failed business transaction.", "dse_recommendation": "DSE recommends choosing representative handled failures with the application owner before adding reporting.", "primary_source": { "name": "Add and Modify OpenTelemetry in Application Insights - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-add-modify", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Microsoft explains that some instrumentation libraries report exceptions automatically, while exceptions handled by application code ordinarily are not reported. The OpenTelemetry customization guide describes manual reporting for exceptions that should appear in failure investigations and end-to-end transaction views. Microsoft Learn.

\n

Applicability

\n

Use this review for a particular handled-error path in an instrumented application. Identify the language, instrumentation already installed, intended telemetry destination and the operational question that the exception should help answer. A handled exception alone does not establish a failed business transaction.

\n

DSE recommendation

\n

DSE recommends choosing representative handled failures with the application owner before adding reporting. Define which errors merit investigation, what context is safe to include and how repeated occurrences should be interpreted. Review the relevant language example in the current source and limit the first change to a controlled application build.

\n

Verification

\n

Exercise the approved handled-error path and locate its exception record alongside the intended transaction. Also run a normal request and an automatically captured failure. Check that the added reporting supplies useful context without duplicating existing records or exposing request secrets. Preserve sanitized examples and the instrumentation configuration for later diagnosis.

\n

Official references

\n

Microsoft Learn: Add and Modify OpenTelemetry in Application Insights.

", "content_text": "Source facts\nMicrosoft explains that some instrumentation libraries report exceptions automatically, while exceptions handled by application code ordinarily are not reported. The OpenTelemetry customization guide describes manual reporting for exceptions that should appear in failure investigations and end-to-end transaction views. Microsoft Learn.\nApplicability\nUse this review for a particular handled-error path in an instrumented application. Identify the language, instrumentation already installed, intended telemetry destination and the operational question that the exception should help answer. A handled exception alone does not establish a failed business transaction.\nDSE recommendation\nDSE recommends choosing representative handled failures with the application owner before adding reporting. Define which errors merit investigation, what context is safe to include and how repeated occurrences should be interpreted. Review the relevant language example in the current source and limit the first change to a controlled application build.\nVerification\nExercise the approved handled-error path and locate its exception record alongside the intended transaction. Also run a normal request and an automatically captured failure. Check that the added reporting supplies useful context without duplicating existing records or exposing request secrets. Preserve sanitized examples and the instrumentation configuration for later diagnosis.\nOfficial references\nMicrosoft Learn: Add and Modify OpenTelemetry in Application Insights.", "content_markdown": "## Source facts\n\nMicrosoft explains that some instrumentation libraries report exceptions automatically, while exceptions handled by application code ordinarily are not reported. The OpenTelemetry customization guide describes manual reporting for exceptions that should appear in failure investigations and end-to-end transaction views. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-add-modify).\n\n## Applicability\n\nUse this review for a particular handled-error path in an instrumented application. Identify the language, instrumentation already installed, intended telemetry destination and the operational question that the exception should help answer. A handled exception alone does not establish a failed business transaction.\n\n## DSE recommendation\n\nDSE recommends choosing representative handled failures with the application owner before adding reporting. Define which errors merit investigation, what context is safe to include and how repeated occurrences should be interpreted. Review the relevant language example in the current source and limit the first change to a controlled application build.\n\n## Verification\n\nExercise the approved handled-error path and locate its exception record alongside the intended transaction. Also run a normal request and an automatically captured failure. Check that the added reporting supplies useful context without duplicating existing records or exposing request secrets. Preserve sanitized examples and the instrumentation configuration for later diagnosis.\n\n## Official references\n\n[Microsoft Learn: Add and Modify OpenTelemetry in Application Insights](https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-add-modify)." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/", "url": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Decide which caught exceptions deserve explicit Application Insights reporting", "item": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/", "url": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/", "headline": "Decide which caught exceptions deserve explicit Application Insights reporting", "description": "Review handled failures that automatic instrumentation may not report.", "abstract": "Review handled failures that automatic instrumentation may not report.", "articleBody": "Source facts\nMicrosoft explains that some instrumentation libraries report exceptions automatically, while exceptions handled by application code ordinarily are not reported. The OpenTelemetry customization guide describes manual reporting for exceptions that should appear in failure investigations and end-to-end transaction views. Microsoft Learn.\nApplicability\nUse this review for a particular handled-error path in an instrumented application. Identify the language, instrumentation already installed, intended telemetry destination and the operational question that the exception should help answer. A handled exception alone does not establish a failed business transaction.\nDSE recommendation\nDSE recommends choosing representative handled failures with the application owner before adding reporting. Define which errors merit investigation, what context is safe to include and how repeated occurrences should be interpreted. Review the relevant language example in the current source and limit the first change to a controlled application build.\nVerification\nExercise the approved handled-error path and locate its exception record alongside the intended transaction. Also run a normal request and an automatically captured failure. Check that the added reporting supplies useful context without duplicating existing records or exposing request secrets. Preserve sanitized examples and the instrumentation configuration for later diagnosis.\nOfficial references\nMicrosoft Learn: Add and Modify OpenTelemetry in Application Insights.", "datePublished": "2026-09-17T16:34:53+00:00", "dateModified": "2026-09-17T16:35:03+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260917-007-decide-which-caught-exceptions-deserve-explicit-application-insights-reporting/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Decide which caught exceptions deserve explicit Application Insights reporting" }, "articleSection": [ "Cybersecurity", "IT" ], "keywords": [ "Cybersecurity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 199, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Add and Modify OpenTelemetry in Application Insights - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-add-modify" } } ] } }