Do you want to learn Dynatrace for free, without paid courses or endless videos? This guide offers a four-week plan built only from span.observer courses: concepts, platform, metrics and DQL, then SLOs and automation. Each week points to specific modules, with the duration their author gives.
The plan is for operations engineers, SREs, developers and administrators who want to learn Dynatrace on their own, at their own pace. It also works as a Dynatrace tutorial for beginners: no prior knowledge of the product is needed. Only one choice matters: Dynatrace Managed or Dynatrace SaaS. The two branches are never mixed.
“Free” here means the blog content: lessons, exercises and corrected quizzes, with no sign-up. For the overview of the training offer, see also the free Dynatrace training page.
Learn Dynatrace for free with a 4-week plan
| Week | Goal | Managed | SaaS |
|---|---|---|---|
| 1 | Observability concepts | Free observability training | |
| 2 | The platform | Managed course | SaaS course |
| 3 | Metrics and DQL | Managed metrics | SaaS metrics |
| 4 | SLOs and automation | SLO and SLA course, then Monaco or Terraform | |
The durations below are estimates by the course authors, not official figures. Plan a few hours a week, spread as you like.
What you need to practise in a Dynatrace test environment
A Dynatrace test environment keeps you away from production. Here is what I could read on the official pages.
- SaaS free trial. The documentation page Get started offers a free 15-day trial. It describes three steps: create an account, install OneAgent on a host, explore the features. It does not mention Managed.
- Playground. The same page describes a pre-configured sandbox with sample data, with no installation or data ingestion.
- Dynatrace University. The Education Services page mentions training and a certification programme. It does not say whether courses are free or paid.
I could not verify the access conditions of the Dynatrace University catalogue (the page did not render without JavaScript), nor whether a trial exists for Managed. For Managed, the blog courses advise a staging environment and, ideally, an evaluation licence from the vendor or a partner.
Week 1: concepts before tools
Start by understanding what you observe. The article observability vs monitoring sets out the definitions. The free observability training then links them to traces, spans, metrics and logs, without ever confusing them.
Goal for the end of the week: explain the difference between a trace, a span, a metric and a log, with an example from your own system.
Week 2: the platform, Managed or SaaS
Pick the branch that matches your environment and stay on it.
If you work on Managed
The Dynatrace Managed course has 8 modules, from installing a test cluster to API automation. It states about 6 hours of reading and exercises.
If you work on SaaS
The Dynatrace SaaS course also has 8 modules: Grail, collection, DQL, Notebooks, logs and Workflows. It states about 7.5 to 8 hours, exercises included.
Week 3: metrics and DQL
Metrics are the basis of alerts and SLOs. Again, two separate courses of 7 modules.
- Managed: the Managed metrics course covers
builtin:keys, the metric selector and the Metrics v2 API, in about 5 hours. - SaaS: the SaaS metrics course covers Grail
dt.*keys and the DQLtimeseriescommand, in about 2 hours.
Goal for the end of the week: write a query that counts a service’s errors per minute.
Week 4: SLOs and automation
Start with the SLO and SLA course (6 modules, about 3.5 hours). It turns your metrics into objectives and an error budget. Then pick a configuration-as-code course for your platform.
| Tool | Managed | SaaS |
|---|---|---|
| Monaco (5 modules) | Monaco Managed, 2.5 to 5 hours | Monaco SaaS, about 4 hours |
| Terraform (3 modules) | Terraform Managed, about 2 h 15 | Terraform SaaS, about 2 h 20 |
You do not need both tools: take the one your team already uses. The reliability benefit is concrete: reviewed, versioned configuration reduces toil and the risk of an incident caused by an untracked change.
Use the same rhythm every week: read the lesson, run the exercise in your test environment, then take the quiz. If a module takes longer than planned, extend the plan rather than skipping the exercise, because practice is what makes the vocabulary stick.
Best practices for learning on your own
- One module per session: lesson, exercise, quiz. Note your wrong answers.
- Always work in a test environment, never in production.
- Each week, apply what you learn to a service you know.
- Keep the official documentation open to check function names and token scopes.
Frequently asked questions
Can you learn Dynatrace for free?
Yes, with the blog courses: every module is freely accessible. To practise, the official documentation describes a free 15-day SaaS trial and a Playground. The access conditions of Dynatrace University could not be verified.
How long does it take to learn Dynatrace?
Based on the durations the modules state, expect about 15 to 20 hours for weeks 2 to 4: roughly 17 to 19.5 hours on Managed and 15 h 20 to 17.5 hours on SaaS, depending on the week 4 tool. Week 1 comes on top, with no stated duration. These figures are estimates, not official durations.
Do you need a certification?
No, nothing requires it to follow this plan. These courses do not award a certification. The Dynatrace Education Services page presents an official certification programme; check it for its conditions.
How can you learn Dynatrace alone without an environment?
Start with the official Playground to explore sample data. Move to a SaaS trial when you want to install OneAgent and do the exercises.
Conclusion
To learn Dynatrace for free, go in order: concepts, platform, metrics, then reliability and automation. Choose Managed or SaaS in week 2 and keep that choice to the end. One module per session is enough to keep the pace.
span.observer is an independent community blog, not affiliated with Dynatrace LLC. This plan does not replace the official training and certifications of Dynatrace University. Check the free trial conditions and features in the official documentation for your version.