Filtering out exceptions by class when tracing

I've seen other chatter about this, but I think I have a use case which is valid.... hopefully :slight_smile:

I've got an older application using tapestry 4.5, and the 'normal' method of changing page is to throw a PageRedirectException. This is fine, the code has been that way for ever, and it's relatively functional.

I've turned tracing on to see how the code is behaving, and in the 'Error's tab, I see thousands and thousands of 'errors' and the first few I've been investigating (highest counts) is ultimately because a PageRedirectException has been raised to go to a new application page.

I'd like to be able to filter errors, or filter adding things to the errors display, so that I can investigate issues without the noise of specific exceptions that I don't really want to see.

At a minimum it'd be great to be able to just not show PageRedirectExceptions, but I could also see cases where other possibilities would potentially be handy like optimistically trying to parse a string into an integer, and it raising an exception but that exception is handled and expected...

Maybe this is a case of 'im new to elastic-apm and there's a way to do this already' - i'd be equally happy if that's the case :slight_smile:

We have an issue for that over at the Java agent's repo:

Are you interested in creating a PR for this?

yep if it can be controlled via environment variables in the same way the trace variables can be, then that'd be perfect...

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.