Hi Henry,
There are 2 types of CEM/Introscope integration and for the "Problem resolution triage" type Business Segment data is only created by Introscope Triggered Transaction Traces when the CEM slow time defect threshold is breached:
Configure Introscope to Work with CEM - CA Application Performance Management - 10.5 - CA Technologies Documentation
So the Introscope data for Responses Per Interval (RPI) will not be a direct match to the CEM "Good Business Transactions" because not all Business transactions have been traced. From the 3 data points on your screenshots it looks like Introscope traces were triggered from CEM at some point due to some individual slow transactions but it would appear that did not result in any defective Business transaction
Similarly the "Defective Business Transactions" are based on the defect thresholds being exceeded in CEM and are not connected to "Errors Per Interval".
So in summary we are dealing with 2 different sets of data.
For the 2nd type of integration for "Customer experience metrics" (RTTM/BTstats), the CEM UI data and the metric data you see under "CEM Agent > Business Services" is all data that came from the TIM so you can use that for comparison purposes.
Hope that all makes sense & helps.
Regards,
Lynn