In order to evaluate the quality gates, we have to set up monitoring to provide the needed data.
Get your Dynatrace Tenant
Create a Dynatrace API Token
Log in to your Dynatrace tenant, and go to Settings > Integration > Dynatrace API. Then, create a new API Token with the following permissions:
Create a Dynatrace PaaS Token
In your Dynatrace tenant, go to Settings > Integration > Platform as a Service, and create a new PaaS Token.
Start the following script:
Execute the installation script:
When this script is finished, the Dynatrace OneAgent will be deployed in your cluster.
Note: To see the services running in your cluster, make sure to restart the pods they are running in.
Note 2: If the nodes in your cluster run on Container-Optimized OS (cos), make sure to follow the instructions for setting up the Dynatrace OneAgent Operator. This means that after the initial setup with
deployDynatrace.sh, which is a step below, the
cr.yml has to be edited and applied again. In addition, all pods have to be restarted.
Go to Jenkins at
http://jenkins.keptn.<EXTERNAL_IP>.xip.io/ and login with the credentials
AiTx4u8VyUV8tCKk or with the updated credentials you set after the installation. You can retrieve the external ip with the following command:
$ kubectl get svc istio-ingressgateway -n istio-system
Navigate to Jenkins > Manage Jenkins > Configure System, scroll to the environment variables and enter the Dynatrace tenant URL and Dynatrace API token.
Create a naming rule for process groups
Screenshot shows this rule definition.