Gain a deeper understanding of Dynatrace terminology and concepts.
A performance-measurement standard that shows the relationship between recorded performance measurements and real-user satisfaction. Apdex offers a uniform means of measuring how well performance meets user expectations. For full details on the Apdex standard, please visit Apdex.org. In the context of Dynatrace, Apdex is used to give you a quick and easy rating that you can use to evaluate the satisfaction of your application's end users. Apdex ratings in Dynatrace are based on application-specific thresholds. An Apdex measurement rating of
1 equates to perfect performance. An Apdex rating below
0.5 equates to poor performance. For more details about how Apdex is applied in Dynatrace, please see [What is an Apdex rating?]((/support/help/user-experience/analytics/what-is-an-apdex-rating/))
A web application consists of web pages that are served by web servers and web containers, for example Tomcat. A web or mobile application is built upon services that process requests like web requests, web service calls, and messaging. Within Dynatrace, the term application refers to the front-end part that you can access via a browser or a mobile app.
Dynatrace monitors all of your application's services, processes, and infrastructure. By evaluating all components collectively, Dynatrace pinpoints exactly how each service contributes to the performance of your application. For example, in Java monitoring, the host, JVM, and processes are seen as a whole.
Dynatrace monitors all the individual components that applications are built upon: web requests, database requests, processes, services, and more. It's these individual components working together that collectively deliver what your end users view as a complete application. Dynatrace identifies and tracks each of these individual application components at a highly granular level. Dynatrace doesn't simply identify that a service is running on a server in a process but rather identifies all the details of these components. For example, Dynatrace can show you which of your web services is running on your Tomcat application server and how your Tomcat server's performance is affected by its host, or even your VMware vCenter server. In this way, Dynatrace gives you insight into the performance of your unique application stack, including all its components and connections.
A simulated user visit that monitors your application’s business critical workflows. Use the Dynatrace recorder to record an exact sequence of clicks and user input that you're interested in monitoring for availability and performance. Once you’ve captured the mouse clicks and additional user actions that you want your browser clickpath to include, your tic monitor runs automatically at regular intervals to test your site’s availability and functionality.
The equivalent of a simulated user visiting your application using a modern web browser. Browser monitors can be configured to run from any of our global locations at a frequency of up to once every 5 minutes. Browser monitors alert you when your application is inaccessible from the Internet or when baseline performance degrades significantly.
The process of determining the root causes of a process crash.
Dynatrace accelerates crash analysis by providing a process crash entry in each affected process and monitored host. Details available for crash analysis may include a native core dump, a Java core dump, or an abnormal program exit due to exceptions. Dynatrace also provides access to additional crash artifacts, such as
hs_err_pid files for Java crashes, text files providing Linux and Windows core dump analysis, and files containing the
Node.js exceptions that are potentially responsible for crashes.
From the perspective of Dynatrace Smartscape environment-topology mapping, a data center is either:
- A grouping of virtual machines running in an Amazon cloud instance. We map Availability Zones to your data center.
- Or a set of vCenter-based virtual hosts that transmit data to Dynatrace via a single Security Gateway. You may have multiple vCenter servers or standalone ESXi hosts associated with a single data center.
Each virtual host within a data center must have Dynatrace OneAgent installed on it. You will see at least one data center in Smartscape view if you have a Security Gateway installed. If you don't have a Security Gateway in your environment, Smartscape can't create a data center for your topology map.
Note that Dynatrace provides real-world geographic location details for data centers—look for data center location details in Smartscape and on Host pages (in the Properties pane).
The Dynatrace Artificial Virtual Intelligence System. Davis is the first digital performance assistant powered by artificial intelligence. Using an Amazon Alexa compatible device and Dynatrace artificial intelligence, you can ask Davis natural language questions about your Dynatrace environment using only your voice. The conversational interface brings Davis into the room with you, where he can serve as your virtual assistant. Davis provides data-driven answers and insights instead of raw data, and even learns who you are and customizes answers.
You can also interact with Davis through a number of other services, including Slack, and the Davis web app.
Dynatrace provides you with deep visibility into the performance of all the services that comprise your web application: web services, web containers, database requests, custom services, and more. You can even track service performance over time, with both historical and up-to-the-moment data.
The amount of time a tic monitor or tic action waits before the web application is ready to initiate another user action.
Monitors the performance of the computers in your application-deployment environment and all their processes. Based on your environment settings, Dynatrace OneAgent enables detailed performance monitoring and real user monitoring of your application and its services. Changes to your applications as well as infrastructure and performance problems are reported to Dynatrace for performance monitoring.
A Dynatrace component that provides secure and reliable communication with cloud-based Dynatrace cluster nodes. Similar to a proxy, Security Gateway reduces bandwidth requirements by encrypting and compressing network communication. It also provides monitoring of virtual infrastructure. Stopping or disabling Security Gateway reduces the monitoring capabilities of hosts that use Security Gateway to communicate with Dynatrace clusters.
The automatic mapping or diagramming of the layout of mission-critical applications in your Dynatrace monitoring environments. The environment topology shows relationships between different applications, their access by various computers and networks, and their current availability and performance.
With no manual configuration, Dynatrace uses its Smartscape technology to auto-discover all the components and dependencies of your entire technology stack end-to-end and visualizes it in an easy to understand environment topology. Dynatrace auto-detects and monitors the broadest range of technologies in the industry.
A manual action reported by Dynatrace that is performed in your environment. Examples include a machine reboot, system shutdown, process restart, or new code deployment. Any manual action you perform on a server is an event, even if it's a regularly scheduled event.
Any service that is called by your application or another service, but isn't directly monitored by Dynatrace OneAgent is considered to be an external service. Dynatrace maintains awareness that external services are in operation because these services are in communication with the services and/or applications that Dynatrace does monitor, however Dynatrace doesn't receive performance data related to these services. An exception to this rule is database services. If you have Dynatrace OneAgent installed on a machine from which JDBC calls are sent to your database, Dynatrace will provide a full spectrum of performance analysis related to the called database service (even when Dynatrace OneAgent isn't installed on the database server machine itself).
The size of a host based on the amount of that host's RAM. A host with 16 GB of RAM equates to 1 host unit for full stack monitoring, and .3 host units for cloud infrastructure. So, for example, a host with a memory size of 24 GB equates to 3 host units for full stack, and .9 host units for cloud monitoring.
Dynatrace pricing is based on host unit hours. A single host unit hour represents 1 host unit running for 1 hour. So, if you have a host with a memory size of 24 GB, the host will be billed at a rate of 2 host units. That host would then consume 48 host units when running for 24 hours. If you use a cloud infrastructure monitoring license for your servers, a 24 GB host running for 24 hours consumes 8 host units (24 x .3).
Dynatrace's multidimensional visual interface that lets you see multiple dimensions of the top three (action duration(?)) findings of your application's usage. With Hyperlyzer, you can see details on where your users are located, what browser version they're using, their operating system, and the number of different user actions the application has received. The hyperlyzer wheel interface lets you quickly focus on details based on a filtered dimension.
Hyperlyzer data is based on detection rules, which can be configured for each application.
Web requests that are of particular interest in your web-application environment because they are critical measure of the success of your business (for example, a login request or a shopping-cart checkout request) or because they provide vital technical functionality that your application relies on. Dynatrace provides advanced monitoring functionality for these key requests so that you can monitor them with extra care.
Key requests are highlighted in the Key requests section on each service overview page. This visibility is particularly valuable for low-volume, high-importance requests that might otherwise appear at the bottom of the Top requests section on the service overview page.
The practice of intelligent evaluation of data logging records produced by network devices, operating systems, applications, or any intelligent or programmable device.
Dynatrace log analytics provides direct access to the log content of all your system's mission-critical processes, and lets you quickly search for specific log message. You can filter log content based on keywords or time frame, and even analyze multiple log files simultaneously—even when log files are stored across multiple hosts.
Most significantly, Dynatrace artificial intelligence automatically correlates relevant log messages with any problems that it detects in your environment. Any relevant log messages associated with a problem is factored into the problem's root-cause analysis.
A host (either a VMware virtual machine or an EC2 instance) that communicates with monitored hosts in your environment, but does not itself have Dynatrace OneAgent installed. It's recommended that you install Dynatrace OneAgent on all monitoring candidates to gain full visibility and complete monitoring capabilities.
In Smartscape, a candidate is visualized with dashed circles and a generic host icon. It is shown linked to the relevant datacenter. Each monitoring candidate is also listed on the Hosts page, within the Unmonitored category.
Any inactive monitoring candidates (those that haven't communicated with a host for more than 2 hours) are not included in Smartscape or listed on the Hosts page.
Where all instances of OneAgent send captured monitoring data for your analysis via the Dynatrace UI. A monitoring environment is analogous to an analysis server that provides all Dynatrace application-performance analysis functionality, including all dashboards, charts, reports and other tools.
You can set up multiple monitoring environments to group related entities for discrete analysis. For example, you might set up one monitoring environment to monitor and analyze the performance of your production clusters. You might set up a second environment that's dedicated to the performance of your developers' machines and a third environment for your staging servers. How you segment your monitoring environments is entirely up to you.
There are a number of variables or “dimensions” that affect application performance—most notably, geographic region, OS, browser, connection type, and user action. These are the five dimensions that Dynatrace uses to evaluate application health. Each subset of user is subject to a unique set of these variables so Dynatrace measures the health of and reports on each of these user subsets separately.
“oneagentmon device” appears in your Windows system during Dynatrace OneAgent installation. It's used by Dynatrace for deep process monitoring. It works like a monitoring driver and allows Dynatrace OneAgent to add its own library between the operating system and processes it is running.
A special device that appears in your Windows system during Dynatrace OneAgent installation. It is indispensable for deep monitoring purposes, as it allows the Dynatrace to add its own library between the system and the monitored processes.
A service detected on the calling side by Dynatrace for which code-level visibility isn't available.
Dynatrace can detect requests an opaque service and identify which processes they are processed by, but Dynatrace can't monitor the service directly. Code-level visibility isn't available for a service whose technology type doesn't support deep monitoring, or the service's technology is not recognized or supported.
Evaluating traffic and load anomalies carries different assumptions than evaluating performance anomalies. Dynatrace uses a wide range of measures and methodologies to identify performance anomalies that affect customer experience and therefore require your attention. However, traffic and load anomalies are based on daily, seasonal, and business-cycle related patterns driven by an application's business model, related marketing efforts, and sociological factors. These are fairly predictable cycles that impact traffic and load as customers use your application. Examples of predictable cycles include weekends/workweeks, workday/evening hours, and customer activity occurring on an annual cycle, such as Black Friday. Because of this, Dynatrace uses a prediction-based methodology approach to detect abnormalities in application traffic and service load.
A Security Gateway that is bound to your environment, and thus only handles traffic from OneAgents that belong to the same environment as the Security Gateway. A private Security Gateway is downloaded from your Dynatrace environment and installed within your infrastructure.
A private Security Gateway only handles traffic from OneAgents, not from other Security Gateways. A private Security Gateway can communicate to a Dynatrace server either directly or via a public Managed Security Gateway.
A logical grouping of information in Dynatrace that includes the AI-driven analysis, environmental context, root cause analysis, and other details provided for one or more incidents in your environment. Problems can express themselves in your environment as performance degradations, improper functionality, or lack of availability. A problem can be the result of a single "event" or multiple events.
A process is an instance of a computer program that is being executed. Processes serve as containers that host services. When you look at processes you see topology information, whereas services give you code-level insight. For example, you might have a Tomcat process that hosts a web application in the form of a server-side service. While processes are host-centric—associated with a single machine in your environment—services are request-centric and therefore typically span across multiple machines in a data center.
A set of processes that perform the same function across multiple hosts. For example, you might have a cluster of servers with each server running the same process in support of multiple hosts.
An assessment of process health determined from response measurements that track process respose times when reacting to requests from other processes or clients (regardless of resource consumption).
Real user monitoring shows your visitors experience when they interact with your application. It is a combination of web analytics and performance measurements that build the picture of how your customer-facing components operate.
The time it takes for a service to be executed and complete a task.
The systematic process for identifying why problems occur, and an approach for responding to them and preventing them.
Dynatrace identifies performance problems before your customers are affected by them and prioritizes problems based on customer impact, providing instant insight into problem severity and user experience impact. When Dynatrace discovers performance problems, it provides a single problem notification that identifies the problem root cause so you don’t have to manually interpret dozens of data sources identify the root cause and can fix them quicker.
Because performance problems are seldom isolated and usually symptoms of larger issues, Dynatrace artificial intelligence looks at billions of events throughout your entire IT environment and helps you address the causes of problems, not the symptoms. Dynatrace root cause analysis also streamlines bug fixing through deep-dive analysis into source code and database statements, letting you cut down mean time to repair by 90% or more.
Web applications consist of web pages that are served by web servers and web containers, for example Tomcat. The web requests that are sent to a specific Tomcat server are an example of a server-side service. Web and mobile applications are built upon services that process requests like web requests, web service calls, and messaging. Such "server-side services" can take the form of web services, web containers, database requests, custom services, and more. Services may in turn call other services such as web services, remote services, and databases services.
Processes are essentially containers that host services. When you look at processes you see topology information, whereas services give you code-level insight. For example, you might have a Tomcat process that hosts a web application in the form of a server-side service. While processes are host-centric—associated with a single machine in your environment—services are request-centric and therefore typically span across multiple machines in a data center.
Server-side code executed within a process group.
A visualization of all the services that send requests to a specific back-end service. More than just showing which services directly call a specific back-end service, Service backtrace shows you the sequence of service calls that leads up to each request, all the way back up to the browser click that triggered the sequence of calls.
An easy-to-read report that summarizes the monitoring insights that Dynatrace has compiled over the past week. It is structured in such a way that even non-technical team members can understand them. Reports calculate how well your stack monitoring stack components perform and provides scores for the following areas:
- Overall environment
Service quality reports give you insights into hot spots in your environment and make it easy to share insights with others.
One or more actions that cover any interaction between a user’s browser and your application. A session includes at least one action. Sessions end when a user’s browser closes or is inactive for 30 minutes. Note that bounced sessions (sessions with only a single action) don't count against your billable session quota.
Using proprietary Smartscape technology, Dynatrace is able to automatically discover your entire application stack, from the data centers, hosts, and processes that comprise your infrastructure and network, through the services that comprise your applications, and extending all the way up to your applications. Dynatrace even discovers and maps all of the dependencies of these components, in real time. Dynatrace then presents its findings to you in an interactive Smartscape topology map. You can click anywhere within a Smartscape visualization to view performance statistics for each of discovered entity in your environment.
The equivalent of a simulated user action. When a Browser clickpath triggers the loading of a new page or an XHR request, Dynatrace monitors the availability and performance of that action.
Application availability and performance experiences can vary greatly between different customers around the world and at any given time. Therefore, constant availability and performance monitoring of your application is imperative. It marks how successful you deliver full application and availablity and performance to your users.
Dynatrace tic monitoring makes it easy for you to monitor application availability and performance as your customers experience it, around the world and around the clock. It can proactively simulate user visits regardless of whether or not users are currently visiting your site. Tic monitoring provides 24x7 global visibility into your web applications by driving real web browser sessions with full HTML5/Ajax support.
The mechanism available in the upper-right corner of all pages and views that lets you specify a time range to display only data in that range in the page. Previous and Next buttons in the time frame selector let you move forward and backward in time. A selected time frame propagates to all pages you visit where time-frame selection is supported.
Actions your customers perform within your application. User actions equate to common user activities such as performing a search, viewing an account balance, viewing items in a shopping cart, or ordering a product. User actions vary based on the features of your application.
The duration of a user action is called action duration. This represents the time that the user must wait before they can proceed. So a low action duration is better than a high action duration. For more details, see What are user actions?.
A group of user actions performed by the same user within a certain time period. It is created with the first user interaction with your application and ends after the user closes the browser or is inactive for a specified period of time, so it comprises a single customer experience with your web application.
Dynatrace typically shows all the visits of each individual user, even when those sessions are anonymous (non-authenticated users identified with browser cookies) or when a user tag has been edited or deleted. For mobile apps, Dynatrace identifies individual users based on the specific mobile device they use. For web applications, user identification is achieved by storing a persistent cookie within each user’s browser. Cookies enable Dynatrace to assign even anonymous user sessions to known users. As long as a user has logged into your application at least once, you can search for and identify that user, even when the user accesses your application within anonymous, unauthenticated sessions. This is particularly useful for analyzing periods of time when a user may not have been able to log into your application due to an issue with your authentication service.