Hi,
Congrats on your Associate cert — and the fastest way to gain real Dynatrace implementation/admin experience is to install a demo app and practice on real telemetry.
1) Install a demo app: EasyTravel (or better for Kubernetes: EasyTrade)
EasyTravel is the classic Dynatrace demo app and is great for learning APM/RUM basics.
Community thread (Kubernetes):
https://community.dynatrace.com/t5/Cloud-platforms/EasyTravel-installation-on-Kubernetes/m-p/235465
EasyTrade is usually better suited for Docker/Kubernetes because it was designed for container deployments from the start (less friction, more learning).
GitHub repo:
https://github.com/Dynatrace/easytrade
Also useful: “Download and Set Up Dynatrace Demo Application” (Community):
https://community.dynatrace.com/t5/Start-with-Dynatrace/Download-and-Set-Up-Dynatrace-Demo-Applicati...
Learning path:
1. Install OneAgent / Dynatrace Operator (K8s) and validate:
- hosts / k8s nodes are visible
- processes / services are detected
- Smartscape shows real dependencies
2. Get comfortable navigating and filtering:
- Infrastructure → Hosts / Kubernetes
- Services → top services / errors / response time
3. Tagging → Management Zones → clean structure
Set host metadata (e.g., env=lab, owner=you, app=easytrade)
- Create rule-based tags from metadata (auto-tagging rules)
- Build a Management Zone (MZ) based on tags: e.g., “LAB-EasyTrade”
Confirm that:
- views and dashboards can be scoped to the MZ
- an alerting profile can target only that MZ
If u want, you can study entity selectors, eg in kubernetes. Is advance but really good practise. Eg.
type("CONTAINER_GROUP_INSTANCE"),fromRelationships.isCgiOfCa(type("CLOUD_APPLICATION"),toRelationships.isNamespaceOfCa(type("CLOUD_APPLICATION_NAMESPACE"),entityname.in("kubernetes_namespace")))"
4. APM/RUM — core configuration
- Split and identify the frontend (web application detection):
- application naming, domains, detection rules
- Configure user action naming and define key actions:
- e.g., “Search”, “Add to cart”, “Checkout”
- Improve service and process naming:
- service naming rules
- process group naming rules to make everything readable
5. Dashboards + alerting (what you’ll use in real ops)
- Build one “Operations” dashboard for EasyTrade/EasyTravel:
- availability / error rate / response time
- top failing services
- frontend experience (Apdex / load / JS errors)
6. Configure alerting + notifications:
- separate alerting profile scoped to “LAB-EasyTrade” MZ
- at least 2 problem types (e.g., availability + error rate)
7. Next level
DQL: write 3 queries for errors, latency, top endpoints and filter only for one service
Define an SLO for a key user journey (e.g., checkout) + monitor burn rate
Create an Automation / Workflow: notify (Slack/Teams/email) with context
I’d also recommend leveraging Dynatrace’s official learning resources and community events to accelerate your progress:
- Dynatrace University: follow the learning paths
- Training enablement sessions: great for hands-on walkthroughs, best practices, and Q&A with instructors.
- Dynatrace events & webinars : useful to see real-world use cases, new features, and common implementation patterns.
