Splunk AppDynamics

Caught exception that is logged as info treated as an Error

CommunityUser
Splunk Employee
Splunk Employee

Hello,

My team has a scenario where a frequently used API catches an Exception and logs it as an info (using log4j2).  AppD is showing this as a transaction error each time it occurs, although this is a benign exception.  My understanding was that exceptions are only treated as business transaction errors if they are uncaught or logged with level ERROR or FATAL.

Are there any other situations that would cause caught/info logged exceptions to be treated as errors?  The exception in question is a RuntimeException.  Do caught RuntimeExceptions still get treated as a business transaction error?

Regards,

Jeremy

Labels (1)
0 Karma

Peter_Holditch
Builder

Exceptions that are thrown through instrumentation (i.e. thrown within a backend call and handled by the application code) will get detected like this.

You can configure the agent to ignore certain exceptions if required.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

In this scenario, it was not thrown by a backend call.  The code in question is contained entirely through the java service/application.

I plan to configure our Error/Exception detection to ignore this, but I wanted to validate that this is expected behavior.

0 Karma
Get Updates on the Splunk Community!

Why You Can't Miss .conf25: Unleashing the Power of Agentic AI with Splunk & Cisco

The Defining Technology Movement of Our Lifetime The advent of agentic AI is arguably the defining technology ...

Deep Dive into Federated Analytics: Unlocking the Full Power of Your Security Data

In today’s complex digital landscape, security teams face increasing pressure to protect sprawling data across ...

Your summer travels continue with new course releases

Summer in the Northern hemisphere is in full swing, and is often a time to travel and explore. If your summer ...