This repository contains the hands on for the Day 2 Operations - Cloud Native Observability Workshop.


Lab Setup

The following steps are used for this lab:

What You'll Learn

In this exercise, we will deploy the OneAgent to a Linux instance running Kubernetes(Microk8s) and let the OneAgent discover what is running in that instance.

Using Terminal via Web Browser

To faciliate the labs, we will access the Linux instance via terminal through a web browser.

Use the URL was provided in your email to access the SSH terminal. Make sure the URL looks like Public IP Address:8080/wetty

Use the login name and password as provided in your email.


Download the OneAgent

Open your browser and access the Dynatrace URL.

Follow these steps below:


Within the Monitor Kubernetes / Openshift page, follow these steps below:



Connecting to (||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7310 (7.1K) [application/octet-stream]
Saving to: ‘'                      100%[=====================================================>]   7.14K  --.-KB/s    in 0s      

2021-06-01 05:46:36 (40.7 MB/s) - ‘' saved [7310/7310]

Check for token scopes...

Check if cluster already exists...

Creating Dynatrace namespace...

Applying Dynatrace Operator...
Warning: CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use CustomResourceDefinition created
serviceaccount/dynatrace-dynakube-oneagent created
serviceaccount/dynatrace-dynakube-oneagent-unprivileged created
serviceaccount/dynatrace-kubernetes-monitoring created
serviceaccount/dynatrace-operator created
serviceaccount/dynatrace-routing created
podsecuritypolicy.policy/dynatrace-dynakube-oneagent created
podsecuritypolicy.policy/dynatrace-dynakube-oneagent-unprivileged created
podsecuritypolicy.policy/dynatrace-kubernetes-monitoring created
podsecuritypolicy.policy/dynatrace-operator created
podsecuritypolicy.policy/dynatrace-routing created created created created created created created created created created created created created created created
deployment.apps/dynatrace-operator created
W0601 05:46:39.025776   29593 helpers.go:553] --dry-run is deprecated and can be replaced with --dry-run=client.
secret/dynakube configured

Applying DynaKube CustomResource... created

Adding cluster to Dynatrace...
Kubernetes monitoring successfully setup.

Validate the installation in Deployment status

Click on Show deployment status to check the status of the connected host.

You should be able to see a connected host as per the image below.


Restart Sockshop application

To restart the sample app Sockshop execute the following command:

kubectl delete po --all -n dev
kubectl delete po --all -n production

Explore the Sockshop Application

Within Dynatrace, follow the steps below to get Sockshop URL:

Explore the Smartscape

While waiting for Easy Travel to start, you can explore Dynatrace and using the Smartscape, Dynatrace will automatically discover the processes and dependencies that comprises the Easy Travel application!

4 things that you will love about Dynatrace!


In this exercise, we will automate configuration of Dynatrace environment.

Using Dynatrace Monitoring as Code (Monaco), you can automate the configuration of all global Dynatrace environments without human intervention. Various use cases include:

To faciliate the session, you can run the monaco code with the below:

cd sockshop

After setting it up, configure the DT_TENANT and DT_API_TOKEN and DT_DASHBOARD_OWNER variables. These can be found within the lab registration email.

export DT_TENANT=<ENV>
export DT_API_TOKEN=dt0c01.IH6********************************************
export DT_DASHBOARD_OWNER=<your email address>

After setting up, run the following command to configure Dynatrace:


Below are the configurations done:

In this exercise, we will cover the setting up basic Service Level Objectives (SLO). These objectives are based on a target of our measured Service Level Indicators (SLI) to fulfill the business's Service Level Agreement (SLA).

Creating SLO

On the left nav, go to Service level objectives > Add new SLO

We will be creating a SLO for Sockshop Frontend. Use the following:


In this exercise, we will cover the setting up an advance Service Level Objectives (SLO). These objectives would require creating a custom metric first, followed by targeting the measured Service Level Indicators (SLI) to fulfill the business's Service Level Agreement (SLA).

Creating metrics for Catalogue page

Next, we will be creating a custom metric for successful requests count to Catalogue page



Creating SLO for Catalogue Availability


Refer to the left navigation bar and go to Dashboards. Dynatrace has now prebuilt dashboard templates such as Kubernetes Dashboards and Real User Monitoring dashboards.

As part of the Monaco rollout, you should also see dashboards created such as Environment Overview Dashboard and Prometheus - Environment Overview Dashboard


Drill down into each of these dashboards and explore the various dashboard widgets for App Owners and Business Users.


Adding a SLO widget

We will now add a new SLO widget based on the new SLO we've created.

On the left nav, go to Service level objectives

You can use the pin icon to pin the dashboard to Environment Overview Dashboard


Adding a custom metric widget

Within the Environment Overview Dashboard dashboard, click on Edit

Drag the Custom Chart widget onto the dashboard and click on configure custom chart


Adding a custom metric widget with CODE

Back at the dashboard view, click on the newly created widget to clone another custom chart

On the new widget, click on configure custom chart

Back in the Data Explorer view, following the below:


Dynatrace also offers a built-in release-analysis solution that helps you determine the versions or stages of your deployed applications.

On the left nav, go to Releases


This provides an overview of deployed component versions and their release events.

Drilling into each component, you will find additional metadata from the respective component. This provides context to the monitored component as well as information regarding it's lifecycle and tracking issues.


We hope you enjoyed this lab and found it useful. We would love your feedback!

How was your overall experience with this lab?

Excellent Good Average Fair Poor

What did you benefit most from this lab?

Deploy OneAgent to a Kubernetes GitOps / Monitoring as code approach Service Level Objectives Releases

How likely are you to recommend this lab to a friend or colleague?

Very Likely Moderately Likely Neither Likely nor unlikely Moderately Unlikely Very Unlikely