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

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.

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.