Troubleshoot OneAgent deployment issues on Cloud Foundry

Find out how to troubleshoot the possible issues you might encounter when deploying OneAgent on Cloud Foundry and how to access the OneAgent log files.

OneAgent deployment issues on Cloud Foundry for application-only monitoring

The Dynatrace integration for the Node.js buildpack allows you to successfully push your application even when the download of Dynatrace OneAgent fails (for example, because of a network connection error). You can configure OneAgent error handling via the option skiperrors that you can specify in the payload of the user-provided Dynatrace Cloud Foundry service that’s bound to your application:

shell
cf cups dynatrace-service -p "environmentid, apitoken, skiperrors"

You’re prompted automatically to provide your environment ID, API token, and either true or false for the skiperrors flag. Note that, by default, an unsuccessful download of Dynatrace OneAgent will result in a deployment error.

Log files

You can troubleshoot issues regarding OneAgent deployment on Cloud Foundry by examining the logs. Depending on your deployment strategy, these are located at the following paths:

OneAgent BOSH log files

You can access the installed OneAgent log files at /var/vcap/data/dynatrace/oneagent/log, /var/vcap/sys/log/dynatrace, or at the default path /opt/dynatrace/oneagent, which is a symlink to /var/vcap/data/dynatrace/oneagent/log.

Note: You need root permission to access the /var/vcap/data/dynatrace directory.

OneAgent for application-only monitoring log files

For the Java buildpack, you can access the log files at <path-to-app-container>/.java-buildpack/dynatrace_one_agent/log.
For the Node.js, Staticfile, PHP buildpacks, as well as the NPM module, you can access the log files at <path-to-app-container>/dynatrace/oneagent/log.

Note: In order to stream logs, run the following command.

plaintext
cf logs app-name