Android Auto-Instrumentation: Is "Monitoring Server URL" required?
When using the Android Auto-Instrumentation, there is an input for "Monitoring Server URL". Customer is trying to auto-instrument from systems that are not connected to their dynatrace server. Is there any way around this?
Thanks in advance
Hi
This is the URL endpoint that will receive the monitored data. Typically you would install a web server (apache, IIS, ...) and install a dynatrace web server agent on it. Then use that URL for that web server to COLLECT the data. You obviously have to have a dynatrace agent and server somewhere as otherwise the data we capture ends up nowhere.
An alternative option is to look into our Dynatrace APM/UEM as a Service offering where we host dynatrace + a web server that can be used to retrieve that monitoring signal
Andi
Thanks for such a quick reply!
I understand. In this case the customer is having the external developers, that don't have access to the dt server, deliver the instrumented app, but I guess that is not a possibility. Provieded they can't go to APM as a Service, I guess this would not be an issue if they go with manual instrumentation. Correct?
It doesnt matter whether they do auto instrumentation or manual instrumentation. Instrumenting an App means that we are collecting data. The question is: WHERE to send the data to? Thats the endpoint. In both cases - manual and automated - they need to figure out WHERE to send this data to. It has to be a Web Server with a Dynatrace Web Server Agent installed.
Does this make sense? The external devs can still use the auto-instrumentor but you need to tell them where this data gets send to.
If I understand correctly, the auto-instrumentation wizard doesn't let you progress unless you supply a valid Dynatrace Server that it can test. There button for "Get Started" only works after the URL is tested. They know what that is but the developers can't access it. That is why if you do it manually I was guessing it would be OK as it wouldn't get tested.
Hi Francisco,
I get your point. The autoinstumentation is that restrictive because most of the issues related to mobile were due to invalid URLs to the endpoints. If you use the command line autoinstrumentor you can specify whatever URL you want but be aware that the agent after app startup checks whether the URL is valid or not. If the URL is not valid it will stop collecting data.
Cheers Klaus
Thank you Andreas and Klaus!
