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.2 https://github.com/keptn/installer --single-branch cd installer/scripts ./defineDynatraceCredentials.sh
When the script asks for your Dynatrace tenant, please enter your tenant according to the appropriate pattern:
Execute the installation script
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 ksvc dynatrace-service -n keptn
NAME DOMAIN LATESTCREATED LATESTREADY READY dynatrace-service dynatrace-service.keptn.svc.cluster.local dynatrace-service-26sm4 dynatrace-service-26sm4 True
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.
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.
Due to a change of the data stored in the
dynatrace secret in the
keptn namespace, it is necessary to update the secret according to the following steps:
1. Prepare the Dynatrace URI:
- Dynatrace SaaS tenant:
- Dynatrace-managed tenant:
1. Update the property
DT_TENANT based on the Dynatrace URI. Please note that the value has to be base64 encoded.
kubectl edit secret dynatrace -n keptn
Create a naming rule for process groups
Screenshot shows this rule definition.