Solved: Configuration of Dynatrace Managed for easyTravel application

kohei-saito · ‎11 Jan 2019

Hi,

I'm building a whole environment for testing of Dynatrace Managed.

The build of Managed Cluster itself finished successfully.

And then, I'm going to set up easyTravel as a demo application for test.

Now I have a trouble.

I don't know well how to modify configuration file of easyTravel.

According this page, after installation of easyTravel, I have to modify some configuration.

In the case of Linux, the configuration file is set at the following path:

/opt/easytravel-2.0.0-x64/resources/easyTravelConfig.properties

(note) Here, easyTravel is installed into /opt/

Then the above documentation tells us modifications as follows:

config.apmServerDefault = APM
 
config.apmServerHost=<managed_server_host>
config.apmServerWebPort=443
config.apmServerPort=8443
config.apmServerWebURL=https://<managed_server_host>:443
config.apmTenant=<environment_id>

If my Dynatrace Managed environment have such URL as https://abc123.dynatrace-managed.com/e/abcd1234-ef... what parameters do I need for configuration files?

I assume:

config.apmServerDefault = APM
 
config.apmServerHost=abc123.dynatrace-managed.com
config.apmServerWebPort=443
config.apmServerPort=8443
config.apmServerWebURL=https://abc123.dynatrace-managed.com:443
config.apmTenant=abcd1234-ef56-gh78-ijkl4321

Is this correct?

Regards,

Kohei

radek_jasinski · ‎11 Jan 2019

The configuration looks correct for Dynatrace Managed. Where you have the problem?:)

config.apmServerDefault = APM

config.apmServerHost=abc123.dynatrace-managed.com /Is this the host name of your machine where you have Dynatrace Managed?/

config.apmServerWebPort=443

config.apmServerPort=8443

config.apmServerWebURL=https://abc123.dynatrace-managed.com:443

config.apmTenant=abcd1234-ef56-gh78-ijkl4321

R.

Have a nice day!

kohei-saito · ‎15 Jan 2019

Hi @Radosław J.

Thanks for your comment! 🙂

>config.apmServerHost=abc123.dynatrace-managed.com
>Is this the host name of your machine where you have Dynatrace Managed?

Yes, it is. I confirmed ping to this hostname.

However, Dynatrace Managed monitoring of Applications and User sessions from auto-generated requests of easyTravel is not get started with this configuration.

In the first place, this might be a kind of basic question, but what is this configuration for?

Dynatrace started to monitor Services, Processes and Hosts even if I didn't modify this.

On the other hand, Applications and User sessions from auto-generated requests of easyTravel cannot be monitored if I don't modify this configuration file.
(That is, it seems that all of entities related with RUM cannot be monitored. In addition, actions from my browser can be monitored.)

In the case of Dynatrace SaaS, I can monitor Applications and User sessions even from auto-generated requests of easyTravel if I modify this configuration properly.

So I guess that I need this configuration for capture RUM data from auto-generated requests of easyTravel...

Could you tell me what should I do to monitor RUM data?

Thanks,

Kohei

kohei-saito · ‎15 Jan 2019

Hi,

after several tests, I found that it seems to be necessary to modify another property in this configuration file for getting RUM data.

That's the following:

- before(default)

# Which type of APM mode is chosen if we cannot determine the type automatically (i.e. if the APM server is down during startup)
# If at least one set of server properties above are correct, apmServerDefault is ignored and mode is chosen automatically.
# If settings for both servers are correct, APM mode is chosen in first place.                  # possible values are: Classic (=AppMon), APM (=Dynatrace)
# config.apmServerDefault=APM
config.apmServerDefault=Classic

- after(to be)

# Which type of APM mode is chosen if we cannot determine the type automatically (i.e. if the APM server is down during startup)
# If at least one set of server properties above are correct, apmServerDefault is ignored and mode is chosen automatically.
# If settings for both servers are correct, APM mode is chosen in first place.                  # possible values are: Classic (=AppMon), APM (=Dynatrace)
config.apmServerDefault=APM
# config.apmServerDefault=Classic

After changing the value of this property "config.apmServerDefault" into "APM", Dynatrace Managed got to capture RUM data.

I consider this property has something to do with RUM.

Kohei