To prevent specific Struts Actions and methods from being monitored, add a custom exclude rule. The criteria for Struts exclude rules are the same as those for custom match rules. In particular, you may need to exclude custom-built dispatch servlets, as described next.

Exclude Custom-built Dispatch Servlet

When a Struts action is called, it can demarcate a transaction as an entry point. Splunk AppDynamics instruments the Struts invocation handler to get the action name because the Struts action is not an interface. The invocation handler provides the Java Agent with the name of the action being invoked. If the dispatcher Servlet is custom-built and has not been excluded from instrumentation, the wrong entry point could be instrumented and the business transaction could be misidentified.

To address this issue, add a custom exclude rule for the dispatcher servlet or add a BCI exclude for it.