# Look in the exceptions table when a Java logger receives an exception object

> Check the telemetry table before concluding that a log message was lost.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:33:38+00:00
- Modified: 2026-09-17T16:38:45+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, IT
- Reading time: 1 minutes

## What you need to know

Check the telemetry table before concluding that a log message was lost.

## 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.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config).

## Applicability

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. 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.

## Verification

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.

## Official references

[Microsoft Learn: Configure Azure Monitor Application Insights for Java](https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config).

## Primary reference

- Name: Configure Azure Monitor Application Insights for Java - Azure Monitor | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Look in the exceptions table when a Java logger receives an exception object,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-082-look-in-the-exceptions-table-when-a-java-logger-receives-an-exception-object/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.