{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/", "slug": "dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object", "url": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/" }, "title": "Look in the exceptions table when a Java logger receives an exception object", "summary": "Check the telemetry table before concluding that a log message was lost.", "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:33:38+00:00", "modified_at": "2026-09-17T16:38:45+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 216, "potentially_affected": "Use this review for an instrumented Java application with an apparently missing log message. Identify whether the logging call included an exception object and confirm the Application Insights resource and time interval. Do not assume every absent trace is explained by this routing behavior.", "dse_recommendation": "DSE recommends comparing the logging call with the query used by the support runbook.", "primary_source": { "name": "Configure Azure Monitor Application Insights for Java - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config", "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 documents that passing an exception object to a Java logger sends the log message and exception details to the Application Insights exceptions table rather than the traces table. To inspect messages across both tables, the source proposes a query that combines their results. Microsoft Learn.

\n

Applicability

\n

Use this review for an instrumented Java application with an apparently missing log message. Identify whether the logging call included an exception object and confirm the Application Insights resource and time interval. Do not assume every absent trace is explained by this routing behavior.

\n

DSE recommendation

\n

DSE recommends comparing the logging call with the query used by the support runbook. If both ordinary messages and exception-bearing messages are relevant, define a combined view with clearly labeled record types. Preserve the original tables and fields in the investigation. Review the displayed message content so the support view does not disclose exception details unnecessarily.

\n

Verification

\n

In an approved test build, emit an ordinary log message and a message carrying an exception object. Locate each in the expected table and then in the combined view. Confirm the timestamps and request context refer to the intended test. Record the tested logging pattern so future investigators know which query is appropriate.

\n

Official references

\n

Microsoft Learn: Configure Azure Monitor Application Insights for Java.

", "content_text": "Source facts\nMicrosoft documents that passing an exception object to a Java logger sends the log message and exception details to the Application Insights exceptions table rather than the traces table. To inspect messages across both tables, the source proposes a query that combines their results. Microsoft Learn.\nApplicability\nUse this review for an instrumented Java application with an apparently missing log message. Identify whether the logging call included an exception object and confirm the Application Insights resource and time interval. Do not assume every absent trace is explained by this routing behavior.\nDSE recommendation\nDSE recommends comparing the logging call with the query used by the support runbook. If both ordinary messages and exception-bearing messages are relevant, define a combined view with clearly labeled record types. Preserve the original tables and fields in the investigation. Review the displayed message content so the support view does not disclose exception details unnecessarily.\nVerification\nIn an approved test build, emit an ordinary log message and a message carrying an exception object. Locate each in the expected table and then in the combined view. Confirm the timestamps and request context refer to the intended test. Record the tested logging pattern so future investigators know which query is appropriate.\nOfficial references\nMicrosoft Learn: Configure Azure Monitor Application Insights for Java.", "content_markdown": "## Source facts\n\nMicrosoft documents that passing an exception object to a Java logger sends the log message and exception details to the Application Insights exceptions table rather than the traces table. To inspect messages across both tables, the source proposes a query that combines their results. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config).\n\n## Applicability\n\nUse this review for an instrumented Java application with an apparently missing log message. Identify whether the logging call included an exception object and confirm the Application Insights resource and time interval. Do not assume every absent trace is explained by this routing behavior.\n\n## DSE recommendation\n\nDSE recommends comparing the logging call with the query used by the support runbook. If both ordinary messages and exception-bearing messages are relevant, define a combined view with clearly labeled record types. Preserve the original tables and fields in the investigation. Review the displayed message content so the support view does not disclose exception details unnecessarily.\n\n## Verification\n\nIn an approved test build, emit an ordinary log message and a message carrying an exception object. Locate each in the expected table and then in the combined view. Confirm the timestamps and request context refer to the intended test. Record the tested logging pattern so future investigators know which query is appropriate.\n\n## Official references\n\n[Microsoft Learn: Configure Azure Monitor Application Insights for Java](https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config)." }, "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-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/", "url": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Look in the exceptions table when a Java logger receives an exception object", "item": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/", "url": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/", "headline": "Look in the exceptions table when a Java logger receives an exception object", "description": "Check the telemetry table before concluding that a log message was lost.", "abstract": "Check the telemetry table before concluding that a log message was lost.", "articleBody": "Source facts\nMicrosoft documents that passing an exception object to a Java logger sends the log message and exception details to the Application Insights exceptions table rather than the traces table. To inspect messages across both tables, the source proposes a query that combines their results. Microsoft Learn.\nApplicability\nUse this review for an instrumented Java application with an apparently missing log message. Identify whether the logging call included an exception object and confirm the Application Insights resource and time interval. Do not assume every absent trace is explained by this routing behavior.\nDSE recommendation\nDSE recommends comparing the logging call with the query used by the support runbook. If both ordinary messages and exception-bearing messages are relevant, define a combined view with clearly labeled record types. Preserve the original tables and fields in the investigation. Review the displayed message content so the support view does not disclose exception details unnecessarily.\nVerification\nIn an approved test build, emit an ordinary log message and a message carrying an exception object. Locate each in the expected table and then in the combined view. Confirm the timestamps and request context refer to the intended test. Record the tested logging pattern so future investigators know which query is appropriate.\nOfficial references\nMicrosoft Learn: Configure Azure Monitor Application Insights for Java.", "datePublished": "2026-09-17T16:33:38+00:00", "dateModified": "2026-09-17T16:38:45+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/" }, "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-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/#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": "Look in the exceptions table when a Java logger receives an exception object" }, "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": 216, "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": "Configure Azure Monitor Application Insights for Java - Azure Monitor | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config" } } ] } }