In order to evaluate the quality gates and allow self-healing in production, we have to set up monitoring to provide the needed data.
Bring your Dynatrace SaaS or Dynatrace-managed 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.
Clone the install repository and setup your credentials by executing the following steps:
git clone --branch 0.2.0 https://github.com/keptn/dynatrace-service --single-branch cd dynatrace-service/deploy/scripts ./defineDynatraceCredentials.sh
When the script asks for your Dynatrace tenant, please enter your tenant according to the appropriate pattern:
Execute the installation script for your platform:
When this script is finished, the Dynatrace OneAgent and the dynatrace-service are deployed in your cluster. Execute the following command to verify the deployment of the dynatrace-service.
kubectl get svc dynatrace-service -n keptn
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE dynatrace-service ClusterIP 10.0.44.191 <none> 8080/TCP 2m48s
Note 1: To monitor the services that are already onboarded in the
production namespace, make sure to restart the pods. If you defined different environments in your shipyard file, please adjust the values accordingly.
kubectl delete pods --all --namespace=sockshop-dev kubectl delete pods --all --namespace=sockshop-staging kubectl delete pods --all --namespace=sockshop-production
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.
In your Dynatrace tenant, when you navigate to Settings > Tags > Automatically applied tags you will find two entries:
This means that Dynatrace will automatially apply tags on your onboarded services.
In addition, a Problem Notification has automatically been set up to inform your keptn installation of any problems with your services to allow auto-remediation. This will be described in more detail in the runbook automation and self-healing use case. You can check the problem notification by navigating to Settings > Integration > Problem notifications and you will find a keptn remediation problem notification.
The Dynatrace service will take care of pushing events of the keptn workflow to the artifacts that have been onboarded with keptn. For example, the deployment as well as custom infos like starting and finishing of tests will appear in the details screen of your services in your Dynatrace tenant.
Create a naming rule for process groups
Screenshot shows this rule definition.
If you want to uninstall Dynatrace, there are scripts provided to do so. Uninstalling keptn will not automatically uninstall Dynatrace.
git clone --branch 0.2.0 https://github.com/keptn/dynatrace-service --single-branch
cd dynatrace-service/deploy/scripts ./uninstallDynatrace.sh