End User Monitoring (EUM)

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I provide different account keys for different flavors?

SOLVED
Highlighted
Producer

Hi we have an Android setup where we distinguish between production and test builds through the use of Android  Flavors. We also have two separate accounts at AppDynamics for Production and Test. How can I provide different set of credentials when everything seems to be done at compile time in a single build.gradle config setting like below?

 

adeum {
    account {
        name 'ourAccount'
        licenseKey '11111111-1111-1111-111111111111'
    }
}

Is it possible to set the credentials runtime instead?

Or parameterize this somehow dependent on flavors? Something like

 

adeum {
    account("test") {
        name 'ourTestAccount'
        licenseKey '11111111-1111-1111-111111111111'
    }
}
adeum {
    account("prod") {
        name 'ourProdAccount'
        licenseKey '22222222-2222-2222-222222222222'
    }
}
How can I provide different account keys for different flavors?
1 REPLY 1
Producer

I might have misunderstood how accounts relate to environments in AppDynamics. Seems you can use the same account for multiple environments? With "environment" I mean whatever domain name comes in front of "*.saas.appdynamics.com". If this is correct then merely swapping App Key in 

 

Instrumentation.start(AgentConfiguration.builder()
.withAppKey(environmentSpecificKey))

..would do the trick - reusing the same "adeum" section in build.gradle for both