Dynatrace Professional key terms

A generative AI assistant embedded in the Dynatrace platform that answers natural-language questions about your environment, explains findings, and drafts queries or dashboards from conversational prompts.

Dynatrace's causal, deterministic AI engine that baselines behavior, detects anomalies, and correlates them into a single root-cause explanation rather than isolated alerts.

Machine-learning capability that forecasts future behavior such as capacity exhaustion or failure risk, distinct from Davis's causal detection of conditions that already occurred.

Continuous comparison of observed metrics against learned seasonal baselines to flag statistically unusual behavior without fixed static thresholds.

A learned model of normal behavior for a metric or entity, adjusted for time-of-day and weekday patterns, used as the reference for anomaly detection.

The process of tracing a user-visible symptom back through the dependency chain to the single faulty component, service, or infrastructure element responsible.

Dynatrace's real-time topology model of hosts, processes, services, and applications and their dependencies, which underpins correlation and impact analysis.

A captured end-to-end transaction trace showing every method, service call, and database statement with timing, used for code-level diagnosis.

Propagation of a trace context across service and process boundaries so a single request can be reconstructed end to end in a microservices architecture.

A single timed operation within a trace, with attributes and parent-child relationships, forming the building blocks of OpenTelemetry-based trace analysis.

Vendor-neutral open standard for producing and exporting traces, metrics, and logs; Dynatrace ingests OTLP data and enriches it with its own topology.

Dynatrace's single autonomous agent deployed on hosts that auto-discovers processes and instruments applications, services, and infrastructure without manual configuration.

A Dynatrace component that routes and proxies traffic between OneAgents and the cluster, and enables private network monitoring and extensions.

Automatic deep instrumentation of application methods, frameworks, and database calls, revealing where time is spent inside a transaction without code changes.

A target for a reliability metric such as availability or latency measured over a window, used to drive release and operational decisions.

A measurable objective for a service expressed as a target percentage of good events over a period, with an error budget derived from the target.

The allowable amount of unreliability implied by an SLO target, consumed by failures and used to gate releases or prioritize remediation work.

Automated comparison of key metrics and SLOs before and after a deployment to confirm the new version did not degrade performance or reliability.

A Dynatrace capability that runs automated quality gates against objectives during delivery pipelines, blocking promotion when validations fail.

Dynatrace Query Language, used to query logs, events, spans, and metrics with pipe-based commands for filtering, aggregation, and transformation.

Collection of log data through OneAgent, Fluentd, or the log ingest API, with parsing and enrichment applied before storage and analysis.

Rules that parse, extract attributes, mask sensitive content, and route incoming log records so they are searchable and retained appropriately.

Capture of actual user sessions in browsers and mobile apps, measuring load performance, errors, and user actions to reflect real experience.

Scripted browser or HTTP checks executed on a schedule from global locations to test availability and performance independent of real user traffic.

A synthetic check that drives a real browser through a scripted user journey, validating clicks, navigation, and visual outcomes from multiple locations.

Reconstruction of a real user's interaction with a web or mobile app, showing clicks, navigation, and rendering issues for experience diagnosis.

A captured record of a business-relevant occurrence such as an order or login, ingested via the events API or OneAgent and analyzed alongside technical data.

A defined sequence of business events representing an end-to-end process, enabling conversion, drop-off, and duration analysis across stages.

Connecting technical telemetry to business outcomes and KPIs so teams can quantify revenue, conversion, or process impact of IT behavior.

Continuous assessment of loaded libraries and application code against known vulnerability databases, prioritized by actual exposure and exploitability.

An inventory of components and libraries in an application build, mapped to known vulnerabilities and licenses for supply-chain risk management.

A detected attempt to exploit a vulnerability or weakness, correlated in Dynatrace with the affected process, service, and potential blast radius.

Correlating security findings with runtime topology and traces so defenders see which workloads, services, and users are actually impacted.

Monitoring of workloads, pods, and cluster events with automatic mapping of Kubernetes objects to the services and applications they support.

A monitored physical or virtual machine entity in the Dynatrace model, carrying process groups, resource metrics, and availability state.

A logical grouping of identical processes across hosts, used to aggregate monitoring data and map processes to services and applications.

An ActiveGate deployed in your own network to route agent traffic, run extensions, and reach private endpoints without exposing them publicly.