How do I customize a mobile agent's collector endpoint to use the North America, Europe and APAC EUM SAAS Cloud?

[#1]

If you are using one of our SAAS EUM Clouds in North America, Europe, and APAC region, below are the instrumentation customizations required to set the collector and config endpoint.

• North America
• Europe
• APAC

North America

Android

Instrumentation.start(AgentConfiguration.builder()
      .withAppKey("<EUM_APP_KEY>")
      .withCollectorURL("https://mobile.eum-appdynamics.com:443") // The URL of the EUM Server(on-prem)
      .build());

iOS

[Objective C]

ADEumAgentConfiguration *adeumAgentConfig = [[ADEumAgentConfiguration alloc] initWithAppKey:<#EUM_APP_KEY#>];
// Set the Collector URL and Screenshot Service URL to the EUM Server URL.
adeumAgentConfig.collectorURL = "https://mobile.eum-appdynamics.com:443";
adeumAgentConfig.screenshotURL = adeumAgentConfig.collectorURL;
[ADEumInstrumentation initWithConfiguration:adeumAgentConfig];

[Swift]

let configuration = ADEumAgentConfiguration(appKey: <#EUM_APP_KEY#>)
// Set the Collector URL and Screenshot Service URL to the EUM Server URL.
configuration.collectorURL = "https://mobile.eum-appdynamics.com:443"
configuration.screenshotUrl =  configuration.collectorURL
ADEumInstrumentation.initWith(configuration)

Note: The default endpoint for iOS and the Android agent is still https://mobile.eum-appdynamics.com:443, so even if this is not explicitly set, the agent will send data to the North America EUM Cloud.

Europe

Android 

Instrumentation.start(AgentConfiguration.builder()
      .withAppKey("<EUM_APP_KEY>")
      .withCollectorURL("https://fra-col.eum-appdynamics.com:443") // The URL of the EUM Server(on-prem)
      .build());

iOS

[Objective C]

ADEumAgentConfiguration *adeumAgentConfig = [[ADEumAgentConfiguration alloc] initWithAppKey:<#EUM_APP_KEY#>];
// Set the Collector URL and Screenshot Service URL to the EUM Server URL.
adeumAgentConfig.collectorURL = "https://fra-col.eum-appdynamics.com:443";
adeumAgentConfig.screenshotURL = adeumAgentConfig.collectorURL;
[ADEumInstrumentation initWithConfiguration:adeumAgentConfig];

[Swift]

let configuration = ADEumAgentConfiguration(appKey: <#EUM_APP_KEY#>)
// Set the Collector URL and Screenshot Service URL to the EUM Server URL.
configuration.collectorURL = "https://fra-col.eum-appdynamics.com:443"
configuration.screenshotUrl =  configuration.collectorURL
ADEumInstrumentation.initWith(configuration)

APAC

Android

Instrumentation.start(AgentConfiguration.builder()
      .withAppKey("<EUM_APP_KEY>")
      .withCollectorURL("https://syd-col.eum-appdynamics.com:443") // The URL of the EUM Server(on-prem)
      .build());

iOS

[Objective C]

ADEumAgentConfiguration *adeumAgentConfig = [[ADEumAgentConfiguration alloc] initWithAppKey:<#EUM_APP_KEY#>];
// Set the Collector URL and Screenshot Service URL to the EUM Server URL.
adeumAgentConfig.collectorURL = "https://syd-col.eum-appdynamics.com:443";
adeumAgentConfig.screenshotURL = adeumAgentConfig.collectorURL;
[ADEumInstrumentation initWithConfiguration:adeumAgentConfig];

[Swift] 

let configuration = ADEumAgentConfiguration(appKey: <#EUM_APP_KEY#>)
// Set the Collector URL and Screenshot Service URL to the EUM Server URL.
configuration.collectorURL = "https://syd-col.eum-appdynamics.com:443"
configuration.screenshotUrl =  configuration.collectorURL
ADEumInstrumentation.initWith(configuration)

[vidyasagar_ell1]

Just wondering there are still few hiccups while showing details for custom data, custom timers, info points, and bread crumbs on AppD console after applying the above coding standards to mobile IOS application. Please advise if it's still needed any further custom instrumentation.