Installing and Configuring Dynatrace Full-Stack Add-on for PCF

Create the Dynatrace Manifest
Download and Deploy the Dynatrace Full-Stack Add-on for PCF

This topic explains how to install and configure the Dynatrace Full-Stack Add-on for Pivotal Cloud Foundry (PCF).

Create the Dynatrace Manifest

Follow these steps to create the Dynatrace manifest for your deployment:

Create a Dynatrace manifest file called runtime-config-dynatrace.yml, using the code below as a template to get started.

releases:
- {name: dynatrace-oneagent, version: 0.3.4}

addons:
- name: dynatrace-oneagent-addon
  jobs:
  - name: dynatrace-oneagent
    release: dynatrace-oneagent
  include:
    stemcell:
    - os: ubuntu-trusty
  exclude:
    jobs:
    - {name: smoke-tests, release: cf}
    - {name: push-apps-manager, release: push-apps-manager-release}
    - {name: deploy-notifications, release: notifications}
    - {name: deploy-notifications-ui, release: notifications-ui}
    - {name: push-pivotal-account, release: pivotal-account}
    - {name: deploy-autoscaling, release: cf-autoscaling}
    - {name: register-broker, release: cf-autoscaling}
    - {name: nfsbrokerpush, release: nfs-volume}
    - {name: bootstrap, release: cf-mysql}
    - {name: rejoin-unsafe, release: cf-mysql}
    - {name: broker-registrar, release: cf-mysql}
    - {name: deregister-and-purge-instances, release: cf-mysql}
    - {name: smoke-tests, release: cf-mysql}
    - {name: install-hwc-buildpack, release: hwc-buildpack}
  properties:
    dynatrace:
      environmentid: <environmentid>
      apitoken: <token>
      apiurl: https://{your-managed-cluster.com}/e/{environmentid}/api
#optional: extra addon configuration for Windows cells
- name: dynatrace-oneagent-windows-addon
  jobs:
  - name: dynatrace-oneagent-windows
    release: dynatrace-oneagent
  include:
    stemcell:
    - os: windows2012R2
  properties:
    dynatrace:
      environmentid: <environmentid>
      apitoken: <token>
      apiurl: https://{your-managed-cluster.com}/e/{environmentid}/api

Replace the values listed in the template as follows:
- releases: - version: Specify the version number of your Dynatrace Full-Stack Add-on for PCF download from Pivotal Network.
- jobs: - name: Do not change the name of this job. It must be dynatrace-oneagent for Linux VMs.
- include: stemcell - os: Do not change the OS type.
- environmentid: Replace with your Dynatrace environment ID.
- apitoken: Replace with your PaaS token from the Dynatrace UI.
- apiurl: Replace with your Dynatrace Managed URL, including the environment ID. An example URL might look like the following https://{your-managed-cluster.com}/e/{environmentid}/api
Optional: The add-on supports additional configuration properties:
- sslmode: Set to all if you want to accept all self-signed SSL certificates.
- downloadurl Specify a direct download URL for Dynatrace OneAgent. If this propery is set, BOSH will download OneAgent from this location.
- proxy: Specify the proxy to be used for communication.
If you also want to deploy Dynatrace to Windows Diego cells, please configure a second add-on section for the dynatrace-oneagent-windows job. The properties for environmentid, apitoken, and apiurl remain the same as with the normal Linux configuration.
- jobs: - name: For Windows cells this must be dynatrace-oneagent-windows.
- include: stemcell - os: For Windows cells this must be windows2012R2.

Note: To modify the configuration of an existing deployment, you must update the manifest file and redeploy.

Download and Deploy the Dynatrace Full-Stack Add-on for PCF

After deploying Ops Manager, perform the following steps to download and deploy the Dynatrace Full-Stack Add-on for PCF:

Download the Dynatrace Full-Stack Add-on for PCF software binary from the Pivotal Network to your local machine.

Copy the software binary to your Ops Manager instance.

$ scp -i PATH/TO/PRIVATE/KEY dynatrace-release.tar.gz ubuntu@YOUR-OPS-MANAGER-VM-IP:

Copy the Dynatrace manifest file to your Ops Manager instance.

$ scp -i PATH/TO/PRIVATE/KEY runtime-config-dynatrace.yml ubuntu@YOUR-OPS-MANAGER-VM-IP:

SSH into Ops Manager.

$ ssh -i PATH-TO-PRIVATE-KEY ubuntu@YOUR-OPS-MANAGER-VM-IP

On the Ops Manager VM, navigate to the software binary location in your working directory.
```
$ cd PATH-TO-BINARY
```
Log in to the BOSH director.
- For Ops Manager v1.10 or earlier:
  1. On the Ops Manager VM, target the internal IP address of your BOSH Director. When prompted, enter your BOSH Director credentials. To retrieve your BOSH Director credentials, navigate to Ops Manager, click the Credentials tab, and click Link to Credential next to Director Credentials.
```
$ bosh --ca-cert /var/tempest/workspaces/default/root_ca_certificate target YOUR-BOSH-DIRECTOR-INTERNAL-IP
Target set to 'p-bosh'
Your username: director
Enter password: ******************
Logged in as 'director'
```
- For Ops Manager v.1.11 or later:
  1. On the Ops Manager VM, create an alias in the BOSH CLI for your BOSH Director IP address. For example:
```
$ bosh2 alias-env my-env -e 10.0.16.10
```
  2. Log in to the BOSH Director, specifying the newly created alias. For example:
```
$ bosh2 -e my-env log-in
```

Upload your release.

For Ops Manager v1.10 or earlier:

$ bosh upload release PATH-TO-BINARY/dynatrace-release.tar.gz

For Ops Manager v1.11 or later:

$ bosh2 -e my-env upload-release PATH-TO-BINARY/dynatrace-release.tar.gz

Optionally, from the command line, you can confirm that upload of the Dynatrace software binary is complete. You should see the Dynatrace binary file.
- For Ops Manager v1.10 or earlier:
```
$ bosh releases
```
- For Ops Manager v1.11 or later:
```
$ bosh2 -e my-env releases
```
Update your runtime configuration to include the Dynatrace Add-on for PCF.
Note: If you installed other BOSH add-ons, you must merge the Dynatrace manifest into your existing add-on manifest. Append the contents of runtime-config-dynatrace.yml to your existing add-on YML file.
- For Ops Manager v1.10 or earlier:
```
$ bosh update runtime-config PATH/runtime-config-dynatrace.yml
```
- For Ops Manager v1.11 or later:
```
$ bosh2 -e my-env update-runtime-config PATH/runtime-config-dynatrace.yml
```

Verify your runtime configuration changes match what you specified in the Dynatrace manifest file.

For Ops Manager v1.10 or earlier:
```
$ bosh runtime-config
```
For Ops Manager v1.11 or later:
```
$ bosh2 -e my-env runtime-config
```

For example:

Acting as user 'admin' on 'micro'

releases:
- {name: dynatrace-oneagent, version: 0.3.4}

addons:
- name: dynatrace-oneagent-addon
  jobs:
  - name: dynatrace-oneagent
    release: dynatrace-oneagent
...

Navigate to your Installation Dashboard in Ops Manager.
Click Apply Changes.

Create a pull request or raise an issue on the source for this page in GitHub