Although we can see "Internal processes" when we hit the "Currently Active Sessions" link on the "Current" tab, thereby exposing Stored Procedures spawned via Service Broker, NONE of the information about the queries, waits, resources, etc. are collected, which means that for an application actively using an Async OLTP Model, we are effectively RUNNING BLIND with DPA, which makes it an expensive White Elephant!
sp_whoisactive is our go-to process to at least find out what's running, but it's a poor cousin especially as it collates NOTHING we can easily persist and analyze!
Kindly go the extra mile to include Async Model environments in what DPA sees.