Splunk AppDynamics supports both the WebSocket and the HTTP long-polling client transports in CometD. It tracks CometD messages as they traverse channels using POJO rules that split business transactions based on channel name.

Accordingly, business transactions in Splunk AppDynamics correspond to CometD channels. The following screenshot shows a business transaction generated for the /market/nyse channel:

Splunk AppDynamics provides built-in exclude rules for the servlets that implement CometD transport functions, org.cometd.annotation.AnnotationComet and org.cometd.server.CometdServlet. For best results, you should exclude tracking for the container servlet as well, as described in the next section.