Hello Jeff,
you are right, this is one of the CA APM problems. It is lacking in some more useful/individual ways to analyse the collected metrics data. The metrics data is available, but no way to analyse the metrics data.
This is one reason you find a hint to Grafana (see APMSQL Cookbook - CA Application Performance Management - 10.7 - CA Technologies Documentation), I think.
I copy the "importent" metrics data into a Postgres DB to analyse the collected metrics data. This is awkward to do, but more easy to handle and I can group the metrics data based on the used queries to select the data, without creating additional matrics data at the collection time.
See Using Grafana with CA APMSQL - CA Application Performance Management - 10.7 - CA Technologies Documentation, this is a suggestion only.
With regards,
Lutz
p.s.
APM 10.5+ (APMSQL must be available) -> APM 10.7+ for AIX APMSQL
Tomcat 8+ -> Jetty is supported also
Grafana 4.6.0+ -> Linux only