Here's something you might find interesting. In order to figure out which Firebase network calls were getting captured by AppDynamics, I enabled Firebase Performance again and turned on AppDynamics logging with Instrumentation.start( AgentConfiguration.builder() .withAppKey(BuildConfig.APPDYNAMICS_EUM_KEY) .withContext(applicationContext) .withLoggingEnabled(true) ... I did see captures of a Firebase URL (https://firebaselogging-pa.googleapis.com/v1/firelog/legacy/batchlog) in the logs, like this: I/AppDynamics: [{"type":"network-request","ec":5216,"eid":"032d59a6-8e77-455c-8e8e-c3605d8dafcf","sessionCounter":-1,"st":1652898366005,"sut":1311277514,"et":1652898366960,"eut":1311278468,"bkgd":false,"url":"https://firebaselogging-pa.googleapis.com/v1/firelog/legacy/batchlog","hrc":200,"crg":"f2629914-c6ab-4a8e-8a2e-3fae504f1274","bts":[],"see":false,"is":"AppDynamics.URLConnection","avi":52,"av":"4.0.8","agv":"20.5.0","ab":"e7031ad7","dm":"samsung","dmo":"SM-G781U1","ds":110167,"tm":"5628","cf":"1804800","cc":8,"osv":"12","ca":"unknown","ct":"wifi","bid":"33518b01-0b6f-496e-bc1b-8810a92469b6"}] So I tried filtering them out with this: Instrumentation.start( AgentConfiguration.builder() .withAppKey(BuildConfig.APPDYNAMICS_EUM_KEY) .withContext(applicationContext) .withLoggingEnabled(true) .withExcludedUrlPatterns( setOf( "^https:\\/\\/firebaselogging\\-pa\\.googleapis\\.com.*\$", ) ) But they were fairly infrequent, and the high data usage was still present. What I did see being printed repeatedly were entries like these, which seemed to be logging calls made to the AppDynamics collection URL (https://col.eum-appdynamics.com/eumcollector/mobileMetrics?version=2😞 2022-05-18 14:29:25.005 28372-28457/? I/AppDynamics: [2:29:25 PM Eastern Daylight Time] Agent sending beacons to collector (https://col.eum-appdynamics.com/eumcollector/mobileMetrics?version=2) [AD-AAB-AAC-NMJ]:
2022-05-18 14:29:25.006 28372-28457/? I/AppDynamics: [{"type":"network-request","ec":5381,"eid":"6e02c4f4-fe8a-4c7e-9a7b-45297837b2be","sessionCounter":-1,"st":1652898564881,"sut":1311476390,"et":1652898564999,"eut":1311476508,"bkgd":false,"url":"https://col.eum-appdynamics.com/eumcollector/mobileMetrics?version=2","pcl":2,"hrc":200,"crg":"da9ee96c-db86-4174-a35e-535d02f60736","bgan":"appdynamics_eee1d4f8-67a2-498e-a725-47e29803822e","bts":[{"btId":"559464","time":-1,"estimatedTime":0}],"see":false,"is":"AppDynamics.URLConnection","avi":52,"av":"4.0.8","agv":"20.5.0","ab":"e7031ad7","dm":"samsung","dmo":"SM-G781U1","ds":110167,"tm":"5628","cf":"1804800","cc":8,"osv":"12","ca":"unknown","ct":"wifi","bid":"8f6360f2-6186-46d0-ac36-d9f340cff65b"}] It almost seems like AppDynamics is capturing calls to its own collection URL, repeatedly, but only when Firebase Performance is enabled. If I filter out the AppDynamics collection URL as well, like this: Instrumentation.start( AgentConfiguration.builder() .withAppKey(BuildConfig.APPDYNAMICS_EUM_KEY) .withContext(applicationContext) .withLoggingEnabled(true) // set default INFO logging. Tagged "AppDynamics". .withExcludedUrlPatterns( setOf( "^https:\\/\\/firebaselogging\\-pa\\.googleapis\\.com.*\$", "^https:\\/\\/col.eum\\-appdynamics.com\\/eumcollector.*\$", ) ) then the high data usage stops.
... View more
