{"id":75233,"date":"2026-04-25T00:54:52","date_gmt":"2026-04-25T00:54:52","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=75233"},"modified":"2026-04-25T00:54:52","modified_gmt":"2026-04-25T00:54:52","slug":"dynatrace-implementation-professional-certification-master-guide","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/dynatrace-implementation-professional-certification-master-guide\/","title":{"rendered":"Dynatrace Implementation Professional Certification Master Guide"},"content":{"rendered":"\n<p><strong>Last verified:<\/strong> April 24, 2026<br><strong>Audience:<\/strong> Dynatrace implementers, observability engineers, SREs, platform engineers, consultants, delivery engineers, cloud\/Kubernetes engineers, and anyone preparing for Dynatrace Implementation Professional Certification.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">0. What this guide is<\/h2>\n\n\n\n<p>This is a one-stop master guide for <strong>Dynatrace Implementation Professional Certification<\/strong> preparation.<\/p>\n\n\n\n<p>It focuses on how to architect, plan, deploy, configure, validate, and hand over Dynatrace implementations across enterprise environments.<\/p>\n\n\n\n<p>This guide covers:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Implementation planning<\/li>\n\n\n\n<li>Architecture discovery<\/li>\n\n\n\n<li>OneAgent deployment<\/li>\n\n\n\n<li>ActiveGate design<\/li>\n\n\n\n<li>Network zones<\/li>\n\n\n\n<li>Kubernetes and Dynatrace Operator<\/li>\n\n\n\n<li>Cloud integrations<\/li>\n\n\n\n<li>OpenTelemetry and OTLP ingestion<\/li>\n\n\n\n<li>Log ingestion and OpenPipeline<\/li>\n\n\n\n<li>Data governance and retention<\/li>\n\n\n\n<li>RUM and Synthetic implementation<\/li>\n\n\n\n<li>Extensions and remote monitoring<\/li>\n\n\n\n<li>Tags, management zones, ownership, and rollout governance<\/li>\n\n\n\n<li>Validation, troubleshooting, and handover<\/li>\n\n\n\n<li>Hands-on labs, study plan, checklists, and practice questions<\/li>\n<\/ul>\n\n\n\n<p>This is not an exam dump. It is a professional implementation guide designed to help you pass the exam and perform real Dynatrace deployments confidently.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">1. Current certification snapshot<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">1.1 What the certification validates<\/h2>\n\n\n\n<p>The Dynatrace Implementation Professional Certification validates that an individual can implement Dynatrace to solve requirements and drive business value.<\/p>\n\n\n\n<p>An implementation professional should be able to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Architect a Dynatrace deployment.<\/li>\n\n\n\n<li>Plan the implementation approach.<\/li>\n\n\n\n<li>Select the correct deployment pattern.<\/li>\n\n\n\n<li>Deploy OneAgent across supported environments.<\/li>\n\n\n\n<li>Design and deploy ActiveGate where needed.<\/li>\n\n\n\n<li>Configure Kubernetes monitoring with Dynatrace Operator.<\/li>\n\n\n\n<li>Configure data ingestion for logs, metrics, traces, events, business events, and OpenTelemetry.<\/li>\n\n\n\n<li>Manage ingestion quality, routing, enrichment, masking, and cost control.<\/li>\n\n\n\n<li>Implement Real User Monitoring and Synthetic Monitoring.<\/li>\n\n\n\n<li>Connect cloud platforms and remote technologies.<\/li>\n\n\n\n<li>Validate that monitoring data appears correctly.<\/li>\n\n\n\n<li>Troubleshoot deployment and ingestion problems.<\/li>\n\n\n\n<li>Prepare the platform for operational handover.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">1.2 Publicly visible learning path status<\/h2>\n\n\n\n<p>The public Dynatrace University catalog shows:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Dynatrace Implementation Professional Certification Learning Plan<\/strong><\/li>\n\n\n\n<li><strong>9 courses<\/strong><\/li>\n\n\n\n<li><strong>4h 54m<\/strong> total public learning plan duration<\/li>\n<\/ul>\n\n\n\n<p>The public learning plan description says the certification validates that the candidate can <strong>architect, plan, and implement the Dynatrace platform and manage data ingestion for its components<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1.3 Exam-format verification checklist<\/h2>\n\n\n\n<p>Some exam details may require Dynatrace University login. Before booking, verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Current exam duration<\/li>\n\n\n\n<li>Question count<\/li>\n\n\n\n<li>Written\/practical split<\/li>\n\n\n\n<li>Whether practical tasks are included<\/li>\n\n\n\n<li>Whether the practical section is open book<\/li>\n\n\n\n<li>Passing score<\/li>\n\n\n\n<li>Retake waiting period<\/li>\n\n\n\n<li>Retake fee or voucher rules<\/li>\n\n\n\n<li>Proctoring provider<\/li>\n\n\n\n<li>Proctoring language<\/li>\n\n\n\n<li>Whether partner and customer versions differ<\/li>\n\n\n\n<li>Whether the exam focuses on latest Dynatrace, Dynatrace Classic, or both<\/li>\n\n\n\n<li>Whether Associate certification is prerequisite or only recommended<\/li>\n\n\n\n<li>Whether hands-on tasks require tenant access, screenshots, uploaded files, or entered answers<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">1.4 Recommended prerequisite knowledge<\/h2>\n\n\n\n<p>Before attempting Implementation Professional, you should already understand Associate-level Dynatrace concepts:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OneAgent<\/li>\n\n\n\n<li>ActiveGate<\/li>\n\n\n\n<li>Dynatrace Platform \/ Tenant<\/li>\n\n\n\n<li>Grail<\/li>\n\n\n\n<li>DQL<\/li>\n\n\n\n<li>OpenPipeline<\/li>\n\n\n\n<li>Smartscape<\/li>\n\n\n\n<li>PurePath \/ distributed tracing<\/li>\n\n\n\n<li>Davis \/ Dynatrace Intelligence<\/li>\n\n\n\n<li>Infrastructure Observability<\/li>\n\n\n\n<li>Application Observability<\/li>\n\n\n\n<li>Log Management and Analytics<\/li>\n\n\n\n<li>Digital Experience Monitoring<\/li>\n\n\n\n<li>Application Security basics<\/li>\n\n\n\n<li>Business Observability basics<\/li>\n\n\n\n<li>Dashboards, notebooks, alerts, and workflows<\/li>\n<\/ul>\n\n\n\n<p>You should also understand Administration Professional concepts at a practical level:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Users and groups<\/li>\n\n\n\n<li>IAM policies<\/li>\n\n\n\n<li>Tokens and OAuth clients<\/li>\n\n\n\n<li>Settings app<\/li>\n\n\n\n<li>Tags and management zones<\/li>\n\n\n\n<li>Segments and security context<\/li>\n\n\n\n<li>Buckets and retention<\/li>\n\n\n\n<li>Alerting profiles<\/li>\n\n\n\n<li>Maintenance windows<\/li>\n\n\n\n<li>Credential vault<\/li>\n\n\n\n<li>Subscription and cost governance<\/li>\n<\/ul>\n\n\n\n<p>Implementation Professional is less about pure administration and more about <strong>turning requirements into a working deployment<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">2. Implementation professional mental model<\/h1>\n\n\n\n<p>A Dynatrace implementation is not just installing agents. It is an end-to-end delivery lifecycle.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2.1 The implementation lifecycle<\/h2>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">Discover requirements\n  \u2193\nDesign architecture\n  \u2193\nPrepare tenant, access, network, and rollout plan\n  \u2193\nDeploy OneAgent, ActiveGate, Operator, integrations, and ingestion paths\n  \u2193\nConfigure tags, zones, data routing, logs, RUM, Synthetic, alerts, and dashboards\n  \u2193\nValidate telemetry, topology, traces, logs, user experience, and problems\n  \u2193\nOptimize data volume, cost, masking, and retention\n  \u2193\nTrain users and hand over to operations\n<\/code><\/span><\/pre>\n\n\n<h2 class=\"wp-block-heading\">2.2 The implementer\u2019s core questions<\/h2>\n\n\n\n<p>For every deployment, ask:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>What must be monitored?<\/strong><br>Hosts, services, Kubernetes, cloud resources, logs, traces, users, APIs, business events, AI workloads, databases, network devices, queues, serverless, or PaaS.<\/li>\n\n\n\n<li><strong>How will data be collected?<\/strong><br>OneAgent, ActiveGate, Dynatrace Operator, OpenTelemetry, APIs, extensions, cloud integrations, log modules, RUM JavaScript, Synthetic monitors.<\/li>\n\n\n\n<li><strong>How will data reach Dynatrace?<\/strong><br>Direct SaaS endpoint, ActiveGate, proxy, sealed-network route, network zones, Kubernetes ActiveGate, OTLP API, Dynatrace Collector.<\/li>\n\n\n\n<li><strong>How should data be organized?<\/strong><br>Tags, host groups, management zones, segments, security context, naming standards, cloud tags, Kubernetes labels, ownership metadata.<\/li>\n\n\n\n<li><strong>How should data be processed and retained?<\/strong><br>OpenPipeline, buckets, retention, masking, enrichment, routing, filtering, DQL processors, log processing, cost control.<\/li>\n\n\n\n<li><strong>How will success be validated?<\/strong><br>Deployment status, host\/service visibility, traces, logs, topology, RUM sessions, synthetic checks, cloud metrics, Kubernetes health, dashboards, problems.<\/li>\n\n\n\n<li><strong>How will the customer operate it?<\/strong><br>Handover documents, dashboards, alerting profiles, workflows, runbooks, ownership tags, training, support model.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">3. Implementation discovery and requirements gathering<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">3.1 Discovery goals<\/h2>\n\n\n\n<p>Before deployment, collect enough information to design the right architecture.<\/p>\n\n\n\n<p>You need to understand:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Business goals<\/li>\n\n\n\n<li>Technical scope<\/li>\n\n\n\n<li>Application architecture<\/li>\n\n\n\n<li>Infrastructure footprint<\/li>\n\n\n\n<li>Cloud and Kubernetes platforms<\/li>\n\n\n\n<li>Network restrictions<\/li>\n\n\n\n<li>Security\/privacy requirements<\/li>\n\n\n\n<li>Identity\/access model<\/li>\n\n\n\n<li>Log and telemetry volume<\/li>\n\n\n\n<li>Retention requirements<\/li>\n\n\n\n<li>Alerting and incident-management tools<\/li>\n\n\n\n<li>Ownership model<\/li>\n\n\n\n<li>Success criteria<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">3.2 Business discovery questions<\/h2>\n\n\n\n<p>Ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What business services are most critical?<\/li>\n\n\n\n<li>What user journeys matter most?<\/li>\n\n\n\n<li>Which applications generate revenue?<\/li>\n\n\n\n<li>Which incidents cause the most pain today?<\/li>\n\n\n\n<li>What are the top monitoring gaps?<\/li>\n\n\n\n<li>Which teams will use Dynatrace?<\/li>\n\n\n\n<li>What dashboards or reports are expected?<\/li>\n\n\n\n<li>What business KPIs should be connected to telemetry?<\/li>\n\n\n\n<li>What is the desired operational outcome?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">3.3 Technical discovery questions<\/h2>\n\n\n\n<p>Ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How many hosts, VMs, containers, and Kubernetes clusters are in scope?<\/li>\n\n\n\n<li>Which operating systems are used?<\/li>\n\n\n\n<li>Which runtimes are used? Java, .NET, Node.js, Python, Go, PHP, Ruby, Apache, NGINX, IIS, etc.<\/li>\n\n\n\n<li>Which databases, queues, caches, and external services are used?<\/li>\n\n\n\n<li>Which cloud providers are used?<\/li>\n\n\n\n<li>Is Kubernetes managed, self-managed, OpenShift, EKS, AKS, GKE, TKGI, or another platform?<\/li>\n\n\n\n<li>Are applications containerized, serverless, VM-based, or mixed?<\/li>\n\n\n\n<li>Is internet egress allowed from hosts?<\/li>\n\n\n\n<li>Are proxies required?<\/li>\n\n\n\n<li>Are there sealed networks or disconnected zones?<\/li>\n\n\n\n<li>Are there existing OpenTelemetry collectors or instrumented apps?<\/li>\n\n\n\n<li>Are logs currently collected elsewhere?<\/li>\n\n\n\n<li>Which incident-management tools are used?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">3.4 Security and privacy discovery questions<\/h2>\n\n\n\n<p>Ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What data is sensitive?<\/li>\n\n\n\n<li>Are URLs allowed to contain customer data?<\/li>\n\n\n\n<li>Are logs allowed to leave the environment?<\/li>\n\n\n\n<li>Should data be masked at capture or processing?<\/li>\n\n\n\n<li>Are passwords, tokens, account numbers, or PII present in logs or request attributes?<\/li>\n\n\n\n<li>What retention is required by policy?<\/li>\n\n\n\n<li>Which teams can query logs?<\/li>\n\n\n\n<li>Which teams can view session data?<\/li>\n\n\n\n<li>Is SSO required?<\/li>\n\n\n\n<li>Is SCIM required?<\/li>\n\n\n\n<li>Are service users or OAuth clients required for automation?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">3.5 Delivery planning questions<\/h2>\n\n\n\n<p>Ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What is the rollout order?<\/li>\n\n\n\n<li>Which environment will be first?<\/li>\n\n\n\n<li>What is the pilot scope?<\/li>\n\n\n\n<li>What is production rollout timing?<\/li>\n\n\n\n<li>Who approves firewall changes?<\/li>\n\n\n\n<li>Who owns Kubernetes manifests or Helm charts?<\/li>\n\n\n\n<li>Who owns CI\/CD changes?<\/li>\n\n\n\n<li>Who owns cloud IAM permissions?<\/li>\n\n\n\n<li>Who owns log volume approval?<\/li>\n\n\n\n<li>Who validates success?<\/li>\n\n\n\n<li>Who receives handover?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">3.6 Exam focus<\/h2>\n\n\n\n<p>Expect scenario questions where a requirement points to a deployment choice.<\/p>\n\n\n\n<p>Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Private network with no direct internet: use ActiveGate\/proxy design.<\/li>\n\n\n\n<li>Kubernetes cluster: use Dynatrace Operator and DynaKube.<\/li>\n\n\n\n<li>Only selected pods need monitoring: use application monitoring mode, namespace selectors, or annotations.<\/li>\n\n\n\n<li>Existing OpenTelemetry instrumentation: configure OTLP ingestion to Dynatrace SaaS, ActiveGate, or Collector.<\/li>\n\n\n\n<li>Sensitive logs: mask\/drop data through OneAgent and\/or OpenPipeline.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">4. Implementation architecture<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">4.1 Reference architecture<\/h2>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">Applications \/ Hosts \/ Kubernetes \/ Cloud \/ OpenTelemetry \/ Logs \/ APIs\n  \u2193\nOneAgent, Dynatrace Operator, RUM JS, Synthetic, Extensions, OTLP exporters, APIs\n  \u2193\nDirect SaaS endpoint OR ActiveGate OR proxy OR Dynatrace Collector\n  \u2193\nOpenPipeline \/ ingestion processing \/ enrichment \/ masking \/ routing\n  \u2193\nGrail buckets \/ metrics \/ traces \/ logs \/ events \/ business events\n  \u2193\nSmartscape topology + PurePath traces + Davis AI\n  \u2193\nApps, dashboards, notebooks, alerts, workflows, reports, integrations\n<\/code><\/span><\/pre>\n\n\n<h2 class=\"wp-block-heading\">4.2 Architecture deliverables<\/h2>\n\n\n\n<p>A good implementation design includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Environment list<\/li>\n\n\n\n<li>Scope list<\/li>\n\n\n\n<li>Deployment modes<\/li>\n\n\n\n<li>Network diagram<\/li>\n\n\n\n<li>ActiveGate design<\/li>\n\n\n\n<li>Network zone design<\/li>\n\n\n\n<li>Host group strategy<\/li>\n\n\n\n<li>Kubernetes mode selection<\/li>\n\n\n\n<li>Cloud integration design<\/li>\n\n\n\n<li>OpenTelemetry ingestion design<\/li>\n\n\n\n<li>Log ingestion and retention design<\/li>\n\n\n\n<li>Data privacy and masking design<\/li>\n\n\n\n<li>Tagging strategy<\/li>\n\n\n\n<li>Management zone \/ segment strategy<\/li>\n\n\n\n<li>Alert routing design<\/li>\n\n\n\n<li>Dashboard and reporting design<\/li>\n\n\n\n<li>Cost-control plan<\/li>\n\n\n\n<li>Rollout plan<\/li>\n\n\n\n<li>Validation checklist<\/li>\n\n\n\n<li>Handover plan<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">4.3 Design principle: collect close, route securely, process intentionally<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Collect close<\/strong>: install or instrument near the workload.<\/li>\n\n\n\n<li><strong>Route securely<\/strong>: use ActiveGate, network zones, proxies, or Collector when needed.<\/li>\n\n\n\n<li><strong>Process intentionally<\/strong>: use OpenPipeline, buckets, retention, and masking to keep data useful, safe, and cost-aware.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">5. OneAgent implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">5.1 What OneAgent does<\/h2>\n\n\n\n<p>OneAgent is responsible for collecting monitoring data in the monitored environment. A single OneAgent per host can collect relevant monitoring data even when hosts run containers, microservices, or cloud infrastructure.<\/p>\n\n\n\n<p>OneAgent discovers processes and automatically activates instrumentation for supported application stacks.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5.2 What OneAgent can monitor<\/h2>\n\n\n\n<p>OneAgent can contribute visibility for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Hosts<\/li>\n\n\n\n<li>Processes<\/li>\n\n\n\n<li>Process groups<\/li>\n\n\n\n<li>Services<\/li>\n\n\n\n<li>Applications<\/li>\n\n\n\n<li>Databases<\/li>\n\n\n\n<li>Network health<\/li>\n\n\n\n<li>Cloud instances<\/li>\n\n\n\n<li>Containers<\/li>\n\n\n\n<li>Kubernetes workloads<\/li>\n\n\n\n<li>Logs<\/li>\n\n\n\n<li>Distributed traces<\/li>\n\n\n\n<li>Code-level diagnostics<\/li>\n\n\n\n<li>User experience signals when auto-injection is possible<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5.3 OneAgent deployment targets<\/h2>\n\n\n\n<p>Common deployment targets:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Linux<\/li>\n\n\n\n<li>Windows<\/li>\n\n\n\n<li>AIX<\/li>\n\n\n\n<li>Solaris<\/li>\n\n\n\n<li>z\/OS<\/li>\n\n\n\n<li>Docker hosts<\/li>\n\n\n\n<li>Kubernetes nodes<\/li>\n\n\n\n<li>Cloud VMs<\/li>\n\n\n\n<li>On-prem VMs<\/li>\n\n\n\n<li>Bare-metal hosts<\/li>\n\n\n\n<li>PaaS\/container platforms, depending on support<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5.4 Deployment methods<\/h2>\n\n\n\n<p>Common methods:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Manual installer<\/li>\n\n\n\n<li>Shell script \/ command-line installer<\/li>\n\n\n\n<li>Windows installer<\/li>\n\n\n\n<li>Configuration management tools<\/li>\n\n\n\n<li>Golden images<\/li>\n\n\n\n<li>CI\/CD pipelines<\/li>\n\n\n\n<li>Kubernetes Operator<\/li>\n\n\n\n<li>Cloud automation<\/li>\n\n\n\n<li>Infrastructure-as-Code tools<\/li>\n\n\n\n<li>Enterprise software distribution tools<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5.5 OneAgent rollout strategy<\/h2>\n\n\n\n<p>Recommended rollout:<\/p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">Prepare tenant and access\n  \u2193\nPrepare host groups, network zones, and ActiveGates\n  \u2193\nDeploy to non-production pilot\n  \u2193\nValidate host, process, service, trace, and log data\n  \u2193\nTune privacy, exclusions, and data collection\n  \u2193\nDeploy to production pilot\n  \u2193\nValidate business-critical applications\n  \u2193\nRoll out in waves\n  \u2193\nMonitor health, cost, and user adoption\n<\/code><\/span><\/pre>\n\n\n<h2 class=\"wp-block-heading\">5.6 Host groups<\/h2>\n\n\n\n<p>Host groups categorize and manage hosts that share similar characteristics or purposes.<\/p>\n\n\n\n<p>Use host groups for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Environment scoping<\/li>\n\n\n\n<li>Application ownership<\/li>\n\n\n\n<li>Update policies<\/li>\n\n\n\n<li>Alerting thresholds<\/li>\n\n\n\n<li>Process group separation<\/li>\n\n\n\n<li>Service grouping<\/li>\n\n\n\n<li>Tagging rules<\/li>\n\n\n\n<li>Management zone rules<\/li>\n<\/ul>\n\n\n\n<p>Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>prod-payments<\/code><\/li>\n\n\n\n<li><code>prod-checkout<\/code><\/li>\n\n\n\n<li><code>nonprod-platform<\/code><\/li>\n\n\n\n<li><code>k8s-prod-us-east<\/code><\/li>\n\n\n\n<li><code>legacy-windows-prod<\/code><\/li>\n<\/ul>\n\n\n\n<p>Important behavior:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A host belongs to at most one host group.<\/li>\n\n\n\n<li>Host groups can be assigned during or after OneAgent installation.<\/li>\n\n\n\n<li>Host groups affect process group detection and service grouping.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5.7 Monitoring modes<\/h2>\n\n\n\n<p>Common OneAgent monitoring modes:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Full-stack monitoring<\/h3>\n\n\n\n<p>Provides deep infrastructure and application observability, including code modules and distributed tracing.<\/p>\n\n\n\n<p>Best for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Production applications<\/li>\n\n\n\n<li>Critical services<\/li>\n\n\n\n<li>Full root-cause analysis<\/li>\n\n\n\n<li>Application performance diagnosis<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Infrastructure monitoring<\/h3>\n\n\n\n<p>Focuses on host and infrastructure metrics with less deep application instrumentation.<\/p>\n\n\n\n<p>Best for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Systems where application-level instrumentation is not needed<\/li>\n\n\n\n<li>Lower-cost infrastructure visibility<\/li>\n\n\n\n<li>Initial discovery<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Discovery mode<\/h3>\n\n\n\n<p>Lightweight mode for discovering assets and essential metadata.<\/p>\n\n\n\n<p>Best for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Initial inventory<\/li>\n\n\n\n<li>Planning rollout<\/li>\n\n\n\n<li>Low-impact discovery<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Application-only \/ application monitoring patterns<\/h3>\n\n\n\n<p>Used in selected Kubernetes\/container scenarios where only specific applications should be instrumented.<\/p>\n\n\n\n<p>Best for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Selective pod\/workload monitoring<\/li>\n\n\n\n<li>Teams that do not own node-level monitoring<\/li>\n\n\n\n<li>Environments where only specific namespaces or workloads are in scope<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5.8 OneAgent parameters to understand conceptually<\/h2>\n\n\n\n<p>You do not need to memorize every installer flag, but know these concepts:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Environment\/tenant endpoint<\/li>\n\n\n\n<li>API token or installation token<\/li>\n\n\n\n<li>Host group<\/li>\n\n\n\n<li>Network zone<\/li>\n\n\n\n<li>Proxy<\/li>\n\n\n\n<li>Monitoring mode<\/li>\n\n\n\n<li>Tags\/properties<\/li>\n\n\n\n<li>Installation path<\/li>\n\n\n\n<li>Log path<\/li>\n\n\n\n<li>Auto-update behavior<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5.9 OneAgent validation checklist<\/h2>\n\n\n\n<p>After deployment, verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Host appears in Dynatrace.<\/li>\n\n\n\n<li>OneAgent health is OK.<\/li>\n\n\n\n<li>Host group is correct.<\/li>\n\n\n\n<li>Network zone is correct.<\/li>\n\n\n\n<li>Processes are discovered.<\/li>\n\n\n\n<li>Services are discovered.<\/li>\n\n\n\n<li>Code modules are injected where expected.<\/li>\n\n\n\n<li>Distributed traces appear.<\/li>\n\n\n\n<li>Logs appear if configured.<\/li>\n\n\n\n<li>Topology relationships are correct.<\/li>\n\n\n\n<li>Problems can be detected.<\/li>\n\n\n\n<li>No unexpected privacy-sensitive data appears.<\/li>\n\n\n\n<li>License\/consumption impact is acceptable.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">5.10 OneAgent troubleshooting<\/h2>\n\n\n\n<p>Common problems:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Host not visible<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Installer completed successfully<\/li>\n\n\n\n<li>Network connectivity<\/li>\n\n\n\n<li>Proxy settings<\/li>\n\n\n\n<li>ActiveGate reachability<\/li>\n\n\n\n<li>Environment ID\/API URL<\/li>\n\n\n\n<li>Token validity<\/li>\n\n\n\n<li>Firewall<\/li>\n\n\n\n<li>TLS\/certificate issues<\/li>\n\n\n\n<li>Host supported platform<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Processes visible but services not deeply monitored<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monitoring mode<\/li>\n\n\n\n<li>Supported technology\/version<\/li>\n\n\n\n<li>Code module injection<\/li>\n\n\n\n<li>Process restart requirement<\/li>\n\n\n\n<li>Deep monitoring settings<\/li>\n\n\n\n<li>Container\/Kubernetes injection rules<\/li>\n\n\n\n<li>Unsupported runtime or static binary limitations<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">OneAgent connects to wrong ActiveGate<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Network zone assignment<\/li>\n\n\n\n<li>ActiveGate network zone<\/li>\n\n\n\n<li>Alternative network zones<\/li>\n\n\n\n<li>Connectivity\/fallback behavior<\/li>\n\n\n\n<li>Firewall rules<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Unexpected process group split<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Host groups<\/li>\n\n\n\n<li>Process group detection rules<\/li>\n\n\n\n<li>Environment variables<\/li>\n\n\n\n<li>Container image metadata<\/li>\n\n\n\n<li>Kubernetes labels\/annotations<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">6. ActiveGate implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">6.1 What ActiveGate does<\/h2>\n\n\n\n<p>ActiveGate is a secure gateway\/proxy that establishes Dynatrace presence in a local network. It can route OneAgent traffic, reduce outbound connectivity complexity, support sealed networks, and run integration or extension modules.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6.2 ActiveGate use cases<\/h2>\n\n\n\n<p>Use ActiveGate for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Routing OneAgent traffic through a local point<\/li>\n\n\n\n<li>Reducing firewall rules<\/li>\n\n\n\n<li>Sealed\/private networks<\/li>\n\n\n\n<li>Proxy-like connectivity<\/li>\n\n\n\n<li>Cloud integrations<\/li>\n\n\n\n<li>Kubernetes\/OpenShift monitoring<\/li>\n\n\n\n<li>Remote technology monitoring through extensions<\/li>\n\n\n\n<li>OTLP ingestion through ActiveGate<\/li>\n\n\n\n<li>Private Synthetic locations<\/li>\n\n\n\n<li>Beacon forwarding in some RUM scenarios<\/li>\n\n\n\n<li>Memory dump handling<\/li>\n\n\n\n<li>Environment API access through ActiveGate<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6.3 ActiveGate types and concepts<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Environment ActiveGate<\/h3>\n\n\n\n<p>Usually used for SaaS environments to provide local routing, integrations, and extensions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Cluster ActiveGate<\/h3>\n\n\n\n<p>More relevant to Dynatrace Managed scenarios.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Containerized ActiveGate<\/h3>\n\n\n\n<p>Often used in Kubernetes deployments.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6.4 ActiveGate sizing and placement<\/h2>\n\n\n\n<p>Consider:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Number of OneAgents<\/li>\n\n\n\n<li>Network region\/data center<\/li>\n\n\n\n<li>Firewall zones<\/li>\n\n\n\n<li>Cloud region<\/li>\n\n\n\n<li>Kubernetes cluster count<\/li>\n\n\n\n<li>Extension load<\/li>\n\n\n\n<li>Synthetic private location workload<\/li>\n\n\n\n<li>OTLP ingestion volume<\/li>\n\n\n\n<li>High availability requirements<\/li>\n\n\n\n<li>CPU, memory, disk, and network throughput<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6.5 ActiveGate high availability<\/h2>\n\n\n\n<p>Recommended approach:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Deploy at least two ActiveGates per critical network zone where possible.<\/li>\n\n\n\n<li>Avoid a single point of failure for production routing.<\/li>\n\n\n\n<li>Configure network zones and alternatives.<\/li>\n\n\n\n<li>Validate failover behavior.<\/li>\n\n\n\n<li>Monitor ActiveGate health.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6.6 ActiveGate and cloud monitoring<\/h2>\n\n\n\n<p>ActiveGate may be required or recommended for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>AWS monitoring at scale<\/li>\n\n\n\n<li>Azure monitoring<\/li>\n\n\n\n<li>Cloud Foundry monitoring<\/li>\n\n\n\n<li>Kubernetes\/OpenShift API monitoring<\/li>\n\n\n\n<li>VMware monitoring<\/li>\n\n\n\n<li>Remote database or network device monitoring<\/li>\n\n\n\n<li>Extensions that poll remote systems<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6.7 ActiveGate and OTLP<\/h2>\n\n\n\n<p>Dynatrace supports OTLP ingestion through:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dynatrace SaaS platform endpoints<\/li>\n\n\n\n<li>ActiveGate endpoints<\/li>\n\n\n\n<li>Dynatrace Collector as an intermediary<\/li>\n<\/ul>\n\n\n\n<p>Use ActiveGate OTLP endpoints when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Applications cannot directly reach Dynatrace SaaS.<\/li>\n\n\n\n<li>Traffic must stay inside a private network first.<\/li>\n\n\n\n<li>You want local ingress routing.<\/li>\n\n\n\n<li>You need to control egress points.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6.8 ActiveGate validation checklist<\/h2>\n\n\n\n<p>Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ActiveGate appears in Deployment Status.<\/li>\n\n\n\n<li>ActiveGate version is current.<\/li>\n\n\n\n<li>Correct modules are enabled.<\/li>\n\n\n\n<li>ActiveGate can reach Dynatrace.<\/li>\n\n\n\n<li>OneAgents can reach ActiveGate.<\/li>\n\n\n\n<li>Network zone is correct.<\/li>\n\n\n\n<li>Cloud integration data appears.<\/li>\n\n\n\n<li>Kubernetes API monitoring appears.<\/li>\n\n\n\n<li>Extension data appears.<\/li>\n\n\n\n<li>Private synthetic checks work if configured.<\/li>\n\n\n\n<li>OTLP ingestion endpoint works if used.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">6.9 ActiveGate troubleshooting<\/h2>\n\n\n\n<p>Common issues:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Firewall blocks outbound SaaS connection.<\/li>\n\n\n\n<li>OneAgents cannot reach ActiveGate.<\/li>\n\n\n\n<li>Wrong network zone.<\/li>\n\n\n\n<li>Wrong ActiveGate type.<\/li>\n\n\n\n<li>Missing module.<\/li>\n\n\n\n<li>Proxy misconfiguration.<\/li>\n\n\n\n<li>Certificate\/TLS issues.<\/li>\n\n\n\n<li>Cloud API credentials invalid.<\/li>\n\n\n\n<li>Kubernetes API permissions missing.<\/li>\n\n\n\n<li>OTLP endpoint path incorrect.<\/li>\n\n\n\n<li>Port mismatch.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">7. Network zones<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">7.1 What network zones are<\/h2>\n\n\n\n<p>Network zones are Dynatrace entities that represent network structure. They help route traffic efficiently and avoid unnecessary traffic across data centers or network regions.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7.2 Why network zones matter<\/h2>\n\n\n\n<p>Without network zones, OneAgents may connect to any reachable ActiveGate, including one in another region. This can create inefficient routing and unnecessary cross-region traffic.<\/p>\n\n\n\n<p>With network zones, OneAgents prefer ActiveGates in their assigned zone and can use alternative zones as fallback.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7.3 Network zone design pattern<\/h2>\n\n\n\n<p>Recommended naming pattern:<\/p>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-1\" data-shcb-language-name=\"CSS\" data-shcb-language-slug=\"css\"><span><code class=\"hljs language-css\"><span class=\"hljs-selector-tag\">provider<\/span><span class=\"hljs-selector-class\">.region<\/span><span class=\"hljs-selector-class\">.availability-zone<\/span><span class=\"hljs-selector-class\">.datacenter<\/span><span class=\"hljs-selector-class\">.tier<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-1\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">CSS<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">css<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<p>Examples:<\/p>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-2\" data-shcb-language-name=\"CSS\" data-shcb-language-slug=\"css\"><span><code class=\"hljs language-css\"><span class=\"hljs-selector-tag\">aws<\/span><span class=\"hljs-selector-class\">.us-east-1<\/span><span class=\"hljs-selector-class\">.prod<\/span>\n<span class=\"hljs-selector-tag\">aws<\/span><span class=\"hljs-selector-class\">.eu-west-1<\/span><span class=\"hljs-selector-class\">.prod<\/span>\n<span class=\"hljs-selector-tag\">azure<\/span><span class=\"hljs-selector-class\">.japaneast<\/span><span class=\"hljs-selector-class\">.prod<\/span>\n<span class=\"hljs-selector-tag\">onprem<\/span><span class=\"hljs-selector-class\">.dc1<\/span><span class=\"hljs-selector-class\">.prod<\/span>\n<span class=\"hljs-selector-tag\">onprem<\/span><span class=\"hljs-selector-class\">.dc2<\/span><span class=\"hljs-selector-class\">.nonprod<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-2\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">CSS<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">css<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<h2 class=\"wp-block-heading\">7.4 Network zone implementation steps<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Identify regions\/data centers\/firewall zones.<\/li>\n\n\n\n<li>Define zone names.<\/li>\n\n\n\n<li>Deploy ActiveGates per zone.<\/li>\n\n\n\n<li>Assign ActiveGates to zones.<\/li>\n\n\n\n<li>Assign OneAgents to zones.<\/li>\n\n\n\n<li>Configure alternative zones.<\/li>\n\n\n\n<li>Validate routing.<\/li>\n\n\n\n<li>Test failover.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">7.5 Exam focus<\/h2>\n\n\n\n<p>Know:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Network zones model network topology.<\/li>\n\n\n\n<li>They influence OneAgent-to-ActiveGate routing.<\/li>\n\n\n\n<li>They reduce inefficient cross-region traffic.<\/li>\n\n\n\n<li>Alternative zones provide fallback.<\/li>\n\n\n\n<li>Network zones are especially important in enterprise and multi-region deployments.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">8. Kubernetes implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">8.1 Dynatrace Operator<\/h2>\n\n\n\n<p>Dynatrace Operator manages the automated rollout, configuration, and lifecycle of Dynatrace components in Kubernetes environments.<\/p>\n\n\n\n<p>Core components:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dynatrace Operator<\/li>\n\n\n\n<li>Dynatrace Operator webhook<\/li>\n\n\n\n<li>CSI driver<\/li>\n\n\n\n<li>DynaKube custom resource<\/li>\n\n\n\n<li>OneAgent components<\/li>\n\n\n\n<li>ActiveGate components<\/li>\n\n\n\n<li>Code module injection<\/li>\n\n\n\n<li>Kubernetes API monitoring<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">8.2 DynaKube<\/h2>\n\n\n\n<p>DynaKube is the Kubernetes custom resource used to configure Dynatrace Operator.<\/p>\n\n\n\n<p>Important DynaKube concepts:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>apiUrl<\/code><\/li>\n\n\n\n<li><code>networkZone<\/code><\/li>\n\n\n\n<li><code>proxy<\/code><\/li>\n\n\n\n<li><code>skipCertCheck<\/code><\/li>\n\n\n\n<li><code>customPullSecret<\/code><\/li>\n\n\n\n<li>OneAgent mode<\/li>\n\n\n\n<li>ActiveGate configuration<\/li>\n\n\n\n<li>Namespace selector<\/li>\n\n\n\n<li>Metadata enrichment<\/li>\n\n\n\n<li>Code module injection<\/li>\n\n\n\n<li>Token secret<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">8.3 Kubernetes deployment modes<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">cloudNativeFullStack<\/h3>\n\n\n\n<p>Provides infrastructure and application monitoring in Kubernetes using OneAgent injection and Kubernetes API monitoring.<\/p>\n\n\n\n<p>Best for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Full Kubernetes observability<\/li>\n\n\n\n<li>Cluster performance and application behavior<\/li>\n\n\n\n<li>Deep application tracing<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">classicFullStack<\/h3>\n\n\n\n<p>Classic full-stack mode. Still relevant in some existing or migration scenarios.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">applicationMonitoring<\/h3>\n\n\n\n<p>Application monitoring mode focuses on selected applications\/pods rather than full node-level monitoring.<\/p>\n\n\n\n<p>Best for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Selective application monitoring<\/li>\n\n\n\n<li>Teams that cannot or should not monitor nodes<\/li>\n\n\n\n<li>SaaS\/multi-tenant clusters where only some namespaces are in scope<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">hostMonitoring<\/h3>\n\n\n\n<p>Host-level monitoring for Kubernetes nodes without deep application injection.<\/p>\n\n\n\n<p>Best for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Infrastructure visibility<\/li>\n\n\n\n<li>Environments where application injection is not desired<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">8.4 Kubernetes implementation planning<\/h2>\n\n\n\n<p>Before deploying, collect:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cluster distribution and version<\/li>\n\n\n\n<li>OpenShift or vanilla Kubernetes<\/li>\n\n\n\n<li>Managed Kubernetes provider<\/li>\n\n\n\n<li>Namespace ownership<\/li>\n\n\n\n<li>Security policies<\/li>\n\n\n\n<li>Pod Security Standards \/ SCC \/ PSP legacy considerations<\/li>\n\n\n\n<li>Admission webhook restrictions<\/li>\n\n\n\n<li>Network policies<\/li>\n\n\n\n<li>Proxy requirements<\/li>\n\n\n\n<li>Private registry requirements<\/li>\n\n\n\n<li>Image pull secret requirements<\/li>\n\n\n\n<li>Istio\/service mesh presence<\/li>\n\n\n\n<li>Read-only filesystem restrictions<\/li>\n\n\n\n<li>Desired monitoring mode<\/li>\n\n\n\n<li>Log ingestion requirements<\/li>\n\n\n\n<li>Namespace selector requirements<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">8.5 Namespace selectors and annotations<\/h2>\n\n\n\n<p>Use namespace selectors and annotations to control where OneAgent injection, metadata enrichment, or OTLP auto-configuration should apply.<\/p>\n\n\n\n<p>Important concept:<\/p>\n\n\n\n<p>Namespace selector and annotations affect injection done by the webhook. They do not necessarily affect Kubernetes API monitoring or host-level monitoring.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">8.6 Kubernetes log monitoring<\/h2>\n\n\n\n<p>Dynatrace supports Kubernetes log monitoring using Dynatrace Log modules.<\/p>\n\n\n\n<p>Common options:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OneAgent Log module integrated with OneAgent deployed on nodes<\/li>\n\n\n\n<li>Standalone Kubernetes Log module without OneAgent<\/li>\n<\/ul>\n\n\n\n<p>Implementation decisions:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Which namespaces to collect<\/li>\n\n\n\n<li>Which container logs to exclude<\/li>\n\n\n\n<li>Whether logs need masking<\/li>\n\n\n\n<li>Which bucket to route logs to<\/li>\n\n\n\n<li>Retention by environment<\/li>\n\n\n\n<li>OpenPipeline processing and parsing<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">8.7 Kubernetes metadata enrichment<\/h2>\n\n\n\n<p>Metadata enrichment adds Kubernetes context to telemetry.<\/p>\n\n\n\n<p>Useful metadata:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cluster<\/li>\n\n\n\n<li>Namespace<\/li>\n\n\n\n<li>Pod<\/li>\n\n\n\n<li>Container<\/li>\n\n\n\n<li>Workload<\/li>\n\n\n\n<li>Labels<\/li>\n\n\n\n<li>Annotations<\/li>\n\n\n\n<li>Node<\/li>\n\n\n\n<li>Service account<\/li>\n<\/ul>\n\n\n\n<p>Why it matters:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Better filtering<\/li>\n\n\n\n<li>Better ownership mapping<\/li>\n\n\n\n<li>Better DQL queries<\/li>\n\n\n\n<li>Better troubleshooting<\/li>\n\n\n\n<li>Better tag\/zone strategy<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">8.8 Kubernetes GitOps deployment<\/h2>\n\n\n\n<p>Dynatrace Operator and DynaKube can be deployed with GitOps tools such as Argo CD.<\/p>\n\n\n\n<p>Recommended approach:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Store Helm values or manifests in Git.<\/li>\n\n\n\n<li>Use separate overlays per cluster\/environment.<\/li>\n\n\n\n<li>Keep tokens in Kubernetes secrets or secure secret management.<\/li>\n\n\n\n<li>Avoid committing secrets.<\/li>\n\n\n\n<li>Validate DynaKube changes in non-production first.<\/li>\n\n\n\n<li>Use pull requests for monitoring mode changes.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">8.9 Kubernetes validation checklist<\/h2>\n\n\n\n<p>Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Operator pod is running.<\/li>\n\n\n\n<li>Webhook is running.<\/li>\n\n\n\n<li>CSI driver is running when required.<\/li>\n\n\n\n<li>ActiveGate pod is running if configured.<\/li>\n\n\n\n<li>OneAgent components are running.<\/li>\n\n\n\n<li>DynaKube status is healthy.<\/li>\n\n\n\n<li>Kubernetes cluster appears in Dynatrace.<\/li>\n\n\n\n<li>Nodes appear.<\/li>\n\n\n\n<li>Workloads appear.<\/li>\n\n\n\n<li>Pods appear.<\/li>\n\n\n\n<li>Services are discovered.<\/li>\n\n\n\n<li>Code modules are injected where expected.<\/li>\n\n\n\n<li>Distributed traces appear.<\/li>\n\n\n\n<li>Logs appear if configured.<\/li>\n\n\n\n<li>Metadata enrichment works.<\/li>\n\n\n\n<li>Namespace selectors behave as expected.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">8.10 Kubernetes troubleshooting<\/h2>\n\n\n\n<p>Common issues:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Operator not deploying components<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>DynaKube syntax<\/li>\n\n\n\n<li>API URL<\/li>\n\n\n\n<li>Token secret<\/li>\n\n\n\n<li>Operator version<\/li>\n\n\n\n<li>DynaKube API version compatibility<\/li>\n\n\n\n<li>RBAC permissions<\/li>\n\n\n\n<li>Namespace restrictions<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Pods not injected<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monitoring mode<\/li>\n\n\n\n<li>Namespace selector<\/li>\n\n\n\n<li>Pod annotations<\/li>\n\n\n\n<li>Webhook availability<\/li>\n\n\n\n<li>Pod restart after configuration<\/li>\n\n\n\n<li>Image pull issues<\/li>\n\n\n\n<li>Security policies<\/li>\n\n\n\n<li>CSI driver availability<\/li>\n\n\n\n<li>Unsupported runtime<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">ActiveGate pod unhealthy<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>API URL<\/li>\n\n\n\n<li>Proxy<\/li>\n\n\n\n<li>Network route<\/li>\n\n\n\n<li>DNS<\/li>\n\n\n\n<li>TLS\/certificate validation<\/li>\n\n\n\n<li>Token secret<\/li>\n\n\n\n<li>Resource limits<\/li>\n\n\n\n<li>Network policy<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Logs missing<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Log module configuration<\/li>\n\n\n\n<li>Namespace filters<\/li>\n\n\n\n<li>Container filters<\/li>\n\n\n\n<li>OneAgent\/log module deployment<\/li>\n\n\n\n<li>File permissions<\/li>\n\n\n\n<li>OpenPipeline routing<\/li>\n\n\n\n<li>Bucket permissions<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">9. Cloud platform implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">9.1 Cloud monitoring goals<\/h2>\n\n\n\n<p>Cloud monitoring should capture:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud service metrics<\/li>\n\n\n\n<li>Cloud resource metadata<\/li>\n\n\n\n<li>Relationships between cloud resources and monitored workloads<\/li>\n\n\n\n<li>Tags\/labels<\/li>\n\n\n\n<li>Infrastructure health<\/li>\n\n\n\n<li>Cost\/usage context where applicable<\/li>\n\n\n\n<li>Events and resource state<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9.2 AWS implementation<\/h2>\n\n\n\n<p>Typical tasks:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create IAM role or access permissions.<\/li>\n\n\n\n<li>Configure AWS integration in Dynatrace.<\/li>\n\n\n\n<li>Select services to monitor.<\/li>\n\n\n\n<li>Configure regions.<\/li>\n\n\n\n<li>Decide on ActiveGate need for scale or private routing.<\/li>\n\n\n\n<li>Validate metrics and metadata.<\/li>\n\n\n\n<li>Map AWS tags to Dynatrace tags.<\/li>\n\n\n\n<li>Monitor ingest and cost.<\/li>\n<\/ul>\n\n\n\n<p>AWS services commonly monitored:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>EC2<\/li>\n\n\n\n<li>ELB\/ALB\/NLB<\/li>\n\n\n\n<li>RDS<\/li>\n\n\n\n<li>Lambda<\/li>\n\n\n\n<li>ECS\/EKS<\/li>\n\n\n\n<li>S3<\/li>\n\n\n\n<li>CloudWatch metrics<\/li>\n\n\n\n<li>API Gateway<\/li>\n\n\n\n<li>DynamoDB<\/li>\n\n\n\n<li>SQS\/SNS<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9.3 Azure implementation<\/h2>\n\n\n\n<p>Typical tasks:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Create app registration \/ service principal.<\/li>\n\n\n\n<li>Assign required Azure permissions.<\/li>\n\n\n\n<li>Configure Azure integration.<\/li>\n\n\n\n<li>Select subscriptions and services.<\/li>\n\n\n\n<li>Decide on ActiveGate requirement.<\/li>\n\n\n\n<li>Validate metrics and metadata.<\/li>\n\n\n\n<li>Align Azure tags to Dynatrace tags.<\/li>\n<\/ul>\n\n\n\n<p>Azure resources commonly monitored:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Virtual Machines<\/li>\n\n\n\n<li>App Service<\/li>\n\n\n\n<li>AKS<\/li>\n\n\n\n<li>Azure Functions<\/li>\n\n\n\n<li>SQL Database<\/li>\n\n\n\n<li>Storage<\/li>\n\n\n\n<li>Load Balancers<\/li>\n\n\n\n<li>Application Gateway<\/li>\n\n\n\n<li>Event Hubs<\/li>\n\n\n\n<li>Service Bus<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9.4 Google Cloud implementation<\/h2>\n\n\n\n<p>Typical tasks:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Configure service account.<\/li>\n\n\n\n<li>Assign permissions.<\/li>\n\n\n\n<li>Configure GCP integration.<\/li>\n\n\n\n<li>Select projects and services.<\/li>\n\n\n\n<li>Validate metrics and metadata.<\/li>\n\n\n\n<li>Align labels with Dynatrace tags.<\/li>\n<\/ul>\n\n\n\n<p>GCP resources commonly monitored:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Compute Engine<\/li>\n\n\n\n<li>GKE<\/li>\n\n\n\n<li>Cloud SQL<\/li>\n\n\n\n<li>Cloud Functions<\/li>\n\n\n\n<li>Cloud Run<\/li>\n\n\n\n<li>Pub\/Sub<\/li>\n\n\n\n<li>Load Balancing<\/li>\n\n\n\n<li>Cloud Storage<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9.5 Cloud implementation best practices<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use least-privilege cloud permissions.<\/li>\n\n\n\n<li>Start with important services and regions.<\/li>\n\n\n\n<li>Avoid enabling every cloud metric blindly.<\/li>\n\n\n\n<li>Align cloud tags\/labels with Dynatrace ownership strategy.<\/li>\n\n\n\n<li>Validate cloud API limits and polling behavior.<\/li>\n\n\n\n<li>Monitor ingest and cost.<\/li>\n\n\n\n<li>Document cloud account\/subscription\/project ownership.<\/li>\n\n\n\n<li>Use ActiveGate when required for scale, network, or integration architecture.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">9.6 Exam focus<\/h2>\n\n\n\n<p>Know:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Cloud integrations require cloud permissions and Dynatrace configuration.<\/li>\n\n\n\n<li>ActiveGate may be required for some cloud monitoring scenarios.<\/li>\n\n\n\n<li>Cloud metadata and tags are important for topology, ownership, and filtering.<\/li>\n\n\n\n<li>Cloud integrations can increase data volume and must be governed.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">10. OpenTelemetry implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">10.1 Why OpenTelemetry matters<\/h2>\n\n\n\n<p>OpenTelemetry is a vendor-neutral observability framework used to generate traces, metrics, and logs.<\/p>\n\n\n\n<p>Dynatrace implementations often need OpenTelemetry when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Application language\/framework is not automatically instrumented.<\/li>\n\n\n\n<li>Teams already use OTel SDKs or collectors.<\/li>\n\n\n\n<li>Vendor-neutral instrumentation is required.<\/li>\n\n\n\n<li>Custom spans or business attributes are needed.<\/li>\n\n\n\n<li>Third-party services emit OTLP.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">10.2 Ingestion options<\/h2>\n\n\n\n<p>Dynatrace supports OTLP ingestion through:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dynatrace SaaS OTLP endpoints<\/li>\n\n\n\n<li>Environment ActiveGate OTLP endpoints<\/li>\n\n\n\n<li>Containerized ActiveGate OTLP endpoints<\/li>\n\n\n\n<li>Dynatrace Collector as intermediary<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">10.3 Signal types<\/h2>\n\n\n\n<p>OTLP signal paths:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Traces: <code>\/v1\/traces<\/code><\/li>\n\n\n\n<li>Metrics: <code>\/v1\/metrics<\/code><\/li>\n\n\n\n<li>Logs: <code>\/v1\/logs<\/code><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">10.4 OneAgent and OpenTelemetry<\/h2>\n\n\n\n<p>There are two common ways to use OneAgent with OpenTelemetry:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Send OpenTelemetry traces to Dynatrace OTLP API endpoints.<\/li>\n\n\n\n<li>Use the OneAgent code module&#8217;s OpenTelemetry Span Sensor to detect OTel spans from trace data.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">10.5 Dynatrace Collector<\/h2>\n\n\n\n<p>Use Dynatrace Collector when you need:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Batching<\/li>\n\n\n\n<li>Local buffering<\/li>\n\n\n\n<li>Transformations<\/li>\n\n\n\n<li>Sensitive data masking before forwarding<\/li>\n\n\n\n<li>Collector-based topology<\/li>\n\n\n\n<li>Existing OTel collector architecture<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">10.6 OpenTelemetry design questions<\/h2>\n\n\n\n<p>Ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Which apps emit OTel?<\/li>\n\n\n\n<li>Which signals: traces, metrics, logs?<\/li>\n\n\n\n<li>Where are collectors deployed?<\/li>\n\n\n\n<li>Can apps reach Dynatrace SaaS directly?<\/li>\n\n\n\n<li>Should OTLP go through ActiveGate?<\/li>\n\n\n\n<li>Are custom resource attributes needed?<\/li>\n\n\n\n<li>Are service names consistent?<\/li>\n\n\n\n<li>Is context propagation working?<\/li>\n\n\n\n<li>Are spans linked to OneAgent-discovered services?<\/li>\n\n\n\n<li>Are semantic conventions followed?<\/li>\n\n\n\n<li>Are sensitive attributes masked?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">10.7 OTel validation checklist<\/h2>\n\n\n\n<p>Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OTLP endpoint path is correct.<\/li>\n\n\n\n<li>Token\/scopes are correct.<\/li>\n\n\n\n<li>Traces arrive.<\/li>\n\n\n\n<li>Metrics arrive if configured.<\/li>\n\n\n\n<li>Logs arrive if configured.<\/li>\n\n\n\n<li>Service names are meaningful.<\/li>\n\n\n\n<li>Resource attributes are present.<\/li>\n\n\n\n<li>Trace context propagates across services.<\/li>\n\n\n\n<li>OTel spans appear in distributed traces.<\/li>\n\n\n\n<li>Data is correlated with OneAgent telemetry where expected.<\/li>\n\n\n\n<li>No sensitive attributes are exposed.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">10.8 Common OTel issues<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Wrong endpoint path.<\/li>\n\n\n\n<li>Wrong token scope.<\/li>\n\n\n\n<li>Compression\/content encoding mismatch.<\/li>\n\n\n\n<li>Collector misconfiguration.<\/li>\n\n\n\n<li>Missing service.name.<\/li>\n\n\n\n<li>Missing resource attributes.<\/li>\n\n\n\n<li>Broken context propagation.<\/li>\n\n\n\n<li>Too much metric cardinality.<\/li>\n\n\n\n<li>Unsupported or inconsistent semantic attributes.<\/li>\n\n\n\n<li>Data sent to SaaS when it should go through ActiveGate.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">11. Log implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">11.1 Log implementation goals<\/h2>\n\n\n\n<p>A good log implementation provides useful logs without uncontrolled volume, cost, or sensitive data exposure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">11.2 Log ingestion sources<\/h2>\n\n\n\n<p>Common sources:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>OneAgent log module<\/li>\n\n\n\n<li>Kubernetes Log module<\/li>\n\n\n\n<li>OpenTelemetry logs<\/li>\n\n\n\n<li>API ingestion<\/li>\n\n\n\n<li>Cloud log integrations<\/li>\n\n\n\n<li>Extensions<\/li>\n\n\n\n<li>Existing log shippers<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">11.3 Log planning questions<\/h2>\n\n\n\n<p>Ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Which logs are needed for troubleshooting?<\/li>\n\n\n\n<li>Which logs are required for compliance?<\/li>\n\n\n\n<li>Which logs are noisy and low value?<\/li>\n\n\n\n<li>Which logs contain sensitive data?<\/li>\n\n\n\n<li>Which logs need long retention?<\/li>\n\n\n\n<li>Which logs need access restrictions?<\/li>\n\n\n\n<li>Which teams own which logs?<\/li>\n\n\n\n<li>Which logs should become metrics or events?<\/li>\n\n\n\n<li>Which fields should be extracted?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">11.4 OneAgent log monitoring<\/h2>\n\n\n\n<p>OneAgent can discover and collect logs from monitored hosts\/processes.<\/p>\n\n\n\n<p>Configure:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Automatic log discovery<\/li>\n\n\n\n<li>Include\/exclude rules<\/li>\n\n\n\n<li>Sensitive data masking<\/li>\n\n\n\n<li>Host or host-group-level settings<\/li>\n\n\n\n<li>Process-specific log rules<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">11.5 Kubernetes logs<\/h2>\n\n\n\n<p>Plan:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Namespace inclusion\/exclusion<\/li>\n\n\n\n<li>Container inclusion\/exclusion<\/li>\n\n\n\n<li>Workload ownership<\/li>\n\n\n\n<li>Log volume per namespace<\/li>\n\n\n\n<li>OpenPipeline routing by namespace\/app\/team<\/li>\n\n\n\n<li>Retention by environment<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">11.6 OpenPipeline for logs<\/h2>\n\n\n\n<p>Use OpenPipeline to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Route logs to buckets<\/li>\n\n\n\n<li>Drop noisy records<\/li>\n\n\n\n<li>Parse fields<\/li>\n\n\n\n<li>Add ownership metadata<\/li>\n\n\n\n<li>Rename fields<\/li>\n\n\n\n<li>Remove fields<\/li>\n\n\n\n<li>Mask sensitive values<\/li>\n\n\n\n<li>Convert records to events or business events where appropriate<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">11.7 Bucket and retention strategy<\/h2>\n\n\n\n<p>Example bucket design:<\/p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">logs_prod_critical_90d\nlogs_prod_application_30d\nlogs_nonprod_14d\nlogs_debug_3d\nlogs_security_audit_365d\n<\/code><\/span><\/pre>\n\n\n<h2 class=\"wp-block-heading\">11.8 Log implementation validation<\/h2>\n\n\n\n<p>Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Logs arrive from expected sources.<\/li>\n\n\n\n<li>Unwanted logs are excluded.<\/li>\n\n\n\n<li>Sensitive values are masked.<\/li>\n\n\n\n<li>Logs route to correct buckets.<\/li>\n\n\n\n<li>Retention matches design.<\/li>\n\n\n\n<li>Teams can query only authorized logs.<\/li>\n\n\n\n<li>DQL queries work.<\/li>\n\n\n\n<li>Logs correlate with hosts, services, traces, and problems.<\/li>\n\n\n\n<li>Cost\/volume is within expected range.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">12. OpenPipeline implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">12.1 What OpenPipeline does<\/h2>\n\n\n\n<p>OpenPipeline is Dynatrace\u2019s data handling solution for ingesting and processing data from different sources at scale and in different formats.<\/p>\n\n\n\n<p>It helps with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data ingestion<\/li>\n\n\n\n<li>Processing<\/li>\n\n\n\n<li>Routing<\/li>\n\n\n\n<li>Filtering<\/li>\n\n\n\n<li>Enrichment<\/li>\n\n\n\n<li>Contextualization<\/li>\n\n\n\n<li>Masking<\/li>\n\n\n\n<li>Cost optimization<\/li>\n\n\n\n<li>Data quality control<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">12.2 Data flow<\/h2>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">Ingest source\n  \u2193\nRoute\n  \u2193\nPipeline\n  \u2193\nProcessing stage\n  \u2193\nBucket \/ storage \/ persistence\n<\/code><\/span><\/pre>\n\n\n<h2 class=\"wp-block-heading\">12.3 Processing stage<\/h2>\n\n\n\n<p>The Processing stage can prepare data for analysis, extraction, forwarding, and persistence.<\/p>\n\n\n\n<p>Available processor concepts include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>DQL processor<\/li>\n\n\n\n<li>Add fields<\/li>\n\n\n\n<li>Remove fields<\/li>\n\n\n\n<li>Rename fields<\/li>\n\n\n\n<li>Drop record<\/li>\n\n\n\n<li>Logs Technology bundle processor<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">12.4 Example implementation patterns<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Pattern 1: Drop noisy debug logs<\/h3>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-3\" data-shcb-language-name=\"HTTP\" data-shcb-language-slug=\"http\"><span><code class=\"hljs language-http\"><span class=\"hljs-attribute\">Match<\/span>: env == prod and loglevel == DEBUG\n<span class=\"hljs-attribute\">Action<\/span>: drop record\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-3\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">HTTP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">http<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<h3 class=\"wp-block-heading\">Pattern 2: Add ownership field<\/h3>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-4\" data-shcb-language-name=\"HTTP\" data-shcb-language-slug=\"http\"><span><code class=\"hljs language-http\"><span class=\"hljs-attribute\">Match<\/span>: kubernetes.namespace.name == payments\n<span class=\"hljs-attribute\">Action<\/span>: add team = payments\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-4\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">HTTP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">http<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<h3 class=\"wp-block-heading\">Pattern 3: Route critical application logs<\/h3>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-5\" data-shcb-language-name=\"HTTP\" data-shcb-language-slug=\"http\"><span><code class=\"hljs language-http\"><span class=\"hljs-attribute\">Match<\/span>: app == checkout and env == prod\n<span class=\"hljs-attribute\">Action<\/span>: route to logs_prod_critical_90d\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-5\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">HTTP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">http<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<h3 class=\"wp-block-heading\">Pattern 4: Mask sensitive data<\/h3>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-6\" data-shcb-language-name=\"HTTP\" data-shcb-language-slug=\"http\"><span><code class=\"hljs language-http\"><span class=\"hljs-attribute\">Match<\/span>: content contains account-like value\n<span class=\"hljs-attribute\">Action<\/span>: mask matched value\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-6\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">HTTP<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">http<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<h3 class=\"wp-block-heading\">Pattern 5: Extract transaction ID<\/h3>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-7\" data-shcb-language-name=\"CSS\" data-shcb-language-slug=\"css\"><span><code class=\"hljs language-css\"><span class=\"hljs-selector-tag\">Parse<\/span> <span class=\"hljs-selector-tag\">content<\/span> <span class=\"hljs-selector-tag\">and<\/span> <span class=\"hljs-selector-tag\">add<\/span> <span class=\"hljs-selector-tag\">transaction<\/span><span class=\"hljs-selector-class\">.id<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-7\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">CSS<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">css<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<h2 class=\"wp-block-heading\">12.5 OpenPipeline testing checklist<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use sample records.<\/li>\n\n\n\n<li>Validate matching condition.<\/li>\n\n\n\n<li>Validate parsed fields.<\/li>\n\n\n\n<li>Validate masking output.<\/li>\n\n\n\n<li>Validate destination bucket.<\/li>\n\n\n\n<li>Validate query results after processing.<\/li>\n\n\n\n<li>Validate cost\/volume effect.<\/li>\n\n\n\n<li>Validate downstream dashboards or alerts.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">12.6 Exam focus<\/h2>\n\n\n\n<p>Know that OpenPipeline is central to implementation because it connects ingestion with data quality, compliance, routing, and cost control.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">13. Grail, buckets, and data retention<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">13.1 Grail role in implementation<\/h2>\n\n\n\n<p>Grail is the unified observability data lakehouse for logs, metrics, traces, events, business events, and other telemetry.<\/p>\n\n\n\n<p>Implementers must decide:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What data goes into Grail.<\/li>\n\n\n\n<li>Which buckets store it.<\/li>\n\n\n\n<li>How long it is retained.<\/li>\n\n\n\n<li>Who can access it.<\/li>\n\n\n\n<li>How it is queried.<\/li>\n\n\n\n<li>How ingestion cost is controlled.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">13.2 Bucket design principles<\/h2>\n\n\n\n<p>Design buckets by:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Environment<\/li>\n\n\n\n<li>Data type<\/li>\n\n\n\n<li>Team\/application<\/li>\n\n\n\n<li>Retention need<\/li>\n\n\n\n<li>Compliance requirement<\/li>\n\n\n\n<li>Access requirement<\/li>\n\n\n\n<li>Volume profile<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">13.3 Retention design<\/h2>\n\n\n\n<p>Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Debug logs: 3\u20137 days<\/li>\n\n\n\n<li>Non-production logs: 7\u201314 days<\/li>\n\n\n\n<li>Production app logs: 30\u201390 days<\/li>\n\n\n\n<li>Security\/audit logs: 180\u2013365 days<\/li>\n\n\n\n<li>Business events: based on reporting need<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">13.4 Query design<\/h2>\n\n\n\n<p>Teach users to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Query narrow time windows.<\/li>\n\n\n\n<li>Filter early.<\/li>\n\n\n\n<li>Use relevant fields.<\/li>\n\n\n\n<li>Avoid broad scans.<\/li>\n\n\n\n<li>Use dashboards carefully.<\/li>\n\n\n\n<li>Use summaries for large data.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">13.5 Exam focus<\/h2>\n\n\n\n<p>Know:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Buckets control retention and access strategy.<\/li>\n\n\n\n<li>OpenPipeline can route data to buckets.<\/li>\n\n\n\n<li>Poor bucket and retention design can increase cost and security risk.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">14. Tags, ownership, and entity organization<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">14.1 Why tagging is implementation-critical<\/h2>\n\n\n\n<p>Tags make the implementation usable.<\/p>\n\n\n\n<p>Without tags, teams struggle with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Ownership<\/li>\n\n\n\n<li>Alert routing<\/li>\n\n\n\n<li>Dashboard filtering<\/li>\n\n\n\n<li>Maintenance windows<\/li>\n\n\n\n<li>Management zones<\/li>\n\n\n\n<li>Cost allocation<\/li>\n\n\n\n<li>Search<\/li>\n\n\n\n<li>Reporting<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">14.2 Tag sources<\/h2>\n\n\n\n<p>Tags can come from:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Manual assignment<\/li>\n\n\n\n<li>Automatic tagging rules<\/li>\n\n\n\n<li>Cloud tags<\/li>\n\n\n\n<li>Kubernetes labels<\/li>\n\n\n\n<li>Kubernetes annotations<\/li>\n\n\n\n<li>Host group<\/li>\n\n\n\n<li>Process group rules<\/li>\n\n\n\n<li>Environment variables<\/li>\n\n\n\n<li>Metadata enrichment<\/li>\n\n\n\n<li>API\/automation<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">14.3 Standard tag model<\/h2>\n\n\n\n<p>Recommended tag keys:<\/p>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">env\napp\nservice\nteam\nowner\ncost-center\nregion\nplatform\ncriticality\ncompliance\nbusiness-unit\n<\/code><\/span><\/pre>\n\n\n<p>Examples:<\/p>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-8\" data-shcb-language-name=\"CSS\" data-shcb-language-slug=\"css\"><span><code class=\"hljs language-css\"><span class=\"hljs-selector-tag\">env<\/span><span class=\"hljs-selector-pseudo\">:prod<\/span>\n<span class=\"hljs-selector-tag\">app<\/span><span class=\"hljs-selector-pseudo\">:checkout<\/span>\n<span class=\"hljs-selector-tag\">team<\/span><span class=\"hljs-selector-pseudo\">:payments<\/span>\n<span class=\"hljs-selector-tag\">criticality<\/span><span class=\"hljs-selector-pseudo\">:tier1<\/span>\n<span class=\"hljs-selector-tag\">region<\/span><span class=\"hljs-selector-pseudo\">:apac<\/span>\n<span class=\"hljs-selector-tag\">cost-center<\/span><span class=\"hljs-selector-pseudo\">:cc1234<\/span>\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-8\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">CSS<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">css<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<h2 class=\"wp-block-heading\">14.4 Implementation best practices<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Align with existing CMDB\/cloud\/Kubernetes labels.<\/li>\n\n\n\n<li>Prefer automatic tags over manual tags at scale.<\/li>\n\n\n\n<li>Use lowercase standard values.<\/li>\n\n\n\n<li>Avoid duplicate synonyms like prod, production, prd.<\/li>\n\n\n\n<li>Define owners for tag standards.<\/li>\n\n\n\n<li>Validate tags during rollout.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">14.5 Exam focus<\/h2>\n\n\n\n<p>Know that tags are implementation building blocks for ownership, filtering, alerting, dashboards, management zones, and cost allocation.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">15. Management zones, segments, and access scoping<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">15.1 Management zones<\/h2>\n\n\n\n<p>Management zones define logical scopes of entities and data, often used for team\/application\/environment visibility.<\/p>\n\n\n\n<p>Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Payments production<\/li>\n\n\n\n<li>Checkout non-production<\/li>\n\n\n\n<li>APAC infrastructure<\/li>\n\n\n\n<li>Platform Kubernetes clusters<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">15.2 Management zone design<\/h2>\n\n\n\n<p>Use rules based on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Tags<\/li>\n\n\n\n<li>Host groups<\/li>\n\n\n\n<li>Process groups<\/li>\n\n\n\n<li>Services<\/li>\n\n\n\n<li>Kubernetes namespaces<\/li>\n\n\n\n<li>Cloud tags<\/li>\n\n\n\n<li>Entity relationships<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">15.3 Segments and security context<\/h2>\n\n\n\n<p>Latest Dynatrace uses modern access-scoping concepts such as segments and security context, especially for Grail-powered data and platform resources.<\/p>\n\n\n\n<p>Implementation professionals should understand that classic management zones may not automatically control every log, span, metric, or event in Grail.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">15.4 Exam focus<\/h2>\n\n\n\n<p>Know:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Management zones help scope entity visibility and team views.<\/li>\n\n\n\n<li>Segments\/security context are important in latest Dynatrace access models.<\/li>\n\n\n\n<li>Grail data access may require bucket\/policy\/security-context planning.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">16. Real User Monitoring implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">16.1 What RUM does<\/h2>\n\n\n\n<p>Real User Monitoring captures actual user sessions, user actions, page loads, browser errors, mobile actions, and frontend performance.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">16.2 RUM deployment methods<\/h2>\n\n\n\n<p>Common methods:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Automatic injection by OneAgent<\/li>\n\n\n\n<li>Manual JavaScript tag insertion<\/li>\n\n\n\n<li>Agentless monitoring<\/li>\n\n\n\n<li>Mobile SDK instrumentation<\/li>\n\n\n\n<li>Custom application instrumentation<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">16.3 RUM implementation questions<\/h2>\n\n\n\n<p>Ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Which web\/mobile applications are in scope?<\/li>\n\n\n\n<li>Is OneAgent auto-injection possible?<\/li>\n\n\n\n<li>Are pages served by monitored hosts?<\/li>\n\n\n\n<li>Are Content Security Policy changes needed?<\/li>\n\n\n\n<li>Are cookies allowed?<\/li>\n\n\n\n<li>Are user\/session fields allowed?<\/li>\n\n\n\n<li>Is IP address masking required?<\/li>\n\n\n\n<li>Are user tags allowed?<\/li>\n\n\n\n<li>Is Session Replay required or allowed?<\/li>\n\n\n\n<li>Which user actions matter most?<\/li>\n\n\n\n<li>Which geographies, devices, and browsers matter?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">16.4 Application detection rules<\/h2>\n\n\n\n<p>Use application detection rules to map incoming RUM data to the correct application.<\/p>\n\n\n\n<p>Important when:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Multiple apps share domains.<\/li>\n\n\n\n<li>Same domain hosts multiple frontends.<\/li>\n\n\n\n<li>URLs need path-based separation.<\/li>\n\n\n\n<li>Mobile\/web traffic needs clear separation.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">16.5 Privacy controls<\/h2>\n\n\n\n<p>RUM implementation must consider:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>User identification<\/li>\n\n\n\n<li>IP masking<\/li>\n\n\n\n<li>Personal data in URLs<\/li>\n\n\n\n<li>Form field capture<\/li>\n\n\n\n<li>Session Replay masking<\/li>\n\n\n\n<li>Cookies and consent<\/li>\n\n\n\n<li>Legal\/compliance requirements<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">16.6 RUM validation checklist<\/h2>\n\n\n\n<p>Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Application receives real user data.<\/li>\n\n\n\n<li>User sessions appear.<\/li>\n\n\n\n<li>User actions appear.<\/li>\n\n\n\n<li>JavaScript errors appear if present.<\/li>\n\n\n\n<li>Frontend\/backend split is visible.<\/li>\n\n\n\n<li>Backend services are linked to user actions.<\/li>\n\n\n\n<li>Apdex\/user satisfaction is calculated.<\/li>\n\n\n\n<li>Detection rules map data correctly.<\/li>\n\n\n\n<li>Privacy settings are correct.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">17. Synthetic Monitoring implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">17.1 What Synthetic Monitoring does<\/h2>\n\n\n\n<p>Synthetic Monitoring simulates availability and user journeys from controlled locations.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">17.2 Synthetic monitor types<\/h2>\n\n\n\n<p>Common types:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>HTTP monitor<\/li>\n\n\n\n<li>Browser monitor<\/li>\n\n\n\n<li>Browser clickpath<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">17.3 Public vs private locations<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Public synthetic locations<\/h3>\n\n\n\n<p>Used to monitor externally available websites and APIs from Dynatrace-managed locations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Private synthetic locations<\/h3>\n\n\n\n<p>Used to monitor internal\/private systems. Usually require ActiveGate.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">17.4 Synthetic implementation questions<\/h2>\n\n\n\n<p>Ask:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What should be tested proactively?<\/li>\n\n\n\n<li>Which APIs need availability checks?<\/li>\n\n\n\n<li>Which user journeys are critical?<\/li>\n\n\n\n<li>Which regions matter?<\/li>\n\n\n\n<li>Are internal apps involved?<\/li>\n\n\n\n<li>Are credentials required?<\/li>\n\n\n\n<li>Should credentials be stored in Credential vault?<\/li>\n\n\n\n<li>How often should checks run?<\/li>\n\n\n\n<li>What failure threshold should trigger alerts?<\/li>\n\n\n\n<li>Which teams receive notifications?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">17.5 Synthetic validation checklist<\/h2>\n\n\n\n<p>Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monitor executes successfully.<\/li>\n\n\n\n<li>Locations are correct.<\/li>\n\n\n\n<li>Frequency is correct.<\/li>\n\n\n\n<li>Authentication works.<\/li>\n\n\n\n<li>Credential vault is used when needed.<\/li>\n\n\n\n<li>Screenshots\/waterfalls are useful.<\/li>\n\n\n\n<li>Failures generate events\/problems as expected.<\/li>\n\n\n\n<li>Alerts route correctly.<\/li>\n\n\n\n<li>Private location ActiveGate is healthy.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">18. Extensions and remote monitoring implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">18.1 Why extensions matter<\/h2>\n\n\n\n<p>Extensions monitor technologies where OneAgent installation is not possible or not sufficient.<\/p>\n\n\n\n<p>Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Network devices<\/li>\n\n\n\n<li>Databases<\/li>\n\n\n\n<li>Appliances<\/li>\n\n\n\n<li>PaaS services<\/li>\n\n\n\n<li>Message brokers<\/li>\n\n\n\n<li>Custom APIs<\/li>\n\n\n\n<li>Cloud services<\/li>\n\n\n\n<li>VMware\/vCenter<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">18.2 Extension architecture<\/h2>\n\n\n\n<p>Extensions often run on ActiveGate and poll remote endpoints.<\/p>\n\n\n\n<p>Implementation requirements:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ActiveGate with extension module<\/li>\n\n\n\n<li>Network access from ActiveGate to target<\/li>\n\n\n\n<li>Credentials in Credential vault<\/li>\n\n\n\n<li>Extension installation<\/li>\n\n\n\n<li>Configuration instance<\/li>\n\n\n\n<li>Metric\/event\/topology mapping<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">18.3 Extension validation<\/h2>\n\n\n\n<p>Verify:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ActiveGate can reach target.<\/li>\n\n\n\n<li>Credentials are valid.<\/li>\n\n\n\n<li>Extension instance is healthy.<\/li>\n\n\n\n<li>Metrics arrive.<\/li>\n\n\n\n<li>Entities appear in topology where applicable.<\/li>\n\n\n\n<li>Alerting works if configured.<\/li>\n\n\n\n<li>Data volume is acceptable.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">18.4 Exam focus<\/h2>\n\n\n\n<p>Know that extensions extend monitoring to remote technologies and often execute from ActiveGate.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">19. Metrics, custom metrics, and events<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">19.1 Custom metric ingestion<\/h2>\n\n\n\n<p>Custom metrics can be pushed to Dynatrace when built-in monitoring does not capture a required measurement.<\/p>\n\n\n\n<p>Use cases:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Business counters<\/li>\n\n\n\n<li>Application-specific health indicators<\/li>\n\n\n\n<li>Queue depth<\/li>\n\n\n\n<li>Batch job duration<\/li>\n\n\n\n<li>Domain-specific KPIs<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">19.2 Metric design principles<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use clear metric names.<\/li>\n\n\n\n<li>Control dimensionality\/cardinality.<\/li>\n\n\n\n<li>Use consistent units.<\/li>\n\n\n\n<li>Avoid high-cardinality labels such as user ID or transaction ID.<\/li>\n\n\n\n<li>Define owner and purpose.<\/li>\n\n\n\n<li>Decide retention and alerting.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">19.3 Events<\/h2>\n\n\n\n<p>Events represent meaningful occurrences, such as deployments, configuration changes, custom alerts, or business\/operational markers.<\/p>\n\n\n\n<p>Use events to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mark deployments<\/li>\n\n\n\n<li>Correlate changes with problems<\/li>\n\n\n\n<li>Trigger alerts or workflows<\/li>\n\n\n\n<li>Add context to incident timelines<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">19.4 Exam focus<\/h2>\n\n\n\n<p>Know that custom metrics and events can extend Dynatrace beyond automatic collection, but must be designed carefully to avoid volume and cardinality problems.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">20. Business events implementation<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">20.1 What business events are<\/h2>\n\n\n\n<p>Business events represent business-relevant actions such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Order placed<\/li>\n\n\n\n<li>Payment failed<\/li>\n\n\n\n<li>Booking completed<\/li>\n\n\n\n<li>Cart abandoned<\/li>\n\n\n\n<li>Loan application submitted<\/li>\n\n\n\n<li>Subscription renewed<\/li>\n\n\n\n<li>Shipment delayed<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">20.2 Why implement business events<\/h2>\n\n\n\n<p>They connect technical telemetry to business impact.<\/p>\n\n\n\n<p>Questions answered:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How many payments failed during the outage?<\/li>\n\n\n\n<li>Which region lost the most orders?<\/li>\n\n\n\n<li>Did a deployment reduce conversion?<\/li>\n\n\n\n<li>Which business process step failed?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">20.3 Implementation paths<\/h2>\n\n\n\n<p>Business events can be ingested through:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>APIs<\/li>\n\n\n\n<li>Logs transformed through OpenPipeline<\/li>\n\n\n\n<li>Application instrumentation<\/li>\n\n\n\n<li>Event sources\/integrations<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">20.4 Design checklist<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Define business event names.<\/li>\n\n\n\n<li>Define required attributes.<\/li>\n\n\n\n<li>Avoid sensitive data.<\/li>\n\n\n\n<li>Define retention.<\/li>\n\n\n\n<li>Define owner.<\/li>\n\n\n\n<li>Define dashboards\/reports.<\/li>\n\n\n\n<li>Validate DQL queries.<\/li>\n\n\n\n<li>Align with business stakeholders.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">21. Deployment validation methodology<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">21.1 Validation dimensions<\/h2>\n\n\n\n<p>Validate implementation in these layers:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Connectivity<\/li>\n\n\n\n<li>Agent health<\/li>\n\n\n\n<li>Infrastructure visibility<\/li>\n\n\n\n<li>Process visibility<\/li>\n\n\n\n<li>Service visibility<\/li>\n\n\n\n<li>Trace visibility<\/li>\n\n\n\n<li>Log visibility<\/li>\n\n\n\n<li>Topology accuracy<\/li>\n\n\n\n<li>User experience visibility<\/li>\n\n\n\n<li>Synthetic availability<\/li>\n\n\n\n<li>Cloud metrics<\/li>\n\n\n\n<li>Kubernetes metadata<\/li>\n\n\n\n<li>Alert generation<\/li>\n\n\n\n<li>Dashboard usability<\/li>\n\n\n\n<li>Security\/privacy<\/li>\n\n\n\n<li>Cost\/volume<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">21.2 Validation checklist<\/h2>\n\n\n\n<p>For each application:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Host appears.<\/li>\n\n\n\n<li>Process appears.<\/li>\n\n\n\n<li>Service appears.<\/li>\n\n\n\n<li>Service calls are detected.<\/li>\n\n\n\n<li>Distributed traces are present.<\/li>\n\n\n\n<li>Database calls appear.<\/li>\n\n\n\n<li>External calls appear.<\/li>\n\n\n\n<li>Logs are correlated.<\/li>\n\n\n\n<li>User actions are linked to backend services.<\/li>\n\n\n\n<li>Smartscape topology is correct.<\/li>\n\n\n\n<li>Problems are generated for test failures if applicable.<\/li>\n\n\n\n<li>Tags are correct.<\/li>\n\n\n\n<li>Management zone\/segment access is correct.<\/li>\n\n\n\n<li>Dashboards show expected data.<\/li>\n\n\n\n<li>Alerts route to correct team.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">21.3 Synthetic validation scenario<\/h2>\n\n\n\n<p>Test:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Application home page loads.<\/li>\n\n\n\n<li>Login flow works.<\/li>\n\n\n\n<li>Search works.<\/li>\n\n\n\n<li>Checkout\/payment path works in test environment.<\/li>\n\n\n\n<li>API health endpoint returns expected status.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">21.4 Failure injection for validation<\/h2>\n\n\n\n<p>Where safe, test:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Service latency increase<\/li>\n\n\n\n<li>Controlled HTTP 500<\/li>\n\n\n\n<li>Database dependency slowdown<\/li>\n\n\n\n<li>Host CPU\/memory pressure in non-prod<\/li>\n\n\n\n<li>Synthetic endpoint failure<\/li>\n\n\n\n<li>Log error generation<\/li>\n\n\n\n<li>Deployment event correlation<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">22. Implementation troubleshooting framework<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">22.1 Troubleshooting sequence<\/h2>\n\n\n<pre class=\"wp-block-code\"><span><code class=\"hljs\">Is data generated?\n  \u2193\nIs data collected?\n  \u2193\nIs data routed?\n  \u2193\nIs data accepted?\n  \u2193\nIs data processed?\n  \u2193\nIs data stored?\n  \u2193\nIs data visible?\n  \u2193\nIs data correlated?\n<\/code><\/span><\/pre>\n\n\n<h2 class=\"wp-block-heading\">22.2 Common root causes<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Missing token or wrong scope<\/li>\n\n\n\n<li>Invalid API URL<\/li>\n\n\n\n<li>Firewall\/proxy issue<\/li>\n\n\n\n<li>ActiveGate unreachable<\/li>\n\n\n\n<li>Wrong network zone<\/li>\n\n\n\n<li>Unsupported technology<\/li>\n\n\n\n<li>Process restart not performed<\/li>\n\n\n\n<li>Kubernetes webhook not injecting<\/li>\n\n\n\n<li>Missing RBAC or cloud IAM permissions<\/li>\n\n\n\n<li>Wrong OTLP endpoint path<\/li>\n\n\n\n<li>High-cardinality metrics rejected or expensive<\/li>\n\n\n\n<li>Log include\/exclude rules too restrictive<\/li>\n\n\n\n<li>OpenPipeline drops or routes data incorrectly<\/li>\n\n\n\n<li>Bucket access missing<\/li>\n\n\n\n<li>RUM detection rule mismatch<\/li>\n\n\n\n<li>Synthetic credentials invalid<\/li>\n\n\n\n<li>Privacy masking rules too broad<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">22.3 Practical troubleshooting examples<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">OneAgent installed but no service data<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Full-stack mode enabled<\/li>\n\n\n\n<li>Supported runtime<\/li>\n\n\n\n<li>Code module injection<\/li>\n\n\n\n<li>Process restarted<\/li>\n\n\n\n<li>Deep monitoring settings<\/li>\n\n\n\n<li>Container\/Kubernetes injection rules<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Kubernetes services missing<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>DynaKube mode<\/li>\n\n\n\n<li>Namespace selector<\/li>\n\n\n\n<li>Annotations<\/li>\n\n\n\n<li>Webhook health<\/li>\n\n\n\n<li>Pod restart<\/li>\n\n\n\n<li>CSI driver<\/li>\n\n\n\n<li>Security policies<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">OTLP traces missing<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Endpoint URL and path<\/li>\n\n\n\n<li>Token scope<\/li>\n\n\n\n<li>Collector exporter config<\/li>\n\n\n\n<li>TLS\/proxy<\/li>\n\n\n\n<li>Compression settings<\/li>\n\n\n\n<li>Service name\/resource attributes<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Logs missing<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Log module installed<\/li>\n\n\n\n<li>Include rules<\/li>\n\n\n\n<li>File permissions<\/li>\n\n\n\n<li>Namespace filters<\/li>\n\n\n\n<li>OpenPipeline route\/drop rule<\/li>\n\n\n\n<li>Bucket access<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Synthetic private check failing<\/h3>\n\n\n\n<p>Check:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>ActiveGate health<\/li>\n\n\n\n<li>Private location config<\/li>\n\n\n\n<li>DNS<\/li>\n\n\n\n<li>Firewall<\/li>\n\n\n\n<li>Credential vault<\/li>\n\n\n\n<li>Proxy<\/li>\n\n\n\n<li>Target app availability<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">23. Implementation handover<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">23.1 Handover deliverables<\/h2>\n\n\n\n<p>A complete implementation handover should include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Architecture diagram<\/li>\n\n\n\n<li>Deployment inventory<\/li>\n\n\n\n<li>OneAgent rollout status<\/li>\n\n\n\n<li>ActiveGate inventory<\/li>\n\n\n\n<li>Network zone design<\/li>\n\n\n\n<li>Kubernetes DynaKube\/Operator configuration<\/li>\n\n\n\n<li>Cloud integration configuration summary<\/li>\n\n\n\n<li>OpenTelemetry ingestion design<\/li>\n\n\n\n<li>Log ingestion and bucket strategy<\/li>\n\n\n\n<li>OpenPipeline rules<\/li>\n\n\n\n<li>Tagging standard<\/li>\n\n\n\n<li>Management zone\/segment design<\/li>\n\n\n\n<li>Alerting profile design<\/li>\n\n\n\n<li>Synthetic monitor list<\/li>\n\n\n\n<li>RUM application list<\/li>\n\n\n\n<li>Dashboard list<\/li>\n\n\n\n<li>Workflow\/integration list<\/li>\n\n\n\n<li>Token\/OAuth\/service user inventory<\/li>\n\n\n\n<li>Credential vault usage summary<\/li>\n\n\n\n<li>Cost and consumption baseline<\/li>\n\n\n\n<li>Validation results<\/li>\n\n\n\n<li>Known limitations<\/li>\n\n\n\n<li>Operational runbooks<\/li>\n\n\n\n<li>Ownership matrix<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">23.2 Handover training topics<\/h2>\n\n\n\n<p>Train operations teams on:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How to find hosts, services, logs, traces, and problems<\/li>\n\n\n\n<li>How to investigate a problem<\/li>\n\n\n\n<li>How to use dashboards and notebooks<\/li>\n\n\n\n<li>How to run DQL basics<\/li>\n\n\n\n<li>How alert routing works<\/li>\n\n\n\n<li>How to identify owners through tags<\/li>\n\n\n\n<li>How to handle agent\/ActiveGate health issues<\/li>\n\n\n\n<li>How to add new applications to monitoring<\/li>\n\n\n\n<li>How to request new log ingestion<\/li>\n\n\n\n<li>How to avoid cost spikes<\/li>\n\n\n\n<li>How to handle privacy incidents<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">23.3 Post-implementation review<\/h2>\n\n\n\n<p>Review:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Did implementation meet requirements?<\/li>\n\n\n\n<li>Are critical apps monitored?<\/li>\n\n\n\n<li>Are logs useful and controlled?<\/li>\n\n\n\n<li>Are alerts actionable?<\/li>\n\n\n\n<li>Are dashboards adopted?<\/li>\n\n\n\n<li>Are owners assigned?<\/li>\n\n\n\n<li>Are costs acceptable?<\/li>\n\n\n\n<li>Are there unsupported technologies?<\/li>\n\n\n\n<li>What should be improved in the next phase?<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">24. Implementation Professional hands-on lab checklist<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">24.1 OneAgent labs<\/h2>\n\n\n\n<p>You should be able to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explain OneAgent purpose.<\/li>\n\n\n\n<li>Explain supported deployment targets.<\/li>\n\n\n\n<li>Install OneAgent conceptually.<\/li>\n\n\n\n<li>Assign host group.<\/li>\n\n\n\n<li>Assign network zone.<\/li>\n\n\n\n<li>Configure proxy conceptually.<\/li>\n\n\n\n<li>Validate host, process, service, trace, and log visibility.<\/li>\n\n\n\n<li>Troubleshoot missing data.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">24.2 ActiveGate labs<\/h2>\n\n\n\n<p>You should be able to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explain ActiveGate use cases.<\/li>\n\n\n\n<li>Design ActiveGate placement.<\/li>\n\n\n\n<li>Explain modules.<\/li>\n\n\n\n<li>Configure ActiveGate conceptually for routing.<\/li>\n\n\n\n<li>Explain sealed network use.<\/li>\n\n\n\n<li>Explain ActiveGate use for cloud, Kubernetes, OTLP, private synthetic, and extensions.<\/li>\n\n\n\n<li>Validate ActiveGate health.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">24.3 Kubernetes labs<\/h2>\n\n\n\n<p>You should be able to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explain Dynatrace Operator.<\/li>\n\n\n\n<li>Explain DynaKube.<\/li>\n\n\n\n<li>Compare deployment modes.<\/li>\n\n\n\n<li>Explain namespace selectors and annotations.<\/li>\n\n\n\n<li>Explain CSI driver and webhook roles.<\/li>\n\n\n\n<li>Explain ActiveGate role in Kubernetes monitoring.<\/li>\n\n\n\n<li>Validate cluster, node, workload, pod, service, trace, and log data.<\/li>\n\n\n\n<li>Troubleshoot missing injection.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">24.4 OpenTelemetry labs<\/h2>\n\n\n\n<p>You should be able to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explain OTLP endpoints.<\/li>\n\n\n\n<li>Explain SaaS vs ActiveGate vs Collector ingestion.<\/li>\n\n\n\n<li>Configure traces conceptually.<\/li>\n\n\n\n<li>Explain metrics\/logs ingestion.<\/li>\n\n\n\n<li>Validate spans in distributed traces.<\/li>\n\n\n\n<li>Explain service.name and resource attributes.<\/li>\n\n\n\n<li>Troubleshoot missing spans.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">24.5 Log\/OpenPipeline labs<\/h2>\n\n\n\n<p>You should be able to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explain log sources.<\/li>\n\n\n\n<li>Configure include\/exclude conceptually.<\/li>\n\n\n\n<li>Explain bucket routing.<\/li>\n\n\n\n<li>Explain retention strategy.<\/li>\n\n\n\n<li>Create sample OpenPipeline processor conceptually.<\/li>\n\n\n\n<li>Explain masking.<\/li>\n\n\n\n<li>Validate logs with DQL.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">24.6 RUM\/Synthetic labs<\/h2>\n\n\n\n<p>You should be able to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explain auto-injection vs manual RUM.<\/li>\n\n\n\n<li>Explain application detection rules.<\/li>\n\n\n\n<li>Explain privacy settings.<\/li>\n\n\n\n<li>Create HTTP monitor conceptually.<\/li>\n\n\n\n<li>Create browser\/clickpath monitor conceptually.<\/li>\n\n\n\n<li>Explain private locations and ActiveGate.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">24.7 Cloud\/extensions labs<\/h2>\n\n\n\n<p>You should be able to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Explain cloud integration requirements.<\/li>\n\n\n\n<li>Explain least-privilege cloud permissions.<\/li>\n\n\n\n<li>Explain ActiveGate need for cloud\/remote integrations.<\/li>\n\n\n\n<li>Explain extension execution from ActiveGate.<\/li>\n\n\n\n<li>Validate metrics and topology from remote systems.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">25. 21-day study plan<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">Day 1: Certification orientation<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Review current Dynatrace University Implementation Professional Learning Plan.<\/li>\n\n\n\n<li>Verify exam details.<\/li>\n\n\n\n<li>Review Associate and Administration basics.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 2: Implementation lifecycle<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study discovery, design, deployment, validation, optimization, handover.<\/li>\n\n\n\n<li>Create a sample implementation project plan.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 3: OneAgent architecture<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study OneAgent capabilities and deployment targets.<\/li>\n\n\n\n<li>Review supported technologies and monitoring modes.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 4: OneAgent rollout<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study host groups, network zones, proxies, install parameters, validation.<\/li>\n\n\n\n<li>Practice troubleshooting missing host\/service data.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 5: ActiveGate architecture<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study routing, sealed networks, modules, cloud integrations, extensions, private synthetic, OTLP.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 6: Network zones<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Design zones for a multi-region deployment.<\/li>\n\n\n\n<li>Practice alternative-zone design.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 7: Kubernetes Operator<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study Operator, DynaKube, webhook, CSI driver, ActiveGate.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 8: Kubernetes deployment modes<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Compare cloudNativeFullStack, classicFullStack, applicationMonitoring, hostMonitoring.<\/li>\n\n\n\n<li>Practice selecting a mode from scenarios.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 9: Kubernetes troubleshooting<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study namespace selectors, annotations, pod injection, logs, metadata enrichment.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 10: Cloud integrations<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study AWS\/Azure\/GCP design patterns, permissions, ActiveGate requirements, tagging.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 11: OpenTelemetry<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study OTLP endpoints, Collector, OneAgent OTel, traces\/metrics\/logs, resource attributes.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 12: Logs<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study OneAgent logs, Kubernetes logs, OTel logs, API logs, log planning.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 13: OpenPipeline<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study routes, pipelines, processors, masking, enrichment, bucket routing.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 14: Grail, buckets, retention<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study bucket strategy, data access, retention, query behavior, cost control.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 15: Tags, zones, ownership<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study tag standards, management zones, segments, security context.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 16: RUM implementation<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study auto-injection, manual injection, detection rules, privacy, validation.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 17: Synthetic implementation<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study HTTP, browser, clickpath, public\/private locations, credentials, alerting.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 18: Extensions and remote monitoring<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Study remote technologies, ActiveGate execution, credentials, metrics\/topology.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 19: Validation and troubleshooting<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Practice end-to-end validation and common failure scenarios.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 20: Handover and operations<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Build an implementation handover package.<\/li>\n\n\n\n<li>Review dashboards, alerts, ownership, cost baselines.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Day 21: Mock exam and final review<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Answer practice questions.<\/li>\n\n\n\n<li>Revisit weak areas.<\/li>\n\n\n\n<li>Verify current exam format in Dynatrace University.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">26. Final revision cheat sheet<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">26.1 Component cheat sheet<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Area<\/th><th>Implementation meaning<\/th><\/tr><\/thead><tbody><tr><td>OneAgent<\/td><td>Primary automatic collection and instrumentation component<\/td><\/tr><tr><td>ActiveGate<\/td><td>Secure gateway, routing point, integration host, private location support<\/td><\/tr><tr><td>Network zones<\/td><td>Efficient OneAgent\/ActiveGate routing by network structure<\/td><\/tr><tr><td>Host groups<\/td><td>Organize hosts and influence settings\/process\/service grouping<\/td><\/tr><tr><td>Dynatrace Operator<\/td><td>Kubernetes lifecycle and deployment manager<\/td><\/tr><tr><td>DynaKube<\/td><td>Kubernetes custom resource for Dynatrace configuration<\/td><\/tr><tr><td>cloudNativeFullStack<\/td><td>Kubernetes infrastructure + app monitoring with injection<\/td><\/tr><tr><td>applicationMonitoring<\/td><td>Selective app\/pod monitoring in Kubernetes<\/td><\/tr><tr><td>hostMonitoring<\/td><td>Kubernetes node\/host-level monitoring without app injection<\/td><\/tr><tr><td>OpenTelemetry<\/td><td>Vendor-neutral traces, metrics, logs ingestion<\/td><\/tr><tr><td>OTLP endpoints<\/td><td>SaaS, ActiveGate, or Collector-based OTel ingest paths<\/td><\/tr><tr><td>OpenPipeline<\/td><td>Ingest processing, filtering, masking, enrichment, routing<\/td><\/tr><tr><td>Grail buckets<\/td><td>Data storage, retention, and access organization<\/td><\/tr><tr><td>Logs<\/td><td>High-value\/high-volume data requiring governance<\/td><\/tr><tr><td>RUM<\/td><td>Real-user experience monitoring<\/td><\/tr><tr><td>Synthetic<\/td><td>Proactive availability and journey monitoring<\/td><\/tr><tr><td>Extensions<\/td><td>Remote technology monitoring, often via ActiveGate<\/td><\/tr><tr><td>Tags<\/td><td>Ownership, filtering, alerting, dashboards, zones<\/td><\/tr><tr><td>Management zones<\/td><td>Classic entity\/data scoping for teams<\/td><\/tr><tr><td>Segments\/security context<\/td><td>Latest access-scoping model for platform\/Grail contexts<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">26.2 Deployment decision cheat sheet<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Requirement<\/th><th>Likely choice<\/th><\/tr><\/thead><tbody><tr><td>Full VM\/app visibility<\/td><td>OneAgent full-stack<\/td><\/tr><tr><td>Host metrics only<\/td><td>Infrastructure monitoring<\/td><\/tr><tr><td>Initial asset inventory<\/td><td>Discovery mode<\/td><\/tr><tr><td>Private\/sealed network<\/td><td>ActiveGate routing<\/td><\/tr><tr><td>Multi-region egress optimization<\/td><td>Network zones<\/td><\/tr><tr><td>Kubernetes full visibility<\/td><td>Dynatrace Operator + cloudNativeFullStack<\/td><\/tr><tr><td>Kubernetes selected apps only<\/td><td>applicationMonitoring + namespace selectors\/annotations<\/td><\/tr><tr><td>Existing OTel apps<\/td><td>OTLP to SaaS\/ActiveGate\/Collector<\/td><\/tr><tr><td>Remote network device<\/td><td>Extension via ActiveGate<\/td><\/tr><tr><td>Internal synthetic journey<\/td><td>Private Synthetic location + ActiveGate<\/td><\/tr><tr><td>Sensitive log data<\/td><td>Mask at capture\/OpenPipeline<\/td><\/tr><tr><td>High log volume<\/td><td>Filter\/route\/drop through OpenPipeline and buckets<\/td><\/tr><tr><td>Team ownership<\/td><td>Tags + zones\/segments<\/td><\/tr><tr><td>Config at scale<\/td><td>Monaco\/GitOps\/IaC<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">26.3 Troubleshooting cheat sheet<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Symptom<\/th><th>Check<\/th><\/tr><\/thead><tbody><tr><td>Host missing<\/td><td>Install status, token, API URL, firewall, proxy, ActiveGate<\/td><\/tr><tr><td>Service missing<\/td><td>Monitoring mode, supported runtime, code module, process restart<\/td><\/tr><tr><td>Wrong routing<\/td><td>Network zone, ActiveGate zone, alternatives, connectivity<\/td><\/tr><tr><td>Kubernetes pod not injected<\/td><td>DynaKube mode, webhook, namespace selector, annotations, pod restart<\/td><\/tr><tr><td>Logs missing<\/td><td>Log module, include\/exclude rules, permissions, OpenPipeline, bucket<\/td><\/tr><tr><td>OTel data missing<\/td><td>Endpoint path, token, collector config, service.name, compression<\/td><\/tr><tr><td>RUM missing<\/td><td>Injection, JavaScript tag, CSP, detection rule, app config<\/td><\/tr><tr><td>Synthetic failure<\/td><td>Location, DNS, credential, proxy, firewall, target app<\/td><\/tr><tr><td>Extension missing metrics<\/td><td>ActiveGate module, credentials, network, target API<\/td><\/tr><tr><td>High cost<\/td><td>Log volume, retention, OTel cardinality, synthetic frequency, cloud scope<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">27. Practice questions<\/h1>\n\n\n\n<h2 class=\"wp-block-heading\">Question 1<\/h2>\n\n\n\n<p>What is the main purpose of Dynatrace Implementation Professional Certification?<\/p>\n\n\n\n<p>A. To validate that a person can only view dashboards<br>B. To validate that a person can architect, plan, implement Dynatrace, and manage data ingestion<br>C. To validate graphic design skills<br>D. To validate payroll administration<\/p>\n\n\n\n<p><strong>Answer: B. To validate that a person can architect, plan, implement Dynatrace, and manage data ingestion<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 2<\/h2>\n\n\n\n<p>Which component is installed on hosts to automatically collect monitoring data and instrument supported application stacks?<\/p>\n\n\n\n<p>A. OneAgent<br>B. Dashboard<br>C. Credential vault<br>D. Alerting profile<\/p>\n\n\n\n<p><strong>Answer: A. OneAgent<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 3<\/h2>\n\n\n\n<p>Which component is commonly used to reduce firewall complexity and route OneAgent traffic through a local point?<\/p>\n\n\n\n<p>A. ActiveGate<br>B. PurePath<br>C. Apdex<br>D. Notebook<\/p>\n\n\n\n<p><strong>Answer: A. ActiveGate<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 4<\/h2>\n\n\n\n<p>What do network zones help optimize?<\/p>\n\n\n\n<p>A. OneAgent-to-ActiveGate routing across network regions<br>B. Dashboard font size<br>C. User passwords<br>D. JavaScript syntax<\/p>\n\n\n\n<p><strong>Answer: A. OneAgent-to-ActiveGate routing across network regions<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 5<\/h2>\n\n\n\n<p>Which Kubernetes component manages the rollout and lifecycle of Dynatrace components?<\/p>\n\n\n\n<p>A. Dynatrace Operator<br>B. Synthetic HTTP monitor<br>C. Dashboard tile<br>D. Alerting profile<\/p>\n\n\n\n<p><strong>Answer: A. Dynatrace Operator<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 6<\/h2>\n\n\n\n<p>What is DynaKube?<\/p>\n\n\n\n<p>A. A Kubernetes custom resource used to configure Dynatrace Operator<br>B. A log line format<br>C. A user group<br>D. A cloud billing unit<\/p>\n\n\n\n<p><strong>Answer: A. A Kubernetes custom resource used to configure Dynatrace Operator<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 7<\/h2>\n\n\n\n<p>Which Kubernetes mode is best for full infrastructure and application observability with OneAgent injection?<\/p>\n\n\n\n<p>A. cloudNativeFullStack<br>B. Dashboard-only mode<br>C. Manual-only mode<br>D. SAML mode<\/p>\n\n\n\n<p><strong>Answer: A. cloudNativeFullStack<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 8<\/h2>\n\n\n\n<p>Which mode is useful when only selected Kubernetes applications should be monitored?<\/p>\n\n\n\n<p>A. applicationMonitoring<br>B. Full tenant admin mode<br>C. Synthetic public mode<br>D. Credential vault mode<\/p>\n\n\n\n<p><strong>Answer: A. applicationMonitoring<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 9<\/h2>\n\n\n\n<p>Which protocol is used for OpenTelemetry telemetry exchange?<\/p>\n\n\n\n<p>A. OTLP<br>B. SMTP<br>C. FTP<br>D. POP3<\/p>\n\n\n\n<p><strong>Answer: A. OTLP<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 10<\/h2>\n\n\n\n<p>Dynatrace OTLP ingestion can be done through which services?<\/p>\n\n\n\n<p>A. Dynatrace SaaS platform, ActiveGate, or Dynatrace Collector<br>B. Only a printer driver<br>C. Only a spreadsheet<br>D. Only a browser bookmark<\/p>\n\n\n\n<p><strong>Answer: A. Dynatrace SaaS platform, ActiveGate, or Dynatrace Collector<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 11<\/h2>\n\n\n\n<p>What is OpenPipeline used for?<\/p>\n\n\n\n<p>A. Processing, filtering, masking, enriching, and routing telemetry<br>B. Restarting physical servers only<br>C. Creating user passwords<br>D. Recording videos<\/p>\n\n\n\n<p><strong>Answer: A. Processing, filtering, masking, enriching, and routing telemetry<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 12<\/h2>\n\n\n\n<p>Which OpenPipeline processor concept can remove records from ingestion?<\/p>\n\n\n\n<p>A. Drop record<br>B. Browser click<br>C. Service flow<br>D. Credential vault<\/p>\n\n\n\n<p><strong>Answer: A. Drop record<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 13<\/h2>\n\n\n\n<p>What is a good reason to use buckets in Grail?<\/p>\n\n\n\n<p>A. To organize data by retention, access, and use case<br>B. To draw architecture diagrams<br>C. To install OneAgent<br>D. To configure SAML<\/p>\n\n\n\n<p><strong>Answer: A. To organize data by retention, access, and use case<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 14<\/h2>\n\n\n\n<p>What is a common implementation risk with logs?<\/p>\n\n\n\n<p>A. High volume, high cost, or sensitive data exposure<br>B. Logs always reduce cost automatically<br>C. Logs never contain sensitive data<br>D. Logs cannot be queried<\/p>\n\n\n\n<p><strong>Answer: A. High volume, high cost, or sensitive data exposure<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 15<\/h2>\n\n\n\n<p>Which approach is strongest when sensitive data must never leave the monitored environment?<\/p>\n\n\n\n<p>A. Mask at capture<br>B. Mask only in dashboard titles<br>C. Do not mask<br>D. Rename the dashboard<\/p>\n\n\n\n<p><strong>Answer: A. Mask at capture<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 16<\/h2>\n\n\n\n<p>What is Real User Monitoring used for?<\/p>\n\n\n\n<p>A. Monitoring actual user sessions and user actions<br>B. Monitoring only ActiveGate CPU<br>C. Creating OAuth clients<br>D. Managing DNS records<\/p>\n\n\n\n<p><strong>Answer: A. Monitoring actual user sessions and user actions<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 17<\/h2>\n\n\n\n<p>When would a private synthetic location be required?<\/p>\n\n\n\n<p>A. When testing internal\/private applications not reachable from public locations<br>B. When creating a user group<br>C. When editing a dashboard title<br>D. When creating a notebook<\/p>\n\n\n\n<p><strong>Answer: A. When testing internal\/private applications not reachable from public locations<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 18<\/h2>\n\n\n\n<p>Where are private Synthetic locations commonly hosted?<\/p>\n\n\n\n<p>A. ActiveGate<br>B. A dashboard tile<br>C. A user session<br>D. A browser bookmark<\/p>\n\n\n\n<p><strong>Answer: A. ActiveGate<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 19<\/h2>\n\n\n\n<p>What are extensions commonly used for?<\/p>\n\n\n\n<p>A. Monitoring remote technologies where OneAgent is not installed or insufficient<br>B. Formatting text<br>C. Creating local users only<br>D. Changing dashboard color<\/p>\n\n\n\n<p><strong>Answer: A. Monitoring remote technologies where OneAgent is not installed or insufficient<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 20<\/h2>\n\n\n\n<p>Which metadata source is commonly useful for tagging Kubernetes telemetry?<\/p>\n\n\n\n<p>A. Kubernetes labels and annotations<br>B. Desktop wallpaper<br>C. Email signatures<br>D. Browser history<\/p>\n\n\n\n<p><strong>Answer: A. Kubernetes labels and annotations<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 21<\/h2>\n\n\n\n<p>A host is visible but a Java service is not deeply monitored. What should you check?<\/p>\n\n\n\n<p>A. Monitoring mode, supported technology, code module injection, and process restart<br>B. Dashboard theme<br>C. User display name<br>D. Calendar settings<\/p>\n\n\n\n<p><strong>Answer: A. Monitoring mode, supported technology, code module injection, and process restart<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 22<\/h2>\n\n\n\n<p>An OTel trace is not arriving in Dynatrace. What should you check first?<\/p>\n\n\n\n<p>A. Endpoint path, token scope, exporter\/collector config, and service.name<br>B. Dashboard title<br>C. Host group naming only<br>D. User avatar<\/p>\n\n\n\n<p><strong>Answer: A. Endpoint path, token scope, exporter\/collector config, and service.name<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 23<\/h2>\n\n\n\n<p>What is the best implementation approach for alert ownership?<\/p>\n\n\n\n<p>A. Use consistent ownership tags and route alerts by team\/application scope<br>B. Send every alert to every team<br>C. Disable all alerts<br>D. Only create dashboards<\/p>\n\n\n\n<p><strong>Answer: A. Use consistent ownership tags and route alerts by team\/application scope<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 24<\/h2>\n\n\n\n<p>What is a good first rollout approach for a large enterprise?<\/p>\n\n\n\n<p>A. Pilot non-production, validate, tune, then roll out production in waves<br>B. Install everywhere at once with no validation<br>C. Enable all logs forever<br>D. Disable all privacy controls<\/p>\n\n\n\n<p><strong>Answer: A. Pilot non-production, validate, tune, then roll out production in waves<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 25<\/h2>\n\n\n\n<p>What should be included in implementation handover?<\/p>\n\n\n\n<p>A. Architecture, inventory, configuration, validation results, runbooks, ownership, and known limitations<br>B. Only a screenshot of the login page<br>C. Only a list of user names<br>D. Only a dashboard title<\/p>\n\n\n\n<p><strong>Answer: A. Architecture, inventory, configuration, validation results, runbooks, ownership, and known limitations<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 26<\/h2>\n\n\n\n<p>What is the purpose of application detection rules in RUM?<\/p>\n\n\n\n<p>A. To map RUM data to the correct web application<br>B. To create host groups<br>C. To configure ActiveGate zones<br>D. To query Grail buckets<\/p>\n\n\n\n<p><strong>Answer: A. To map RUM data to the correct web application<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 27<\/h2>\n\n\n\n<p>Which implementation choice helps control high-cardinality custom metrics?<\/p>\n\n\n\n<p>A. Limit dimensions and avoid values like user ID or transaction ID<br>B. Add every possible field as a dimension<br>C. Use random metric names<br>D. Disable all metrics<\/p>\n\n\n\n<p><strong>Answer: A. Limit dimensions and avoid values like user ID or transaction ID<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 28<\/h2>\n\n\n\n<p>Which implementation component is best suited for routing payment logs to a dedicated 90-day bucket?<\/p>\n\n\n\n<p>A. OpenPipeline<br>B. Smartscape only<br>C. Apdex only<br>D. Synthetic screenshot<\/p>\n\n\n\n<p><strong>Answer: A. OpenPipeline<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 29<\/h2>\n\n\n\n<p>Which validation proves backend visibility from a user action?<\/p>\n\n\n\n<p>A. A RUM user action links to backend service traces<br>B. A user has a profile picture<br>C. A dashboard title is correct<br>D. A host group exists but no data appears<\/p>\n\n\n\n<p><strong>Answer: A. A RUM user action links to backend service traces<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Question 30<\/h2>\n\n\n\n<p>What is the most important implementation mindset?<\/p>\n\n\n\n<p>A. Requirements \u2192 architecture \u2192 deployment \u2192 validation \u2192 optimization \u2192 handover<br>B. Install everything with no design<br>C. Ignore privacy and cost<br>D. Only memorize names<\/p>\n\n\n\n<p><strong>Answer: A. Requirements \u2192 architecture \u2192 deployment \u2192 validation \u2192 optimization \u2192 handover<\/strong><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">28. Final readiness checklist<\/h1>\n\n\n\n<p>You are ready for Implementation Professional when you can confidently explain and apply:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Implementation lifecycle<\/li>\n\n\n\n<li>Requirements discovery<\/li>\n\n\n\n<li>Architecture design<\/li>\n\n\n\n<li>OneAgent deployment planning<\/li>\n\n\n\n<li>OneAgent monitoring modes<\/li>\n\n\n\n<li>Host groups<\/li>\n\n\n\n<li>ActiveGate use cases<\/li>\n\n\n\n<li>ActiveGate modules and placement<\/li>\n\n\n\n<li>Network zones and alternatives<\/li>\n\n\n\n<li>Kubernetes Operator<\/li>\n\n\n\n<li>DynaKube<\/li>\n\n\n\n<li>Kubernetes monitoring modes<\/li>\n\n\n\n<li>Namespace selectors and annotations<\/li>\n\n\n\n<li>Kubernetes log monitoring<\/li>\n\n\n\n<li>Kubernetes metadata enrichment<\/li>\n\n\n\n<li>GitOps deployment concepts<\/li>\n\n\n\n<li>Cloud integrations<\/li>\n\n\n\n<li>Cloud IAM\/permissions concepts<\/li>\n\n\n\n<li>OpenTelemetry\/OTLP ingestion<\/li>\n\n\n\n<li>Dynatrace SaaS vs ActiveGate vs Collector OTel paths<\/li>\n\n\n\n<li>OpenTelemetry troubleshooting<\/li>\n\n\n\n<li>Log ingestion planning<\/li>\n\n\n\n<li>Log masking<\/li>\n\n\n\n<li>OpenPipeline routes and processors<\/li>\n\n\n\n<li>Buckets and retention<\/li>\n\n\n\n<li>Cost control for logs\/metrics\/traces\/synthetic\/RUM<\/li>\n\n\n\n<li>RUM implementation<\/li>\n\n\n\n<li>Synthetic implementation<\/li>\n\n\n\n<li>Private synthetic locations<\/li>\n\n\n\n<li>Extensions and remote monitoring<\/li>\n\n\n\n<li>Tags and ownership<\/li>\n\n\n\n<li>Management zones<\/li>\n\n\n\n<li>Segments\/security context<\/li>\n\n\n\n<li>Custom metrics<\/li>\n\n\n\n<li>Events and business events<\/li>\n\n\n\n<li>Deployment validation<\/li>\n\n\n\n<li>Implementation troubleshooting<\/li>\n\n\n\n<li>Handover and operationalization<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">29. Last-minute memory map<\/h1>\n\n\n<pre class=\"wp-block-code\" aria-describedby=\"shcb-language-9\" data-shcb-language-name=\"JavaScript\" data-shcb-language-slug=\"javascript\"><span><code class=\"hljs language-javascript\">Implementation = Design + Deploy + Validate + Optimize + Handover\n\n<span class=\"hljs-attr\">Collect<\/span>:\n  OneAgent\n  Dynatrace Operator\n  RUM JavaScript\n  Synthetic monitors\n  Extensions\n  OpenTelemetry\n  APIs\n\n<span class=\"hljs-attr\">Route<\/span>:\n  Direct SaaS\n  ActiveGate\n  <span class=\"hljs-built_in\">Proxy<\/span>\n  Network zones\n  Dynatrace Collector\n\n<span class=\"hljs-attr\">Process<\/span>:\n  OpenPipeline\n  Mask\n  Drop\n  Parse\n  Enrich\n  Route\n\n<span class=\"hljs-attr\">Store<\/span>:\n  Grail\n  Buckets\n  Retention\n  Access controls\n\n<span class=\"hljs-attr\">Organize<\/span>:\n  Tags\n  Host groups\n  Management zones\n  Segments\n  Security context\n\n<span class=\"hljs-attr\">Validate<\/span>:\n  Host \u2192 Process \u2192 Service \u2192 Trace \u2192 Logs \u2192 Topology \u2192 User Actions \u2192 Problems \u2192 Dashboards\n\n<span class=\"hljs-attr\">Operate<\/span>:\n  Alerts\n  Workflows\n  Dashboards\n  Runbooks\n  Ownership\n  Cost monitoring\n<\/code><\/span><small class=\"shcb-language\" id=\"shcb-language-9\"><span class=\"shcb-language__label\">Code language:<\/span> <span class=\"shcb-language__name\">JavaScript<\/span> <span class=\"shcb-language__paren\">(<\/span><span class=\"shcb-language__slug\">javascript<\/span><span class=\"shcb-language__paren\">)<\/span><\/small><\/pre>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">30. Final advice<\/h1>\n\n\n\n<p>Implementation Professional is about thinking like a delivery architect.<\/p>\n\n\n\n<p>Do not only memorize component names. Practice choosing the right implementation pattern from a requirement.<\/p>\n\n\n\n<p>Examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>No internet from hosts?<\/strong> Use ActiveGate\/proxy design.<\/li>\n\n\n\n<li><strong>Multi-region enterprise?<\/strong> Use network zones and local ActiveGates.<\/li>\n\n\n\n<li><strong>Kubernetes full visibility?<\/strong> Use Dynatrace Operator with cloudNativeFullStack.<\/li>\n\n\n\n<li><strong>Selected Kubernetes apps only?<\/strong> Use applicationMonitoring with selectors\/annotations.<\/li>\n\n\n\n<li><strong>Existing OTel instrumentation?<\/strong> Configure OTLP to SaaS, ActiveGate, or Collector.<\/li>\n\n\n\n<li><strong>High log volume?<\/strong> Use OpenPipeline, bucket routing, retention, and filtering.<\/li>\n\n\n\n<li><strong>Sensitive data?<\/strong> Mask at capture or processing before storage.<\/li>\n\n\n\n<li><strong>Need team ownership?<\/strong> Use tags, zones, segments, and alert routing.<\/li>\n\n\n\n<li><strong>Need internal journey checks?<\/strong> Use private Synthetic location with ActiveGate.<\/li>\n\n\n\n<li><strong>Need remote technology monitoring?<\/strong> Use extensions running from ActiveGate.<\/li>\n<\/ul>\n\n\n\n<p>A successful Dynatrace implementation is not finished when the agent is installed. It is finished when the customer can reliably observe, troubleshoot, govern, and operate their systems using the platform.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Last verified: April 24, 2026Audience: Dynatrace implementers, observability engineers, SREs, platform engineers, consultants, delivery engineers, cloud\/Kubernetes engineers, and anyone preparing for Dynatrace Implementation Professional Certification. 0. What this guide is&#8230; <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[11138],"tags":[],"class_list":["post-75233","post","type-post","status-publish","format-standard","hentry","category-best-tools"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75233","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=75233"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75233\/revisions"}],"predecessor-version":[{"id":75234,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/75233\/revisions\/75234"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=75233"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=75233"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=75233"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}