Upgrade to remove ads
Only $35.99/year

Dynatrace :: Become a Jedi Master :: updated April 2022

Terms in this set (1637)

An a retail stores have a lot of technologies monitored by Dynatrace. One of these legacy technologies are developed in .NET exe applications by others vendors. When make drill down in the transactions & services dashboard in dynatrace there are no requests incoming and outcoming for these .NET services. What do you do?
Create a custom service detection for .NET services.
The Governance boss requested informations about top services by load and infrastructure problems, by hosts with hours consolidated in the last week, what session you can acess to obtain this informations?
Reports
One host of a reputed bank are affected performance after automatic Dynatrace oneagent update in old legacy systems server. What best praticle to fast resolve this issue?
1 - Select especific host in dynatrace hosts menu, "...", select turn off monitoring, stop oneagent service, uninstall oneagent and restart services.

2 - Download previous oneagent version (except more recent updated), go to Settings > Monitoring > Monitoring overview > Download Dynatrace Oneagent or ActiveGate installer and reinstall (select version from the list).

3 - Disable automatic update in this host and review the technologies and versions supported by Dynatrace before update new oneagent version.
You created a POC in new customer and you need monitoring errors in agentless Real User Monitoring Web Application with Dynatrace, but customer don't see any related incidents about web applications in problems.

What is the best practice to raise alerts in problems in this case?
Settings > Anomaly detection > Custom events for alerting > Create custom event for alerting > Category > Applications
You need to create a dashboard with the total DEMS consumed, what do you do?
...
To capture information from user sessions, what options are supported?
Meta tags, cookies, JavaScript variables, CSS selector & Server side request attribute
In large environments, why is it important to correctly group, organize and configure the technologies detected by the process group on your hosts?
For more accurate monitoring results calculated by artificial intelligence eliminating false positives and noise.
A car dealership have a lot of apps in AWS cloud and use Dynatrace Managed to performance monitor. In the next month they are thinking migrate physical Dynatrace Managed to cloud to reduce local infrastructure server costs. In this change they have questions about security, amount data transmition to cloud and costs evolved. What you sugest for this case?
Connect Dynatrace using AWS PrivateLink
What is a solution that enables Dynatrace customers to connect 3rd-party services, applications and hosts via private connections?
AWS PrivateLink
if you're analyzing a SQL database service and you want to understand the sequence of preceding service requests that ultimately triggered the incoming requests to the SQL service.
Service Backtrace
Your customer needs more customized charts about UX in dashboards, what you recommend?
User Session Query Language
Key request special privileges
Custom thresholds - think SLAs
What are the Authentication method supported by WebChecks
Webforms
Apdex
- A performance-measurement standard that shows the relationship between recorded performance measurements and real-user satisfaction.

- Offers a uniform means of measuring how well performance meets user expectations.
Default APDEX calculation
3
What technique can be used to perform tagging?
Manual and Automated
Host definition
A physical or virtualized operating system
Host availability - Offline - Possible causes
- Crashed.
- There are issues with communication.
- Became so unstable that monitoring is unavailable.
- A virtual machine was terminated without proper system shutdown
Process
A currently executing computer program
Application
- Consists of web pages that are served by web servers and web containers, for example Tomcat.

- A web or mobile is built upon services that process requests like web requests, web service calls, and messaging.
Cluster Management Console (CMC)
The web-based user interface that manages a single Dynatrace Managed.
The CMC allows you to
- View the deployment status and configure your
- Dynatrace Managed cluster.
- Manage cluster nodes and ActiveGates.
- Manage your monitoring environments.
- Create user accounts and groups.
- View licensing information and consumption status.
- View audit log and cluster events.
Monitoring environment
Includes all the dashboards, charts, reports, and other tools that Dynatrace makes available for the analysis of your application or applications.
Dynatrace OneAgent DaemonSet
- You can set up on Kubernetes manually.

- Is a feature that ensures that if a copy of a pod on a node dies, the copy is recreated, and if nodes are added to the cluster, copies of the pod are added as well.
Naming services
Web server name, Context root, & Web application ID.
Web services identify
Web service name
Db service naming identify
Database Name or schema, ip and port
Detailed information kept (including errors)
10d
For Key Transaction How many days is 1h resolution data kept?
400
What components have built in Built-in static thresholds for problem detection?
Infrastructure
Dimensions from automated baselining to learn the typical reference values of application and services..
Response times, error rates, and load
For automated base-lining of response times what values are held in the baseline?
Median & 90th percentile
Application baselining calculates reference values for which different dimensions?
User Action, Geolocation, Browser and OS
For a new application must run for at leave X% of the week before alerting (response time and error rates) will take place.
20
Whats is dashed line in smartscape?
No communication for 2 hours or past
Maintenance windows settings
- Daily
- Day of week
- Day of month
- Once only

- Detect problems and alert
- Detect problems but don't alert
- Disable problem detection during maintenance
Maintenance windows for Dynatrace OneAgent updates
For how often and when to renew your instances.
You will be able to apply these settings to Host Groups or your whole Environment in Automatic Renew settings screens.
No communications between services for 72+ hours
Not showing in smartscape
Disable Java or .Net monitoring from all hosts
Settings > Monitoring > Monitored technologies > Global monitoring (set to off)
Synthetic - Settings for Outage handling

Local problems when a specified number of locations experience a given number of failures

Generate a problem and send an alert when this monitor is unavailable for one or more runs at any location.

- Alert if the selected location is unable to access my web application
- on first ocurrence, - 2, 3, 4 or 5 times consecutively
Service status page
Dynatrace proactively keeps you informed of service incidents and outage resolutions
Synthetic - Performance thresholds
Dynatrace generates a new problem if this monitor exceeds any of the below in 3 of the 5 most recent executions of any particular location, unless there is an open maintenance window for this monitor.

The problem will be closed if no performance threshold is violated in the 5 most recent executions of any location that had been affected in that way before.
Synthetic Advanced setup
- Enable additional HTTP headers
- Block specific requests
- Set cookies
Conversion goal metrics
- Destination
- User action
- Session duration
- Number of actions
Three main problem types for /browser monitors/ or HTTP monitors:
- Global outage
- Local outage
- Performance threshold violation
What is limit in megabytes for synthetic executions
10mb
max private locations for a tenant
100
max locations for individual synthetic browser monitor
200
single-URL browser monitor
is the equivalent of a simulated user visiting your application using a modern, updated web navigator.

can be configured to run from any of our global locations at frequencies of up to every 5 minutes.

alert you when your application becomes inaccessible or when baseline performance degrades significantly.
Browser clickpaths
Are simulated user visits that monitor your application's business critical workflows.

You can use the Dynatrace recorder to record an exact sequence of clicks and user input that you are interested in monitoring for availability and performance.
HTTP monitors
Is a simple request.

You can use it to check if your website or API endpoint is available.

Run automatically at regular intervals.

Are executed by an ActiveGate and require a special ActiveGate configuration.
Web Recorder
Google Chrome (latest version, backwards compatible)
Result chart user session
app version, application, bouce, browser, browser monitor, browser type, conversion goals, converted, error count, ISP, location, manufacturer & device, OS, screen resolution, user action count, user, over time, hour
When you creating synthetic locations, you can filter by:
- Cloud provider
- Continent
- Country
- IP Address
- Name
- Type
How Dynatrace oneagent works?
Is essentially a set of specialized processes that run on each monitored host.

Collects metrics from the operating system it runs on and compares the metrics to performance metrics.

The most important metrics are then reported to Dynatrace.
User management and SSO integration
- SAML 2.0
- OpenID
- LDAP

compatible with:
- AD FS
- Azure configuration
- GSuite
- Okta
What is Dynatrace?
Is a software-intelligence monitoring platform that simplifies enterprise cloud complexity and accelerates digital transformation.

With Davis (the Dynatrace AI causation engine) and complete automation, the Dynatrace all-in-one platform provides answers, not just data, about the performance of your applications, their underlying infrastructure, and the experience of your end users.
Dynatrace capabilities
- Real User Monitoring
- Mobile app monitoring
- Server-side service monitoring
- Network, process, & host monitoring
- Cloud & virtual machine monitoring
- Container monitoring
- Root-cause analysis
Dynatrace OneAgent
Technology uses a single agent to collect and unify all operational and business performance metrics for all types of entities in your application environment—servers, applications, services, databases, and more—across each layer of your technology stack (including containers!).
Smartscape
Visualization technology maps everything running in your environment and detects all causal dependencies between websites, applications, services, processes, hosts, networks, and cloud infrastructure.
PurePath
Technology captures timings and code level context for application transactions end to end, across all supported technologies, from cloud to mainframe.
Dynatrace OneAgent can dig deeper and get network metrics at the process level.

Through our process-to-process monitoring of network communications Dynatrace can:
- Ensure high-quality process communications.

- Understand your topology in dynamic environments.

- Process-level capacity monitoring.

- See integrated health monitoring.
Communication from Dynatrace OneAgent to Dynatrace
Is outbound only, So there's no need to open ports for inbound
Mobile application land page
- User experience
- Network performance
- Crashes
- Called services
- Apdex rating
- User action and users
- New users
- App version distribution
- Problems
- Top 3 actions
- Geographic regions
- Events
Web application land page
- Top browser, xx% real users top user type, view geolocation breakdown

- Load actions, XHR Actions, Apdex rating & JavaScript errors

- Resources: xx/action, 3rd party/CDN resources xx/action resources

- Services

- User behavior: Top users, top user types, geolocation breakdown, Entry actions, other actions, exit actions & bounce rate

- Impact
What is external service?
Any called by your application or another that isn't directly monitored by Dynatrace OneAgent.
Events sample
Machine reboots, system shutdowns, process restarts, and new code deployments.
What is crash analysis?
- Determining the root causes of a problem.

- Dynatrace accelerates analysis by providing a error entry for 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.
From the perspective of Dynatrace Smartscape environment-topology mapping, what is datacenter?
- A grouping of virtual machines running in an Amazon cloud instance.

- Dynatrace maps Availability Zones.
Deep process monitoring
Visibility into the performance of all the services that comprise your web application: web services, web containers, database requests, custom services, and more.
Duration
The amount of time a synthetic monitor or synthetic action waits before the web application is ready to initiate another user action.
Key request
Are requisitions that are of particular interest in your web-application environment because they're a critical measure of the success of your business (for example, a login or a shopping-cart checkout), because they provide vital technical functionality that your application relies on, or because they involve complex calculations.
Merged services
Monitoring of data from services of the same type and the same process group.

Aggregates multiple web-request services of the same process group that perform identical functions across separate cluster nodes.

appears in Dynatrace as a single service that contains all the data of all aggregated services.
Monitoring candidate
A host (either a VMware virtual machine or an EC2 instance) that communicates with monitored hosts in your environment, but doesn't itself have Dynatrace OneAgent installed on it
Multi-dimensional baselining
There are a number of variables that affect application performance—most notably, geographic region, OS, browser, connection type, and user action.

These are the five elements that Dynatrace uses to evaluate application health.
Opaque service
A service detected on the calling side by Dynatrace for which code-level visibility isn't available.
Prediction-based anomaly detection
Evaluating traffic and load abnormality carries different assumptions than evaluating performance.

Dynatrace uses a range of measures and methodologies to identify abnormality performance problems that affect customer experience and therefore require your attention.

Examples of predictable cycles include weekends/workweeks, workday/evening hours, and customer activity occurring on an annual cycle, such as Black Friday.
Problem
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.
Real user monitoring
- Analyzes the experience that your customers have while interacting with your application.

Is a combination of web analytics and performance measurements that build a picture of how well your customer-facing components perform.
Service backtrace
A visualization of all that send requests to a specific back-end service.
Service quality report
- An easy-to-read report that summarizes the monitoring insights that Dynatrace has compiled over the past week, composed by:

- Overall environment
- Applications
- Services
- Infrastructure
Process responsiveness
An assessment of operation health based on response-time metrics that measure how long it takes to react to requests from other operation or clients (regardless of resource consumption).
Response time
The period it takes for a service to execute and complete a task.
Timeframe selector
That's in the upper-right corner of all Dynatrace pages and views.

Enables you to filter monitoring data down to a specific time range.

Previous and Next buttons enable you to move forward and backward in time based on pre-defined increments (30 minutes, 1 hour, 1 day, 1 week, etc.).

When selected remain persistent even when you move between pages and views.
Timeframe selector options
- Presets
- Custom
- Recent
Timeframe selector preset options
- Last:
::30 minutes, 1h, 2h, 6h, 24h, 72h, 7 days, 30 days, 90 days & 365 days.
- Today & yesterday.
Timeframe selector Custom
- Calendar date view - from and to selection including date and time selection
.NET Instrumentation
By placing trace statements at strategic locations in your code for code tracing, performance metrics, error detection, dependency tracking, and more.

Not every detected application is instrumented by default.

Dynatrace maintains a set of rules to instrument specific processes (for example, IIS application-pools, which you can extend with our own rules).
.NET monitoring capabilities:
- End-to-end transaction tracing for web requests services, web services, remoting services, queues, and databases.

- Garbage collection & process metrics

- Always-on 24x7 production grade CPU profiling.

- OneAgent SDK for custom tracing.
.NET Runtimes
Dynatrace provides support for .NET Framework as well as .NET Core.
Java Monitoring
- End to end transaction tracing for web requests services, web services, remoting services, JMS and RabbitMQ.

- Insight into SQL databases (via JDBC) and No SQL databases like MongoDB, Cassandra and Redis.

- Heap, garbage collection, thread, JMX & process metrics.

- Heap dumps—Dynatrace supports heap dumps for the Oracle JVM, OpenJDK and IBM JVM.

- Always on 24x7 production grade CPU profiling.
Java - How to identify memory leaks
As an initial indicator, check the garbage collection metrics.

Select Technologies from the navigation menu and click on a based technology tile.

From the process group list appearing beneath, expand the process group you want to examine and then click Process group details.

Here you can analyze technology-specific metrics by selecting the respective tab.
Use the following methods to identify and fix Java memory leaks:
- Use tools such as JVisualVM and jStat that come with JDK to investigate the cause of these memory issues.

- Check your memory settings configuration because memory issues don't only manifest themselves in the form of out-of-memory errors and memory leaks.

- Check the heap size:
- When heap size is set too low, it leads to increased GC activity because GC must then be executed more often.

- Increased GC usage leads to increased CPU usage and poor performance resulting from JVMs freezing during GC. GCs are short but frequent.

- When heap size is set too high, you get long GC times.

- Combines the problems of too small heap size with the problem of too large heap size.

- GC is triggered frequently and takes longer before the JVM crashes with an out-of-memory error.
The following are some of the causes of Java memory leaks:
- Thread local variables
- Mutable static fields and collections
- Circular and complex bi-directional references
- JNI memory leaks
- Wrong implementation of equals/hashcode
- Classloader escape.
The following are the most common causes of high Java memory usage:
- HTTP session as cache
- Wrong cache usage
- Churn rate and high transactional memory usage
- Large temporary objects
Memory-related ClassLoader issues
- Large classes
- Multiple instances of the same class in the memory
- Same class loaded repeatedly
To generate memory dump, Dynatrace uses
JVM Tool Interface (JVM TI)
If I enable memory dump analysis on multiple ActiveGates, which ActiveGate will perform the memory dump?
Have a priority assigned automatically.
If there is more than one with the same priority, an endpoint will be selected randomly.
What happens if a dump file transfer to an ActiveGate fails?
- Dynatrace OneAgent attempts to send the file list to all available endpoints until it finds one that works.

- This process is retried until it's successful or until the files are deleted by aging tasks (for example, if there are too many or if they are too old).
What happens if ActiveGate runs out of space for memory dumps?
- will first delete outdated files.
- If there are no outdated, will delete the oldest first.
Dynatrace can store and analyze memory dumps for
Java, .NET, and Node.js based applications.
Memory dumps are first stored locally on the disk
of the monitored application-server machine.
Dynatrace OneAgent can subsequently upload the memory dumps automatically to an
ActiveGate, which can act as a long-term storage center for this.
Memory dumps are only available to users who have access to the
network location of your ActiveGate.
If you configure an ActiveGate to collect memory dumps, and then restart the ActiveGate service,
all instances of OneAgent will automatically reconnect and recognize to store this files.
From now on, whenever a memory dump is successfully triggered
the file will be uploaded automatically to the correct ActiveGate.

Once safely stored on the ActiveGate, the Dynatrace OneAgent deletes the local file from its storage.
ActiveGate Example custom.properties file contents - memory
[collector]
DumpSupported = true
[dump]
dumpDir = dump
maxSizeGb = 100
maxAgeDays = 7
maxConcurrentUploads = 5
Memory dump analysis - Before you begin
- You must configure an ActiveGate to store files.
- Your application server must have adequate space to store.

- You need the Configure capture of sensitive data user permission to do this trigger.
Opt-in mode
the injected JavaScript Real User Monitoring code won't capture any data or set cookies.
Do Not Track
HTTP header is for users who explicitly wish not to be monitored.
Session Replay
Is a powerful tool that you can use to capture and visually repeat user sessions.

You can record all interactions that customers have with your application and replay each click and action in a movie-like experience, allowing you to recapture the complete digital experience of every user and understand the exact user actions that led to errors, resolve complaints, and conduct usability analysis.

The settings enable you to protect confidential user data by leveraging data masking rules and permission controls for playing back recorded user sessions.
Session Replay opt-in mode
- Gives you the freedom to decide which parts of a user session must be recorded and when recording is permitted to begin. For example, you may choose to record user sessions:

- As soon as any user logs in
- Only for select customers so that you can offer them premium support
- Only for certain pages of the recorded application
Session replay - default masking settings
- All form fields are hided.
- All password fields are hided.
- Content masking is disabled.
- Attribute masking is disabled.
- Interaction masking is enabled for select form fields, such as gender selection drop-down option lists.
Main functions of ActiveGate
- Message routing.
- Buffering and compression.
- Authentication.
- Entry point for sealed networks.
- Can be used to serve as a single access point for such OneAgent instances.
You need to install an ActiveGate for the following use cases:
- Access sealed networks
- Store memory dumps
- Monitor using an ActiveGate plugin
- Monitor virtualized infrastructure
- Execute private HTTP monitors
- Execute private browser monitors
- Monitor Cloud Foundry
- Monitor Kubernetes/OpenShift & Azure & AWS
Environment ActiveGate
- That is bound to your environment, and thus only handles traffic from OneAgent instances that belong to the same environment.
Configure an Environment ActiveGate for multi-environment support
1 - Create a file called multitenant.properties that lists each Dynatrace environment you want the Environment to support. Use the following format:

tenant = <tenant1_ID>;<tenant1_token>
tenant = <tenant2_ID>;<tenant2_token>

Note that tenant_ID corresponds to environment ID. For security reasons, you can no longer find the tenant_token in the Dynatrace web UI.

2 - Save the file to the following folder:

on Linux: /var/lib/dynatrace/gateway/config
on Windows: %ProgramData%\dynatrace\gateway\config

3 - Restart.
Uninstall ActiveGate
Go to the /opt/dynatrace/gateway directory and, using root rights, run the uninstall.sh script.
You cannot use an Environment ActiveGate configured for multi-environment support to:
- Connect to environments from different clusters

- Route z/OS traffic to Dynatrace with zRemote

- Monitor remote technologies with ActiveGate extensions

- Execute monitors from private Synthetic locations

- Run Database Insights

- Connect to Dynatrace using AWS PrivateLink
Won't automatically detect anomalies for created application if...
10 or less actions per minute
Peak activity intervals
- Top 3 active-session
- Top 3 session-start
Error rate
Alerting on increases begins once the is ready and the application or service has run for at least 20% of a week (7 days).
Application baselining dimensions
User action, Geolocation, Browser & Operating system.
Service baselining dimensions
- Service method: A service's individual service methods (for example, getBookingPage or getReportPage).

- In the case of database services, the service method represents the different SQL statements that are queried (e.g., call verify_location(?) select booking0_.id from Booking booking0_ where booking0_.user_name<>?).

- A reference value is additionally calculated for the predefined service method groups, static requests, and dynamic requests.

- Service method group: Static or dynamic groups for web services, and for database services, groups that correspond to database operations like insert, update, select and so forth.

- For database services, a reference value is calculated for the predefined service method groups inserts, updates, and selects.
How automated baselining works
- Attempts to figure out the best reference values for incoming application and service traffic. To do this, Dynatrace automatically generates a baseline cube for your actual incoming application and service traffic.

- If your application also receives traffic from Beijing, but with a completely different response time, the baseline cube will automatically adapt.
baseline cube
- Is calculated two hours after your application or service is initially detected by Dynatrace OneAgent so that it can analyze two hours of actual traffic to calculate preliminary reference values and identify where your traffic comes from.
What are evaluated time for alerts generation?
Within 5-min and 15-min sliding time intervals.
5-min window alerting interval
Serves for quick alerting in case a sufficient number of sample values surpassing a baselines are identified.
15-min window alerting interval
is used for generating alerts with higher confidence.
In case a large amount of sample values is found to be above the baselines within one minute
will generate an alert at this point of time as well.
Predefined static thresholds for hosts - CPU saturation
Alert if CPU usage is higher than 95% in 3 of 5 one-minute intervals.
Predefined static thresholds for hosts - Memory event usage
- Alert if memory usage is higher than 90% on Windows or 80% on Linux.

- AND memory page fault rate is higher than 100 faults/s on Windows or 20 faults/s on Linux in 3 of 5 one-minute intervals.
Predefined static thresholds for hosts - GC activity
- Alert if GC time is higher than 40%.

- OR GC suspension is higher than 25% in 3 of 5 one-minute intervals.
Predefined static thresholds for hosts - Java out of memory
- Alert if the number exceptions is 1 per minute or higher.
Predefined static thresholds for networks - Number of dropped packets
- Alert if receive/transmit dropped packet percentage is higher than 10%.

- AND total packets rate is higher than 10 packets/s in 3 of 5 one-minute intervals.
Predefined static thresholds for networks - Network utilization
- Alert if sent/received traffic utilization is higher than 90% in 3 of 5 one-minute intervals.
Predefined static thresholds for networks - TCP connectivity for process
- Alert if percentage of new connection failures is higher than 3%

- AND number of failed connections is higher than 10 connections/min in 3 of 5 one-minute intervals.
Predefined static thresholds for networks - Retransmission rate
- Alert if retransmission rate is higher than 10%.

- AND number of retransmitted packets is higher than 10 packets/min in 3 of 5 one-minute intervals.
Predefined static thresholds for disks - Low disk space
- Alert if free disk space is lower than 3% in 3 of 5 one-minute intervals.
Predefined static thresholds for disks - Slow running disks
- Alert if disk read time and write time is higher than 200 ms in 3 of 5 one-minute intervals.
Predefined static thresholds for disks - Inodes number available
- Alert if percent of available inodes is lower than 5% in 3 of 5 one-minute intervals.
Setting lower thresholds
For mission-critical services within your infrastructure (where default thresholds may be too tolerant).
Disvantage of static thresholds
don't adapt to changing environments and require too much manual effort
Setting higher thresholds
For applications and services that are still in development or are in the testing stage.
Specify fixed thresholds is supported for:
- Applications
- Services
- Database services
- Infrastructure
- Plugin events
- NAM (DC RUM) events
- Custom alerts
Thresholds for individual entities:
- Application
- Host
- Request
Event
- A manual action performed on a server in your environment.

- Are reported by Dynatrace and, where applicable, correlated with detected problems.
Prediction-based methodology approach
Is used to detect abnormalities in application traffic and service load. This is because traffic and load are entirely dependent on daily, seasonal, and business-cycle related patterns that are driven by an application's business model, related marketing efforts, and sociological factors.
Unexpected low traffic
problem alert that was raised because actual incoming data differed substantially from predicted incoming data levels.
Frequent issues
Problems that are less severe and have a shorter duration than previous alerts.
Monitoring unavailable event
Indicate a widespread monitoring interruption, where the majority of your installed OneAgents lose their connection with the Dynatrace server.
Availability event
Reports any kind of severe component outage
Error event
Reports any kind of degradation of operational health due to errors.
Slowdown event
Reports a slowdown of an IT component
Resource event
Indicate resource contention.
Typical examples:
:: CPU saturation
:: Memory saturation
Info event
Reports any kind of interesting situation on a component, such as a deployment change
Custom alert event
Triggers an alert without causation and Davis AI involved
Mobile app crash rate increased
If Dynatrace observes an unusually high broken rate of one of your release versions within a sliding window of 10 minutes, event will be raised.
High rate of dropped packets
By default, Dynatrace alerts if the percentage on the TCP network level is higher than 10% and the total number is higher than 10 in 3 of 5 one-minute observation intervals
High number of network errors
By default, Dynatrace alerts if the percentage of failed connection attempts on the TCP level is higher than 3% and the total number of failed connections is higher than 10 connections/min in 3 out of 5 one-minute observation intervals.
Lambda high error rate
Informs about big amount of failed invocations for a specific function. By default, this event is raised if the amount of failed invocations is bigger than 5% in 3 of 5 one-minute intervals.
Elastic load balancer has a high backend failure rate
Dynatrace automatically reports the number of failed connection attempts to the backend of an AWS LB. By default, Dynatrace opens an alert if the number of failed connection attempts is higher than 10 per minute during at least 3 of 5 one-minute intervals.
Restart sequence
Dynatrace detects and alerts on abnormal relational database service (RDS) reset. By default, event is raised if an RDS instance shows a total number of ressets higher than 2 within an observation period of 20 minutes.
User action duration degradation
Are detected in multiple ways within Dynatrace.
By default, Dynatrace uses automated baselining to detect breakdown events of either the 50th percentile (Median) or the 90th percentile of an application's user action performance.

The baseline distinguishes between three main categories: load actions, XHR actions & custom user actions.
Response time degradation
Are detected in multiple ways within Dynatrace.
By default, Dynatrace uses automated baselining to detect breakdown events of either the 50th percentile (Median) or the 90th percentile of the service and service method.
CPU saturation
Are raised on the host level when usage rises above a critical threshold.
By default, Dynatrace alerts if usage is higher than 95% in 3 of 5 consecutive one-minute intervals.
Memory saturation
By default, Dynatrace alerts if usage is higher than 90% on Windows or 80% on Linux AND the page fault rate is higher than 100 faults/s on Windows or 20 faults/s on Linux within 3 of 5 one-minute intervals.
Low disk space
By default, Dynatrace alerts if free data on any of falls below 3% in at least 3 of 5 1-minute observation intervals.
Slow disk
By default, Dynatrace alerts if read or write time on any is higher than 200ms in at least 3 of 5 one-minute observation intervals.
Low number of inodes available
By default, Dynatrace alerts if the percentage of available on any of your disks is lower than 5% in at least 3 of 5 one-minute observation intervals.
High network utilization
By default, Dynatrace alerts if sent/received traffic utilization is higher than 90% in 3 of 5 one-minute observation intervals.
Long garbage-collection time
By default, Dynatrace alerts on times if time is higher than 40% or suspension is higher than 25% in 3 of 5 one-minute observation intervals.
High latency
By default, Dynatrace detects and alerts on greater within your relational database services (RDS).
Service flow
Which illustrates the sequence of calls that are triggered by each task request in your environment.
Maximum limit for Key requests creation
100
Key user action per application
20
Outlier analysis
Requests that have either unusually high or unusually low response times) greatly affect the overall response time of transactions.

To gain a deeper understanding on how response times vary across requests during the selected period
Service response time hotspots
With deep process monitoring enabled, Dynatrace analyzes the response time of each service running within each process.

This is applicable to Java, .NET, Node.js, PHP, Apache webserver, IIS, NGINX, and other technologies.
The Current hotspot pane
- Indicate which activities are consuming the most time for each service.

- Requests with slow response time, or high failure rate, or high CPU consumption appear here.

- The percentage shows the share of the request in the overall response time of the service.
To analyze all response time hotspots of the service, on the service overview page, click either the
View requests, View dynamic web requests, or View resources button.
Code-level visibility
Time the service spent executing its own code.
Automatic Hotspots - Top Findings
Section of the Response time analysis infographic lists the acess point that are the key contributors to the analyzed request.

If a request is slow, you'll see the underlying cause listed.
Response time distribution
Shows the distribution of all analyzed requests.

This shows you if your service has a range or if it performs uniformly.

Typically, web-request services have a wide range.

Analyzing a single request often shows a more uniform picture.
View response time hotspots
To further investigate the differences in response time between nodes.
Backtrace analysis
Provides an instance breakdown for each service.
View top web requests
Understand and analyze which web requests are the most expensive and most frequently called
Current hostspot
Displays top access point findings of the service.

Requests with slow response time, or high failure rate, or high CPU consumption appear here.

The pane also displays requests with high consumption of request resources.

The percentage shows the share of the request in the overall response time of the service.
To analyze all response time hotspots of the service
On the service overview page, click either the View requests, View dynamic web requests, or View resources button.

Dynatrace will display the overall details of the service.
Click the View response time hotspots button
to navigate to the Response time analysis page.
Response time analysis page
See the average observed during the observed timeframe.

On the left side of the infographic, under Distribution, you can see how much is contributed by calls to other services, calls to databases, and code-level execution.

On the right side, under Top findings, we list the biggest hotspots identified by Dynatrace.

You can click any of these entries to view further details.
Click Interaction with services and queues
To display details regarding how these calls contribute to the overall response time.

On the left side you see how often the analyzed service calls other services and to what extent these calls contribute to the response time.

On the right side, this information is broken down into more detail. In the example above, you see that most of the time is contributed by the Easytravel Customer Frontend service.
Click the Database usage portion of the infographic
To access details about the database requests of the analyzed service and to see how they contribute to the response time.

The top section offers the same navigation and information offered by the Interaction with services and queues section.

Beneath this you can view all database requests.
Unexpected services
PurePaths for which a related service can't be determined, for example, due to missing service name or type.

may be caused by network issues (i.e., data lost in transition) or by abrupt termination of the process (restart or scaling).
Volatile services*
Aim to prevent the creation of too many distinct tasks.

is created when it is obvious that too many individual tasks would be detected based on the call information.
Examples of Volatile services
A database that is called through many distinct connection strings.

Each connection is captured as a separate service.

A task that is called via dynamic port setup.

A call from each port is captured as a separate task.
Define service settings globally.

Settings > Server-side service monitoring
to find the available configuration for detecting and naming web requests, database calls, and custom stasks.

These configurations define rules that apply to all tasks detected in your system.
With global service-monitoring settings you can:
Define entry points (a method, class, or interface) for custom task that don't use standard protocols.

Create merged services in order to logically group separately detected services into the same service (in Merged service monitoring).

Customize and enhance the default names of detected task (see Service naming rules).

Create advanced filters based on request attributes (see Request attributes).
With service-specific monitoring settings you can:
Edit the default display names of services and add descriptions to improve tracking (see Naming and Web request naming).

Fine tune HTTP error detection rules (see Error detection).

You can also configure how sensitive Dynatrace should be to 404 HTTP errors (broken links).

Switch off unwanted alerts about response time degradations, failure rate increases, or changes in load behavior (see Anomaly detection).
By default, Dynatrace detects:
- Programming exceptions (Java, .NET, Node.js, and PHP) as the reason for failed requests when exceptions result in the abort of service calls.

- Error pages provided by many web containers for handled exceptions.

- HTTP 500-599 error codes for web requests are interpreted as errors on the server side.

- HTTP 400-599 error codes for web requests are interpreted as errors on the client side.
HTTP response codes
4XX usually only indicate client-side errors, not server-side errors.

Normally, you wouldn't want to be alerted when errors happen due to client problems that are outside of your control.

You can however explicitly specify which missing should be treated as server side errors and which as client side errors.
HTTP 404 - broken link configuration
When a web server can't find a certain page it returns an response code.

Usually, this indicates a problem on the calling side. In cases where the calling side belongs to the same website, this would be considered a broken link.
Requests aborted by the caller
Some exceptions indicate that the client cancel the operation.

Although this is a technical error, in principle doesn't count as a failed request as it's not something that is the services fault. If a service request encounters such an exception, Dynatrace won't consider the request failed, regardless of the HTTP error code or any other information.
Ignore exceptions
There are cases where your code (or 3rd-party code you have no control over) returns restriction that indicate a certain response and not an error.

Take the Thrift client for Cassandra, for example. It returns a NotFound******* when a row isn't found. This isn't an error, but simply a response code.
HTTP 500-599
error codes for web requests are interpreted as errors on the server side.
HTTP 400-599
error codes for web requests are interpreted as errors on the client side.
Custom handled exceptions
There are situations where application code support restriction gracefully in a manner that isn't automatically detected by Dynatrace.

When this happens, Dynatrace doesn't detect failed requests or alert you to errors.

Such situations can easily be remedied by simply specifying any restriction class that should result in a failed request.
Custom errors
Not all situations are triggered by exceptions.

Some fail situations are only detectable via a return value or other means.

To support such cases, you can define a request attribute that captures the required data.

You can then define a fail rule based on the request attribute that will check the value of the request attribute to decide if the request has failed or not.
Client abort exceptions
- Although these are technical errors, in principle they don't count as failed requests as they aren't caused by faults with the service.

- If a service request encounters such, Dynatrace consider the request as successful, regardless of the HTTP error code or any other information. Error detection simply ignores.
Transfer Size
Large bytes don't automatically lead to poor performance.

For example, a page load action might result in a exchange of over 10MB while the corresponding.
Network monitoring overhead
is negligible and varies based on the analyzed traffic volume.

If Weight increases above 5% of available CPU, Dynatrace, throttling occurs.

The module is then paused for slightly less than 3 minutes. After this time is re-enabled.

If the threshold is still exceeded, throttling occurs again, with the module paused for twice as long.

This continues until the threshold is no longer exceeded.

The timing of the pauses doubles each time that the is re-enabled and the threshold remains exceeded, up to a maximum pause time of 45 minutes.
Tag vs metadata
Dynatrace differentiates between tags and metadata.

Metadata properties are key/value pairs that are inherent to any monitored entity.

Tags in Dynatrace are labels or markers that do not belong to an entity.

Tags however may also have a key/value structure.
How are tags and metadata created
Metadata is detected during startup or discovery of a monitored entity and is immutable from within Dynatrace.

Metadata is read only and can't be changed using the Dynatrace web UI.

Tags, on the other hand, aren't information about an entity and don't belong to one specific entity.

Tags are used to find/filter/designate sets of entities.
You can use metadata to
- Apply tags to entities via rules.

- Apply naming schemes to your process groups and services.

- Define Management zones.
As tags have predominantly an organizational and management purpose within Dynatrace, they are useful for:
- Filtering lists

- Defining which entities you want to chart in a custom chart or dashboard.

- Specifying where to send problem notification based on problem context in alerting profiles.

- Defining custom alerts.

- Accessing metric data via the REST API.

- Finding and inspecting monitoring results via Dynatrace search.

- Defining a maintenance window.
Tags are
- Meant for organization, not for defining extra information for your entities.

- It is therefore important to consider whether something is really a tag (a label or marker) or simply metadata and additional information.
Properties supported by Dynatrace for automated tagging
- Service properties
- Process properties
- Host properties
You can also set up automated tagging of the entities in your environment using
- Smartscape and topology API
- Environment variables,
- Host autotag configuration file (for hosts only)
Process properties supported by Dynatrace for automated tagging
- Apache Spark master IP address, Apache configuration path, Azure host name of process,
Azure site name of process.

- Catalina base, Catalina home, Cloud Foundry application, Cloud Foundry instance index, Cloud Foundry space, Cloud Foundry space ID, ColdFusion.
- JVM configuration file, ColdFusion service name.

- Detected group name, Detected process name, Docker container name, Docker image name, Dotnet command, Dynatrace custom cluster ID,
Dynatrace custom node ID.

- Elasticsearch cluster name, Elasticsearch node name, EXE name, EXE path, GlassFish domain name, GlassFish instance name.

- IIS application pool, IIS role name, JBoss home, JBoss mode, JBoss server name, Java JAR file, Java JAR path, Java main class.

- Kubernetes base pod name, Kubernetes container name, Kubernetes full pod name, Kubernetes namespace, Kubernetes pod uid, Listen port, Node.js application name, Node.js script name, Process group name.

- Process name, Ruby application root path, Ruby script path, Varnish instance name, WebLogic home,
WebLogic name, WebSphere cell name, WebSphere cluster name, WebSphere node name, WebSphere server name.
Services properties supported by Dynatrace for automated tagging
- Custom service class name, Database name, Database topology, Database vendor, Detected service name.

- Endpoint path, Public domain name, Service name, Service port, Service tags.

- Web application ID, Web context root, Web server, host, Web server name, Web service name, Web service namespace.
Host properties supported by Dynatrace for automated tagging
- AWS availability zone, Azure SKU, Azure compute mode, Azure web application host name, Azure web application site name, Cloud type.

- Detected AWS Availability Zone, Detected host name, EC2 Instance ID, Host IP address, Host group name, Host name, Host tags, Hypervisor type.

- Local EC2 host name, OS type, OS version, PaaS type,
Public EC2 host name.
Database Statements limits
- is limited to 4KB (KiloBytes).

- This setting isn't configurable.

- That exceed this limit are trimmed to 4KB.
Dynatrace OneAgent code module memory requirement
- Demand depends on multiple factors.

- To facilitate straight forward resource planning, we recommend that you account for an additional 200MB budget for monitored application processes.*

- This number will suffice monitoring of a vast number of applications. Empirical observations show demand well below 100MB for most applications.*

The monitoring demand refers to resident set size (RSS) or equivalent quantification on non Linux operating systems.
If you need to monitor a remote technology where Dynatrace OneAgent installation isn't an option, use
ActiveGate extensions.
If you simply want to monitor a Java application that exposes MBeans, use
JMX extensions.
RSS
Is a key quantifier for applying memory limits to processes.
Cloud platform memory limits
Kubernetes and other technologies feature definition of resources for workloads.

Apply (roughly spoken) to RSS and workloads are automatically terminated once they exceed the defined resources.

As Dynatrace OneAgent code modules increase ******** demand of monitored applications, resources must be adjusted accordingly.
Cost and traffic control
That you can use to reduce your session usage while monitoring your mobile apps.

By default, Dynatrace captures all user actions and user sessions for analysis.

This approach ensures complete insight into your application's performance and customer experience.

You can optionally reduce the granularity of user-action and user-session analysis by capturing a lower percentage of user sessions.
Dynatrace automatically detects
IP addresses, geolocations as well as browsers, devices, and operating systems.
Monitor Docker containers - Home
- Number of running containers, hosts, images, dockerized services and requests/min.
- Top 3 containers & images consuming the most memory
- Most recently started container
- Most frequently used images
Average number of running containers
Section of the page provides deep insights into the dynamics of your Dockerized environment by showing you how the number of containers has evolved over the past 7 days.
Docker hosts
Section at the bottom of the page shows resource usage of individual hosts. This information helps you make decisions about capacity planning and container provisioning.
Metrics provided by docker container
CPU, Memory, Traffic & Throttling
Memory requeriments for Dynatrace OneAgent on Linux
least 300 MB RAM.
What happens during Dynatrace OneAgent installation on Linux?
- Executable code and libraries.

- Creates its own user (dtuser). This user is created without a password.

- Checks the system's global proxy settings.

- Checks for a connection to Dynatrace Server or ActiveGate

- Detects all SELinux-aware applications and adjusts the SELinux security policy accordingly.

- Allows Dynatrace to inject its own libraries into monitored processes.

- Modifies the core pattern configuration so that can detect and report process crashes.
header x-dynatrace-test
VU, SI, TSN, LSN, LTN, PC
Load testing header - VU
Virtual User ID of the unique user who sent the request.
Load testing header - SI
Source ID identifies the product that triggered the request (JMeter, LoadRunner, Neotys, or other)
Load testing header - TSN
Test Step Name is a logical test step within your load testing script (for example, Login or Add to cart.
Load testing header - LSN
Load Script Name - name of the load testing script. This groups a set of test steps that make up a multi-step transaction (for example, an online purchase).
Load testing header - LTN
The Load Test Name uniquely identifies a test execution (for example, 6h Load Test - June 25)
Load testing header - PC
Page Context provides information about the document that is loaded in the currently processed page.
Tag tests with HTTP headers
While executing a load test from your load testing tool of choice (JMeter, Neotys, LoadRunner, etc) each simulated HTTP request can be tagged with additional that contain test-transaction information (for example, script name, test step name, and virtual user ID).

Dynatrace can analyze incoming and extract such contextual information from the header values and tag the captured requests with request attributes. Request attributes enable you to filter your monitoring data based on defined tags.
Push custom events
When running a load test, you can push additional context information to Dynatrace using the custom event API.

A custom annotation then appears in the Events section on all overview pages of the entities that are defined in the API call.
Load test events
are also displayed on associated services pages.
JMX extensions
Java Management Extensions is ideal for monitoring applications built using Java technology.

With Dynatrace, you can monitor any metric in your JVM that is exposed via an MBean.
Not seeing a certain JMX metric?
Is highly dynamic.

If a particular metric doesn't exist in your JVM, it's not an error—the metric simply isn't available.
Dynatrace JMX plugins
Are highly customizable beyond the capabilities of the editor.

You can download your add-on and edit its JSON file that describes your ****** metrics and how you want to display them.

For complete instructions and examples, see the Dynatrace ****** Extensions on GitHub.
API - Possible values for the items element:
- all
- java
- apache
- nginx
- nodejs
- dotnet
- php
- go
- sdk
Dynatrace API integration support
- Environment
- Configuration
Dynatrace API communication
ensures safety by using secured HTTPS protocol.
API - Possible values for the bitness element:
- 32
- 64
- all
API - Possible values for the arch element:
- all
- ppc
- ppcle
- s390
- sparc
- x86
API - Possible values for the flavor element:
- default
- musl
API - Possible values for the installerType element:
- default
- default-unattended
- paas
- paas-sh
API - Possible values for the osType element:
- windows
- unix
- aix
- solaris
Events API
delivers details about all uncorrelated events that Dynatrace collects within your environment.

Information returned for each event includes attributes about the event source, the entity where the event was collected, and other event-specific details.
Log Monitoring API
Provides direct access to the log content of all your system's mission-critical processes and enables you to quickly search for specific log messages.
Custom vs built-in metrics
- All metrics that are automatically detected and analyzed following installation of Dynatrace OneAgent are considered to be built-in metrics.

- Built-in metrics cover a wide range of supported technologies, including Apache Tomcat, NGINX, Couchbase, RabbitMQ, Cassandra, Jetty, and many others.

- A custom metric is defined as a new type of metric that offers a user-provided metric identifier and unit of measure.
Methods of defining and reporting custom metrics:
- Custom-defined Dynatrace OneAgent plugins or ActiveGate plugins.

- Custom JMX definitions that report additional metrics exported by Java processes.

- Use of the Dynatrace REST API to register and send custom metrics to Dynatrace via the REST API.
To view personalized add-in
Settings > Monitoring > Monitored technologies > Custom plugins tab
JMX/PMI plugin custom metrics
- You may notice that the number of metrics in the plugin.json file of your plugin differs from the number of billed custom metrics.

- This is because plugins provide "splittings" which can be used to define additional dimensions for reported metrics.

- For each value of a selected property, a separate timeseries metric is created at runtime.

- The actual number of timeseries metrics depends on the number of distinct values for the selected property.
Dynatrace OpenKit
- Is a set of open source libraries that provides an easy, lightweight means of instrumenting the source code of your custom applications so that you can monitor their performance with Dynatrace or AppMon.

- Is best suited for client/server applications that communicate via HTTP (for example, rich-client-applications, embedded devices, and terminals).
Advantages of OpenKit
- Ease of use.
- No 3rd-party or Dynatrace OneAgent library dependencies
- Ease of portability to other languages and platforms
With Dynatrace OpenKit, you can:
- Track user sessions and user actions.
- Report on events, errors, and crashes.
- Trace web requests to server-side PurePaths.
- Tag user sessions with user tags.
- Maintain compatability with both Dynatrace and AppMon.
With Dynatrace OpenKit, you can't:
- Create server-side PurePaths: This functionality is provided by the Dynatrace OneAgent SDK.

- Create metrics: You can however use the Custom network devices & metrics API to report metrics.
Troubleshoot Dynatrace OpenKit instrumentation
- Verify that you're using an official release. The releases can be found on these GitHub pages:
-- Java releases
-- .NET releases
- Verify that you used the correct property values that are provided in the settings of the custom application.
- Confirm that Dynatrace and your Cluster ActiveGate are reachable from your company network.
- Confirm that the ActiveGate is configured with a valid SSL certificate.
- Check if the log output contains messages that indicate connection problems. See logging for details.
Dynatrace offers two types of plugins:
- OneAgent
- ActiveGate
Dynatrace web UI requirements
- Microsoft Edge Latest version (desktop and mobile)
- Mozilla Firefox Latest version (desktop)
- Google Chrome Latest version (desktop and mobile)
- Safari 10+ (OS X and iOS)
HTTPS requirements
- As of June 30, 2019, you must enable the TLS 1.2 protocol in your browser to access the Dynatrace web UI.

- All modern browsers use TLS 1.2 by default.

- After June 30, 2019, you won't be able to access the Dynatrace web UI using TLS 1.0 or TLS 1.1.
Public cloud platforms supported
- Amazon Web Services
- Azure
- Google Cloud Platform
Enterprise cloud platforms supported
- Cloud Foundry
- Kubernetes
- OpenShift
Other platforms supported:
- Heroku
- Docker
- Mesos Marathon
How Dynatrace monitors containers
- There's no need to modify your Docker images, modify run commands, or create additional parameters to enable monitoring.

- Simply install OneAgent on your hosts.
Additionally, Dynatrace OneAgent detects
Which processes run on each host and collects performance metrics for the most important processes.

Can also monitor specific technologies (Java, Node.js, .NET, and more) in greater detail by injecting itself into those processes and monitoring their performance from within.

This provides you with code-level insights into the services that your applications rely on.
Management zones
Are a powerful information-partitioning mechanism that simultaneously promotes collaboration and the sharing of relevant team-specific data while still ensuring secure access controls.
Each customizable management zone comprises a set of
monitored entities in your environment, be it hosts that share a common purpose, a specific application, a staging environment, or services of a certain technology.
Once you create a management zone, that zone becomes available as a filter
which you can access via the Filter button in the menu bar.

Just select from the list.
Management zone filters apply to all views that display multiple entities
including dashboards, list pages (hosts, process groups, services, and applications), Smartscape, and the Technologies page. This enables each user to view only those entities that are relevant to them.
How management-zone rules are applied
- Using the OR logic—any rule must apply for an entity to be included.

- When creating some entities, you can propagate access to related topological entities without creating an extra condition.

- For example, when creating for services, you can opt to add underlying hosts and process groups.
Set up management zones
Settings > Preferences > Management zones
Dynatrace SaaS - Assign management zone to a group
Account Settings > Identity management > Group management
Dynatrace Managed Assign - management zone to a group
User authentication > User Groups > Users
What's included in host NIC health
Traffic, Packets, Quality & Connectivity
Traffic
The average rate at which data was transmitted during the interval.
Packets
The number of received and sent over the host network interface during the interval.
Quality
An assessment of the number of dropped packets and errors.
The Connectivity measure
can be used as an indicator of whether there's network traffic on a host. Note, however, that 0% connectivity doesn't necessarily indicate that there is a problem with a host.

Assuming no TCP errors are present, it may simply mean that no users have attempted to connect to the host process during the selected timeframe.
With network monitoring enabled
you'll see three new columns: Traffic, Retransmissions and Connectivity.
Connectivity is presented as two separately calculated metrics:
Connectivity & Local connectivity
Connectivity
Percentage of properly established TCP connections, compared to TCP connections that were refused or timed out.
Local connectivity
- Percentage of processes that establish TCP connections to other processes on the same host.

- Such connections don't generate network traffic.

- To keep the value accurate is treated as a separate metric.
To calculate Connectivity metrics
- compares the number of such errors with the total number of connection attempts.
retransmission rates should not exceed
0.5% on local area networks and 2% in Internet or cloud-based networks.
Retransmission rates above 3%
negatively affect user experience in most modern applications.
Retransmission issues are especially noticeable by
customers using mobile devices in poor network coverage areas.
Common network errors
- Checksum errors
- Full queues
- Time to live exceeded
- Packet retransmissions
Checksum errors
Aren't processed by the receiving host.

If the Ethernet (CRC) is wrong, the Ethernet frame is silently dropped by the network interface and can't be recovered even with packet capturing tools.

- Often go undetected, despite the the application of efforts.
Full queues
When the processing queue on a switch or router is overloaded or when the queue for incoming packets on the host is full, packets are dropped.
Time to live exceeded
Usually, when the TTL value hits 0, the time to live exceeded ICMP message is sent to the dispatcher of the package.

However, some network components silently drop packets when TTL is equal to 0.
Common reasons for retransmissions include:
- network congestion where packets are dropped; either a TCP segment is lost on its way to the destination or the associated ACK is lost on the way back to the sender.

- tight router QoS rules that give preferential treatment to certain protocols.

- TCP segments that arrive out of order at their destination, usually because the segments are not in order. If rate of traffic to and from the Internet is higher than 2%, it can impact the user experience.
Commands to troubleshoot network errors
- Ifconfig, netstat & ethtool
ifconfig
provides detailed statistics about received and transmitted packets.

The RX lines contain information about received packets, and the TX lines contain information about transmitted packets.
netstat
To view detailed network informations for TCP, UDP, IP, and ICMP protocols
ethtool
Use to query and control the settings of the network interface and the network driver.

It gives a detailed list of all errors that can occur on the network interface level, such as CRC and carrier errors.

If there are no retransmissions on the TCP layer but ifconfig still returns a lot of erroneous packets, can help dig into the specifics.

If returns a large number of errors, there is usually something wrong with the NIC, cable, switchport, or other hardware.
You can use Dynatrace to measure and evaluate a number of networking and service-related metrics
Network traffic, Responsiveness & Connectivity
Network traffic
provides a good overview of the overall usage and performance of your service.

It's also a good indicator of whether you need to upscale your infrastructure.
Responsiveness
measures the time from the last request packet that the service receives to the first response packet that the service sends.

It measures the time a process needs to produce a response to a given request and must be watched in correlation with hardware resources.
Memory Health from host
- Memory used & Page Fault
System Memory
- Total, Free & Reclaimable
To receive dynatrace notifications in your cellphone
Download Dynatrace app from: Apple and Google
Severity
- Availability
- Error
- Slowdown
- Resource
- Custom
- Info
To view problems in specific time and date
select timeframe in upper right corner and set custom option
How you can disable process group monitoring from all hosts?
Go to Settings, Monitoring, Monitoring overview, Process group and set flag to off.
Process group monitoring - Deep monitoring rules affect service and code-level monitoring and Java/.NET/Node.js/Golang/PHP/Webserver metrics in infrastructure monitoring mode.
They have the following limitations:
- Up to 100 can be defined.
- They only impact hosts and processes where OneAgent is installed.
- Application-only integrations aren't affected.
Host naming
- Naming rules enable you to customize and enhance the default names of your hosts.

- Naming rules apply to already detected hosts that are active and online.
What is the port for communicating from Dynatrace OneAgent to gateway?
9999
How to make use of request attributes
- Filter your monitoring data.
- Define web-request naming rules.
- Set up detection of business-logic related errors.
- Build your own custom analysis charts.
- Enrich PurePath analysis by adding metadata to PurePaths.
- Create custom metrics using the Timeseries API.
- Create custom queries, segmentation, and aggregation of session data with User Session Query Language
Other ad hoc analysis.
You can use request attribute for
a travel website that tracks the destinations of each of your customers' bookings, you can set up a destination attribute for each service request.
Request attributes can be defined based on:
- web data
- Java method arguments
- .NET method arguments
- any data captured with the OneAgent SDK
Mark request attributes as confidential
With this setting enabled, unauthorized Dynatrace users see only an obscured view of masked data.

For example, while unauthorized users can see all performance metrics related to the execution of a certain SQL statement, all sensitive values in the statement are represented with five asterisks (*****), and so are hidden from unauthorized access (see image below).
Request attributes - In these cases you can not only capture the necessary information, you can also choose if you are interested in the calling side of a web request (the client) or the processing side (the server). These sources are all technology independent and work everywhere.
- Java servlet session attribute
- ASP.NET session-state variable
Capture request attributes based on method arguments.
The following limitations apply to deep access object:
- You can obtain only one field at a time. If you're accessing a field, it must be in the beginning of the chain.

- Method parameters are not allowed.

- You must use valid Java or .NET notation.
Custom service detection
- Java
- .NET
- PHP
- Go
- NodeJS
Enable real-time updates to Java and PHP services selector at Custom service detection
may cause CPU spikes when changes are deployed.
For Apache Kafka messaging services
you can only select methods with a ConsumerRecord argument.
Define queue messaging consuming custom services - Apache Kafka
- Is different from other equivalent systems.
- Its interfaces are designed to process content in bulk, yet the purpose of Dynatrace is to follow single transactions.
- Dynatrace can only do this if you define a Java method that is responsible for processing a single content in your code and use this as the entry point.
- Ensures that you only pick methods that have a **** ConsumerRecord.
There are several different sources of request attributes for web requests
- HTTP POST parameters
- HTTP headers
- URL or one of its constituents, like the path or a query parameter
Enable/disable SQL Bind variables?
is only available for Dynatrace Managed deployments, not SaaS deployments.
Settings > Server-side service monitoring > Deep Monitoring > Exclude noisy and unnecessary exceptions
Cut from being captured in monitored requests to reduce network bandwidth, storage requirements and potential overhead.

Dynatrace will still attempt to capture these restrictions if they are the immediate cause of a failing request.
Settings > Server-side service monitoring > Deep Monitoring > Exclude specific incoming web request URLs
unimportant or 'noisy' incoming from monitoring and alerting.

Supported for Java, .NET, Apache HTTP Server, IIS, Nginx, Node.js and beginning with Dynatrace OneAgent 1.177 supported for Go.
Main options in Settings > Server-side service monitoring > Deep Monitoring > Troubleshooting
- Global
- Process group override
Main options in Settings > Server-side service monitoring > Deep Monitoring > Troubleshooting > Global
- Capture PurePath
- Real user monitoring
- Capture SQL Select row count
- Capture method hotspot information in PurePaths
- Capture background CPU method hotspot information
- Capture background CPU method hotspot information (Node.js)
Distributed tracing
for context propagation to help reduce broken traces as the W3C Context headers are less likely to be dropped by proxies and cloud gateways.

W3C Trace Context also helps to achieve ool interoperability and can be used in scenarios with multiple Dynatrace environments.
Alerting profiles
Enable you to set up fine-grained filtering rules that are based on the severity, customer impact, associated tags, and/or duration of detected problems.

Enable you to control exactly which conditions result in problem notifications and which don't.

This includes all problem-push notifications that are sent via the Dynatrace mobile app and displayed in the Dynatrace web UI.
Satisfactory performance
0 to 3s
Tolerable performance
more of 3s up until 12s
Frustrating performance
equal or more of 12s
Where you can adjust thresholds monitoring data you receive for 3rd party, CDN and 1st party resources?
Select desired application, "...", edit, Advanced Setup and change settings in Content resource settings
Tags based on environment variables
This feature is currently only available for processes that are deep monitored via Dynatrace OneAgent (Java, Apache Webserver, NGINX, .NET, Node.js, PHP, Go, and IIS).
A custom service is
that has a manually defined method, class, or interface as its entry point.
You can define custom services for
Java, PHP, .NET, Go & Node.JS
How long is time series data held with a resolution of 5 mins?
28d
How long is time series data held with a resolution of 1 minute?
14d
What percentage of CPU consumed by the Dynatrace OneAgent does dynatrace, start to limit network monitoring?
5
Monitoring live user sessions trought USQL are possible?
Not.
To view live user sessions
Live user activity in dashboard
User Session Details
- Started time
- Licence consumed
- Duration
- Operating System
- IP
- Real User identifier
- Screen resolution
- ISP
- User Experience Score
- Browser
- Action with errors
- Geo location
- Applications accessed
- Session properties
- Analysis timeline & Session replay
What are the characteristics of a service?
A set of code that accepts requests and returns results
What is the port used by the Dynatrace Oneagent to communicate to the Managed Server?
8443
Dynatrace Managed :: Cluster node ports usage
443, 8443, 8018, 8019, 8020, 8021, 8022, 5701, 5711, 7000, 7001, 7199, 9042, 9200 & 9300
Dynatrace Managed :: 8443 Port
Monitoring data from OneAgent, nodes within cluster
Dynatrace Managed :: 8018 Port
Nodekeeper
Dynatrace Managed :: 8019 Port
Upgrade UI
Dynatrace Managed :: 8020 & 8021 Ports
UI and REST API
Dynatrace Managed :: 8022 Port
UI and REST API (NGINX)
Dynatrace Managed :: 5701-5711 Ports
Hazelcast In-memory data grid platform
Dynatrace Managed :: 9042, 7000, 7001 & 7199 Ports
Cassandra-based Hypercube storage
Dynatrace Managed :: 9200 & 9300 Ports
Elasticsearch-based search engine
Outbound communication to Dynatrace Mission Control
Within multi-node clusters, each node must be able to communicate with Mission Control for basic health checks (for example, component states, disk, and CPU usage), in addition to the mandatory management connection
https://mcsvc.dynatrace.com
How long is time series data kept with a resolution of 1 hour?
440d
Session and user action properties can be used to
Enric monitored user sessions and actions with additional details that facilitate fine-grain user-session and application-performance analysis.
Application Settings - Session and user action properties, you might create key/value pairs for:
- purchases above a certain amount (for example, ordersum = 100),
- datacenter location (for example, datacenter = south1), or for
- a segment of users receiving a new promotion (for example, abtesting = c)
Usability analytics
Analyze detected user experience issues within your application.

User action types that commonly reflect user frustration include dead clicks, rage clicks, rage rotates, and page refreshes.
Detect rage clicks
Three or more rapid clicks within the same area of a web page are considered.

Commonly reflect slow-loading or failed page resources.

With this setting enabled, is compiled for each monitored user session.
How long is Visit data held for in Dynatrace SaaS?
35d
Advantages of PrivateLink
- Additional security.
- Better connectivity.
- Reduced traffic costs.
What is the maximum number of nodes allowed in a cluster?
10
Auto-detect proxy settings in Dynatrace OneAgent Installation
su -c 'Dynatrace-Agent-Linux-0.5.0-20140217-175809.sh PROXY=auto'
Dynatrace OneAgent - Display Help
./oneagentctl --help
Dynatrace OneAgent - Display version
./oneagentctl --version
Dynatrace OneAgent - Change communication settings
./oneagentctl --set-server=https://my-server.com:443 --set-tenant=abc123456 --set-tenant-token=abcdefg123456790 --set-proxy=my-proxy.com
Dynatrace OneAgent - Show current communication endpoints
./oneagentctl --get-server
Dynatrace OneAgent - Show environment ID
./oneagentctl --get-tenant
Dynatrace OneAgent - Show tenant token
./oneagentctl --get-tenant-token
Dynatrace OneAgent - Show current proxy
./oneagentctl --get-proxy
Dynatrace OneAgent - Clear proxy configuration
./oneagentctl --set-proxy=
Dynatrace OneAgent - Check current port range
./oneagentctl --get-watchdog-portrange
Dynatrace OneAgent - Set a new port range
./oneagentctl --set-watchdog-portrange=50000:50100
Dynatrace OneAgent - Check if Log Monitoring is enabled
./oneagentctl --get-app-log-content-access
Dynatrace OneAgent - Enable or disable Log Monitoring
./oneagentctl --set-app-log-content-access=true
Dynatrace OneAgent - Check if access to system logs is enabled
./oneagentctl --get-system-logs-access-enabled
Dynatrace OneAgent - Enable or disable access to system logs
./oneagentctl --set-system-logs-access-enabled=true
Dynatrace OneAgent - Display your host ID
./oneagentctl --get-host-id
Dynatrace OneAgent - Define the host ID source
./Dynatrace-OneAgent-Linux.sh --set-host-id-source="ip-addresses;namespace=test"
Dynatrace OneAgent - Change host group assignment
./oneagentctl --set-host-group=MyHostGroup
Dynatrace OneAgent - Clear host group assignment
./oneagentctl --set-host-group=
Dynatrace OneAgent - Custom host name
./oneagentctl --set-host-name=myhostname
Dynatrace OneAgent - Clear Custom host name
./oneagentctl --set-host-name=""
Dynatrace OneAgent - Custom host metadata
./oneagentctl --set-host-property=AppName --set-host-property=Environment=Dev
Dynatrace OneAgent - Remove host properties
./oneagentctl --remove-host-property=AppName --remove-host-property=Environment=Dev
Dynatrace OneAgent - Show all host properties
./oneagentctl --get-host-properties
Dynatrace OneAgent - Custom host tags
./oneagentctl --set-host-tag=TestHost --set-host-tag=role=fallback --set-host-tag=Gdansk
Dynatrace OneAgent - Remove Custom host tags
./oneagentctl --remove-host-tag=role=fallback --remove-host-tag=Gdansk
Dynatrace OneAgent - Show all tags
./oneagentctl --get-host-tags
Dynatrace OneAgent - Check if Infrastructure Monitoring mode is enabled
./oneagentctl --get-infra-only
Dynatrace OneAgent - Enable or disable Infrastructure Monitoring mode
./oneagentctl --set-infra-only=true
Dynatrace OneAgent - Check the ingestion port
./oneagentctl --get-extensions-ingest-port
Dynatrace OneAgent - Set a custom ingestion port
/oneagentctl --set-extensions-ingest-port=14499 --restart-service
Dynatrace OneAgent - StatsD - Check the ingestion port
./oneagentctl --get-extensions-statsd-port
Dynatrace OneAgent - StatsD - Set a custom ingestion port
./oneagentctl --set-extensions-statsd-port=18125 --restart-service
Dynatrace OneAgent - Set a network zone
./oneagentctl --set-network-zone=<your.network.zone>
Dynatrace OneAgent - Reset a network zone
./oneagentctl --set-network-zone=""
Dynatrace OneAgent - Display network zone setting
./oneagentctl --get-network-zone
Dynatrace OneAgent - Passing configuration parameters during installation
/bin/sh Dynatrace-OneAgent-Linux.sh --set-host-group=test_group
Disk space requirements for Dynatrace OneAgent installation and update on Linux (x86)
5.4 GB
The size of the Dynatrace OneAgent installation process is calculated as follows:
3 * installer file size + size of the installation
The Dynatrace OneAgent installer size must be multiplied by 3 to account for:
- Downloaded file.
- Archive, which is separated from the ******** script
- Unpacked external TAR
Dynatrace OneAgent Installation process size
1gb
Dynatrace OneAgent requires root privileges to:
- Access the list of open sockets for each process.
- Access the list of libraries loaded for each process.
- Access the name and path of the executable file for each process.
- Access command line parameters for each process.
- Monitor network traffic.
- Read application configuration files.
- Parse executables for Go Discovery.
- Gather monitoring data related to Docker containers.

*If you have Log Monitoring enabled, is necessary:
- Accessing system logs: /var/log/syslog and /var/log/messages.
- Accessing the list of open file handlers for each process (/proc file system).
- Accessing the log file for each process.
System logs
Dynatrace can diagnose issues that may be caused by conditions in your environment.

Most often such issues are related to deep monitoring or auto-update installations.
System logs files downloaded by Dynatrace OneAgent
/var/log/boot.log
/var/log/dmesg
/var/log/dpkg.log
/var/log/kern.log
/var/log/messages
/var/log/syslog
/var/log/yum.log
/var/log/audit/audit.log
/var/log/zypper.log
Revoke access to system logs
./Dynatrace-OneAgent-Linux.sh DISABLE_SYSTEM_LOGS_ACCESS=1
Disabling system log access
Limits our ability to diagnose and solve issues proactively.

With access is revoked, you may need to manually provide Dynatrace with the contents of your system to help us diagnose issues within your environment.
Dynatrace OneAgent won't automatically update when it's first installed. By default
wait 1440 minutes (24 hours) before allowing on EC2 hosts and 120 minutes on non-EC2 hosts.
Individual host settings
override the global auto-update.
When a new version of Dynatrace OneAgent becomes available
you'll receive an alert on your home dashboard.

In addition, warning symbols are displayed on the Monitoring overview page beside each host that contains an outdated version.
Installation of a specific version of Dynatrace OneAgent on all new hosts
1 - Go to Settings > Preferences > OneAgent updates.

2 - Disable automatic OneAgent updates by setting the Automatically update all OneAgent instances switch to the Off position.

3 - From the drop-down list, select the version of Dynatrace OneAgent that is to be installed on all new hosts.
Global auto-update across all hosts
1 - Go to Settings > Preferences > OneAgent updates.
2 - Switch on Automatically update all OneAgent instances.
Auto-update security
- Communication is encrypted.

- Installers are signed and the signature is verified for each downloaded installer package. If the verification fails, is aborted.
Stop Dynatrace OneAgent on SystemV
service oneagent stop
Stop Dynatrace OneAgent on systemd
systemctl stop oneagent
Stop/restart ActiveGate on linux
service dynatracegateway start | stop | forcestop
Stop/restart ActiveGate on Windows
net stop | start "Dynatrace Gateway"
ActiveGate Hardware requeriments
- 2 GB free disk space
- 2 GB RAM (4 GB recommended)
- 1 dual core processor
ActiveGate If you modify the custom.properties file
restart to put your changes into effect.
The configuration file config.properties is overwritten during each update of ActiveGate. Thus, any customized settings stored in this file will be lost (with some exceptions). To avoid losing your customized settings with each update, store customized settings in the custom.properties file will initially be empty. To specify customized settings, enter section names and include the properties within these sections. We recommend that you first locate the relevant section in the
custom.properties
Activegate - The custom.properties file will initially be empty. To specify customized settings, enter section names and include the properties within these sections. We recommend that you first locate the relevant section in the
config.properties file and then copy the section title along with the names of the desired properties into customized configurations file.
Activegate properties configuration file
[connectivity]
[com.compuware.apm.webserver]
[dump]
[http.client]
[http.client.external]
[collector]
[aws_monitoring]
[azure_monitoring]
[cloudfoundry_monitoring]
[kubernetes_monitoring]
[vmware_monitoring]
[dbAgent]
[synthetic]
Activegate configuration file property [connectivity]
- dnsEntryPoint
- networkZone
Activegate configuration file property [com.compuware.apm.webserver]
- port-ssl
- port
- ssl-protocols
- excluded-ciphers
- certificate-file
- certificate-password
- certificate-alias
Activegate configuration file property [dump]
- dumpDir
- maxSizeGb
- maxAgeDays
- maxConcurrentUploads
- downloadUrl
Activegate configuration file property [http.client]
- proxy-server
- proxy-port
- proxy-user
- proxy-password
Activegate configuration file property [http.client.external]
- proxy-server
- proxy-port
- proxy-user
- proxy-password
Activegate configuration file property [collector]
- MSGrouter
- restInterface
- DumpSupported
- trustedstore-password
- trustedstore-type
Activegate configuration file property [synthetic]
- proxy-server
- proxy-port
- proxy-user
- proxy-password
- proxy-off
- proxy-non-proxy-hosts
- synthetic_enabled
The port 9999 that is used for communication with Dynatrace OneAgents and other ActiveGates
can be manually re-configured in custom.properties file.
Uninstall Dynatrace OneAgent on Linux
/opt/dynatrace/oneagent/agent directory and, using root rights, run the uninstall.sh script.
For a complete Dynatrace OneAgent unistallation, remove
(perform backup before)
- Log files located at /opt/dynatrace/oneagent/log.

- Configuration files located at /var/lib/dynatrace/oneagent/agent/config.

- The user running OneAgent, dtuser.
Server certificate check failed
Dynatrace OneAgent is shipped with trusted Dynatrace SSL certificates, which are used to verify that OneAgent connects successfully to Dynatrace Server or ActiveGate.

If your environment uses a proxy (thereby requiring an update to the remote server's SSL certificate), then you may encounter a Server certificate check failed message during the initial connection check.

To resolve this issue, specify the trusted proxy certificate that is to be utilized by Dynatrace OneAgent. To do this, provide a copy of your proxy's SSL certificate as a file called custom.pem in the /var/lib/dynatrace/oneagent/agent/customkeys directory. The file custom.pem should contain the proxy's certificate along with any intermediate certificates as required.
Processes not detected?
- isn't supported by our monitoring technology. You can always check which types Dynatrace supports.

- Isn't working on your server. Please ensure that your servers are running and that are operational.

- There is delay in communication between Dynatrace and your Dynatrace OneAgent. If this is the case, please wait a few moments and try again.

- Your Dynatrace OneAgent isn't working properly. Go to Settings > Monitoring overview to confirm that monitoring is enabled for the host running your software.

- If you're still unable to resolve this issue, please contact us at Dynatrace answers. Also, consider installing Dynatrace OneAgent on a different machine.
Why doesn't Dynatrace OneAgent start to monitor Apache process after restart?
Following installation, your web server must be completely reloaded to enable monitoring.

To do this correctly, it's important to understand the difference between "partial" and "complete" reload.

In the case of partial reloads, the main web server process re-reads its configuration files, re-opens its log files, and then reloads its worker processes.
To execute a complete Apache restart and enable deep monitoring with Dynatrace OneAgent
apachectl stop
apachectl start
What can I do when Dynatrace OneAgent blocks a port I need?
Consists of different processes that communicate via a TCP port with a watchdog. At startup, OneAgent watchdog attempts to open the first available port between port 50000 and 50100.

In some cases you may need this port for your own applications that are started after OneAgent.

In such cases, you can change the port range that the OneAgent watchdog uses by modifying the file watchdoguserconfig.conf.
Operation not permitted
Make sure that Dynatrace OneAgent installation isn't blocked by antivirus software installed on the host.
Dynatrace OneAgent configuration via command-line interface
oneagentctl
oneagentctl tool is currently not available
for OneAgent deployed as a container using volume-based storage.
Use the oneagentctl command-line interface
to perform some post-installation Dynatrace OneAgent configuration at the individual host level.
oneagentctl interface
Windows, Linux, and AIX
How host groups affect your monitoring environment
Are sets of servers.

This makes it easy to change the settings for a large number of servers.

You can define alerting thresholds and Dynatrace OneAgent update settings on a group basis.

Accepts the globally-configured anomaly thresholds without overriding them.
Host groups affect how process groups are detected.
When the same process is running in two different host groups,
Dynatrace will create one for each host group.
You can also configure process groups differently depending on which host group they run in. Consequently,
services are also grouped per host group. So you can configure services differently per host group.
To override auto-detected host names, do one of the following:
- Define a *** naming rule in Dynatrace settings.

- Use the oneagentctl command-line tool.

- Use a configuration file OneAgent.
Any new Host naming rules will apply to
already detected hosts that are active and online.
A host can be assigned to a host group at the following times:
On Dynatrace OneAgent installation.

For example /bin/sh Dynatrace-OneAgent-Linux-1.137.65.sh HOST_GROUP=MyHostGroup or /bin/sh Dynatrace-OneAgent-Linux-1.177.65.sh --set-host-group=MyHostGroup. The --set-host-group parameter is available since version 1.177.

On Windows, you can also type the group name in the installer UI.

After OneAgent installation using the oneagentctl command-line tool.
Host group string requirements:
- Can contain only alphanumeric characters, hyphens, underscores, and periods.

- Must not start with dt.

- Maximum length is 100 characters
hostname.conf
For Windows:
Create the file in C:\ProgramData\dynatrace\oneagent\agent\config.
Note that Unicode encoding is not available on Windows.

For Linux:
Create the file in /var/lib/dynatrace/oneagent/agent/config.

Example: My App Server
To define a host naming rule
1 - Go to Settings > Monitoring > Host naming.

2 - Select Add a new rule.
Define tags and metadata for hosts
Within dynamic or large environments, manual host tagging can be impractical.

For dynamic deployments that include frequently changing host instances and names (for example, AWS or MS Azure), you can use a dedicated configuration file to programmatically apply tags to your hosts. The same is true for additional host properties, i.e. metadata
Edit the host tag configuration file
During Dynatrace OneAgent installation, the installer creates a simple hostautotag.conf configuration file on the monitored host.
On Windows, the file is located in %ProgramData%\dynatrace\oneagent\agent\config

on Linux in /var/lib/dynatrace/oneagent/agent/config.
Edit the host metadata configuration file
The process of configuring properties is very similar to the one for tags, but this time they are configured through the hostcustomproperties.conf that you need to create and add to Dynatrace OneAgent configuration directories:

*Windows: %PROGRAMDATA%\dynatrace\oneagent\agent\config
all UNIX-like systems /var/lib/dynatrace/oneagent/agent/config
Any hostautotag.conf or hostcustomproperties.conf files created
should be encoded in UTF-8.
/var/lib/dynatrace/oneagent/agent/config/hostcustomproperties.conf
Host metadata configuration file
/var/lib/dynatrace/oneagent/agent/config/hostautotag.conf
Host tag configuration file
Dynatrace API
Automate your monitoring tasks and export different types of data into your third-party reporting and analysis tools.

Communication ensures safety by using secured communication via the HTTPS protocol.
API Explorer
1 - Select Settings in the navigation menu.
2 - Go to Integration > Dynatrace API.
3 - Click the Dynatrace API Explorer link at the top of the page.
API direct link:
Managed https://{your-domain}/e/{your-environment-id}/rest-api-doc/index.jsp

Dynatrace SaaS https://{your-environment-id}.live.dynatrace.com/api-doc/index.jsp
Android Gradle - What does the "Max. user actions per minute exceeded" message mean?
Event informs you that the number of actions generated from Real User Monitoring (Web, Mobile, and OpenKit) has exceeded a limit that is specific to your environment.

Once this limit is reached, Dynatrace automatically throttles the number of user sessions being captured until the number of user actions is below the limit again.

The throttling is done on a user session basis in order to provide statistically correct values in Dynatrace.

If the overall traffic volume drops, Dynatrace will automatically return to the capturing rate you've set for your environment.
Android Gradle - Why does Dynatrace change the capture rate?
The maximum user action count per minute limit is specific to your environment and is there to prevent unexpected high consumption of your license volume by unexpected IT events like unannounced marketing campaigns, unplanned load tests, DDoS attacks, aggressive web scanners, or other.
In Dynatrace SaaS*, my user actions/minute can be changed?
Yes, for details, please contact the Dynatrace ONE team or your sales representative.
In Dynatrace Managed, my user actions/minute can be changed?
Environments > Cluster Management Console settings
Why is Dynatrace OneAgent for Android not sending data to my mobile app?
- Verify that you used the correct applicationId and beaconUrl value provided by your monitoring app.

- Did you adapt the Network Security Configuration correctly? You must include system CA certificates or the certificate to your public Managed Cluster ActiveGate.

- Check if Dynatrace or your public Managed Cluster ActiveGate is reachable from within your company network.

- [For Dynatrace Managed] Does the public Managed Cluster ActiveGate have a valid certificate? Also, verify that the host/domain name is correct.
In Android, why is my reported value, action name, and web request URL truncated?
When they exceed the border limit value of 250.
In Android, why are some of my web requests missing?
Only requisitions from a supported HTTP framework are captured.

Check if your HTTP framework is in this list. If it isn't, instrument your requisitions manually.
In Android, why are web requests not associated with a given user action?
- Only attaches requisitions to a user action triggered within a specific timeframe.

- The timeframe starts when the action opens and ends 500 ms after the action closes.

You can change this value with the userActions.timeout property.
In Android, why does my UI component not generate a user action?
- The UI component is defined in a WebView.

- The listener method is defined in a resource XML file.

- The UI component uses an unsupported listener. You can find the list of all supported listeners in the user action monitoring section.

- Enable the userActions.emptyActions property if your user interaction does not trigger a web request or lifecycle change. Dynatrace OneAgent for Android discards empty user actions by default.
Android build problems - why do I get the following message: "OneAgent SDK version <version_number> does not match Dynatrace Android Gradle plugin version <version_number>"?
- Android Gradle plugin must have the same version.

- You may have added Dynatrace OneAgent SDK (with a higher version) via a Gradle dependency to your Android application project.
Why does my build fail with "Plugin with id com.dynatrace.instrumentation not found"?
Check if you have added the buildscript block with the classpath "com.dynatrace.tools:android:8.+" dependency to your module's build.gradle file.
Why does my build fail with "Could not find com.dynatrace.tools.android:gradle-plugin:<version_number>"?
This is because Gradle was unable to find the specified version.

Check if you have specified the correct version number. You can check the available version on JCenter and Maven Central.

You also must add jcenter() or mavenCentral() to your buildscript configuration.
Why does my build fail with "Could not find any version that matches com.dynatrace.tools.android:gradle-plugin:<version_number>.+."?
Gradle was unable to find a version that matches your version settings.

You can check the available version on JCenter and Maven Central.

You also have to add jcenter() or mavenCentral() to your buildscript configuration.
Why does my build fail with "Could not get unknown property dynatrace for object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler"?
Check if you have applied the Dynatrace Gradle plugin before the dynatrace block dependency.
*
apply plugin: 'com.dynatrace.instrumentation'

dynatrace {
...
}*
Why do I get the message "Task printVariantAffiliation not found in project :<module_name>"?
Ensure that you have added the Dynatrace Android Gradle plugin to the buildscript classpath and that you have applied the plugin.

The Dynatrace Android Gradle plugin only generates new Gradle tasks (like the printVariantAffiliation task) for specific subprojects of your Android application project.

It does not generate tasks for the root project and some subproject. For example, the Dynatrace Android Gradle plugin doesn't generate the printVariantAffiliation for Android library modules.
Why do I get the following message: "The Dynatrace Android Gradle Plugin can only be applied to Android projects"?
Can only be used when your Android project is built with the Android Gradle plugin.

This error message is displayed when the Dynatrace Android Gradle plugin is used in non-Android projects or in Android projects that are not built via the Android Gradle plugin.
Tag specific users in mobile application
Dynatrace.identifyUser("john.doe@example.com")
Tag specific users in web application
Edit application settings > Capturing > User tag
Tag settings options for users in web application
- CSS selector
- JavaScript variable
- Meta tag
- Cookie value
- Query string
- Server side request attribute
Disk space requirements for Dynatrace OneAgent installation and update on Windows
6.5GB
Dynatrace OneAgent - Installation parameters
- SERVER
- TENANT
- TENANT_TOKEN
- PROXY
- HOST_GROUP
- APP_LOG_CONTENT_ACCESS
- DISABLE_SYSTEM_LOGS_ACCESS
- INFRA_ONLY
Non-privileged operation mode for Dynatrace OneAgent on Linux
- Satisfies the requirement for a non-admin monitoring solution.

- By combining full functionality with high security (by reducing the attack surface) Dynatrace provides the best in class solution for cloud environments.
What problems does Dynatrace OneAgent non-privileged mode solve?
Software is always at risk of attack, either by malicious programs operating in unmanned mode or by individuals using specially crafted tools.

One of the most efficient ways of preventing such attacks is by lowering the attack surface and reducing the potential impact of attacks should they be successful.
How to use Dynatrace OneAgent non-privileged mode
Once OneAgent is deployed in non-privileged mode, it begins working without superuser privileges while retaining all the same functionality for discovery, monitoring, data grouping, pushing to Dynatrace clusters, and automatically instrumenting numerous supported technologies with deep monitoring modules.

$ sudo ./Dynatrace-OneAgent-Linux.sh NON_ROOT_MODE=1
Findings
Davis, the Dynatrace AI causation engine, automatically detects for each waterfall.

Are key statistics and tips that capture how resources can impact page-level W3C timings of the initial request of an action—the base page in the case of load actions or the initial XHR in the case of XHR actions.
Select Show all findings
to expand the list of discovery above a waterfall.

Select to highlight the associated resources in the waterfall graph.
If an uncompressed text resource is larger than 860 bytes
the hover data on compression is highlighted in red. This threshold may be configurable.
Thresholds for findings
1 - Select Applications from the navigation menu.
2 - Select the application you want to configure.
3 - Click the Browse button (...) and select Edit.
4 - Select the Advanced setup tab.
5 - In the Content resource settings section, expand Configure thresholds for top ********.
Grouping, filters, and legend
Help you focus on the resources that matter to you. You can combine grouping and filtering controls.
Grouping by domain
organizes resources into first-party, third-party, and CDN *******.

You can see the load order and timing details for specific ********.
Grouping by type
Allows you to see the main categories of first-party, third-party, and CDN resources—image, script (JavaScript), CSS, and others.
The legend at the bottom of the waterfall lists the following with detailed descriptions below:
- W3C page-level metrics.
- JavaScript errors.
- Resource timing components.
Speed index is only applicable for
Load actions as the whole page is used as a reference for calculating the index.
What is the ActiveGate plugins license model?
We provide you with a Addin SDK free of charge.

You don't need a special license to develop and deploy your own custom addin.

Alternatively, you can have one of the Dynatrace partners develop addin for you, in which case your license fee depends on your contract.

Whichever approach you take, after you successfully deploy and start using your addin, you'll be charged for the custom metrics your addin reports.
I have uploaded and configured the plugin but receive a "Plugin doesn't exist on given host error".
Dynatrace doesn't propagate ActiveGate addin automatically.

You need to upload the addin package to Dynatrace Server and to each ActiveGate you want to run it on.

Each addin should be placed unpacked in its own folder in addin _deployment directory in the installation directory.

By default, /opt/dynatrace/remotepluginmodule/plugin_deployment on Linux or C:\Program Files\dynatrace\remotepluginmodule\plugin_deployment on Windows.
How do I deploy an ActiveGate Plugin?
You have to upload the addin to each that will run it and your Dynatrace Server.
I have a technology monitored by Dynatrace OneAgent and want to match Custom device group to the same technology tile.
How can I do that?
Open the Process Group details view of a technology, expand Properties section and look for the technology in the Main technology property. Add this value to technologies field in your plugin.json file. For more information, see plugin metadata in json file
Where can I find plugin logs?
Are saved by default in
/var/lib/dynatrace/remotepluginmodule/log/remote***** on Linux or
C:\ProgramData\Dynatrace\remote****module\log\remote***** on Windows
How do I prepare my development environment for ActiveGate Extension?
To start plugin you need to install python3, pip3 and pluginSDK.
Exclude bots and spiders from monitoring
1 - Select Applications from the navigation menu.
2 - Select the application for which you want to exclude bots and spiders.
3 - Click the browse button (...) and select Edit.
4 - Select Advanced setup from the left menu.
5 - In the Exclude/Include browsers from monitoring section, click Add browser exclusion rule.
6 - In the Browser dropdown, select Bots&Spiders.
7 - Click Add.
User behavior analysis
- Section displays a number of key performance metrics regarding user behavior, like bounces, top landing and exit pages, conversions and many more.

Just expand to analysis section of the infographic on the application overview page to view the user behavior analysis options.
User behavior infographic
- Top users
- Top user types
- Geolocation breakdown
- Sessions
- Entry actions
- Exit actions
- Other actions
- Bounce rate
- Overall conversion
Top conversion goals
Shows the conversion rate of your defined destiny.

Click View full details at the bottom right corner of this section to review overall metrics related to your conversion destiny or to analyze progress toward specific goals.

Alternatively, you can access the conversion analysis page, if you click a specific ******* ***. In this case
Supported out of the box
Varnish Cache, ActiveMQ, Apache Cordova, Cassandra, Couchbase, CouchDB, Elasticsearch, Hadoop, HAProxy, Kafka, Memcached, Microsoft SQL Server, PHP-FPM, PostgreSQL, RabbitMQ, Redis, Spark & Xamarin.
Dynatrace extension
The application software technologies listed below can be monitored by Dynatrace, but they require the addition installation of an addition that is available from Dynatrace.

When monitoring these technologies with Dynatrace, you may incur additional charges for custom metrics ingestion and analysis.

In addition, these technologies require a dedicated support plan that is separate from your Dynatrace license.
Dynatrace support extension technologies
Apigee Edge, Citrix NetScaler, Citrix virtual Apps and Virtual Desktops, IBM iSeries (AS/400), IBM MQ, Juniper Networks, SAP ABAP platform, IBM DataPower, F5 BIG-IP LTM & Windows Server.
Dynatrace OneAgent platform and capability support matrix
Page that describes which capabilities are sustained on different operating systems and platforms.
Early Adopter Release
Dynatrace offers a new OneAgent version each month in a staged roll-out process.

New features are introduced in on an opt-in basis.

Features aren't feature complete, but they're fully supported and production-ready.

Are publicly available, fully supported, production-ready, and available as a user opt-in.
Preview
Features are in the final stages of development and are ready to be viewed.

Features aren't production-ready and they aren't officially supported.

Provide you with access to new features so that we can hear your feedback and ultimately deliver features that exactly meet your needs.
GA
Generally available and fully supported.
Auto-injection of code modules
Automatically insert into monitored applications in a completely transparent and automatic fashion that requires no manual configuration or intervention.

This approach to deep monitoring is supported for Windows (Docker only) and Linux.

Among other things, also automatically inserts into Docker, containerd, CRI-O, and Cloud Foundry Garden containers.

This means that you don't have to change any container images on monitored platforms to gain full insights.
Dynatrace OneAgent deployment via OneAgent Operator
Deploys to Kubernetes or OpenShift clusters via a container.

There are some limitations when rolling out via container.
Limitations when rolling out Dynatrace OneAgent via a container.
- Auto-update mechanism of modules is disabled rollouts, however, the Operator takes care restarting pods to receive updates.

- Auto-injection of code-modules is disabled for native (i.e., non-containerized) processes.

- JMX plugins aren't supported for technologies outside of containers
Dynatrace detects the following properties which can be used for automated rule-based tags and property-based process group detection rules
- Kubernetes base pod name
- Kubernetes container
- Kubernetes full pod name
- Kubernetes namespace
- Kubernetes pod UID
Uninstall Dynatrace OneAgent Operator with kubectl
$ kubectl delete -n dynatrace oneagent --all
$ kubectl delete -f https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/latest/download/kubernetes.yaml
Uninstall Dynatrace OneAgent Operator with Helm
$ helm uninstall dynatrace-oneagent-operator -n dynatrace
Uninstall Dynatrace OneAgent DaemonSet
$ kubectl delete ds/dynatrace-oneagent
Uninstall Dynatrace OneAgent for application-only monitoring
simply remove references on Docker image and redeploy.
Map internal IP addresses to locations
If you don't see data for some of your application's users on the world map, it may be because those users have private network.

You can map such internal private network to real geographic locations at Settings > Web and mobile monitoring > Map IP addresses to locations and thereby make these users visible on the map.

You can also use this to import or update multiple data center mappings from a CSV file.
Customize IP address detection
Are automatically identified from the HTTP headers of web requests.

However, in case load balancers, CDN's or proxies are used, the remote IP of the HTTP(S) request might be different from the original IP address from your user devices.

Therefore, Dynatrace watches also the HTTP headers that are most frequently used for identifying the originating IP address of a client connecting to a web server through an HTTP proxy, a CDN or a load balancer.

To view the supported headers, go to Global Settings > Web & mobile monitoring -> IP determination.
3rd-party and CDN content settings
To see the full list of manual as well as auto-detected services that Dynatrace detects out of the box, along with related configuration settings, go to Settings > Web and mobile monitoring > Provider breakdown.
Modern web applications rely heavily on Content Delivery Networks (CDNs) and 3rd-party integrations (for example, web analytics, tag managers, chat bots, A/B testing tools, ad providers, and more). Such web resources have things in common:
- Their requests never hit your data center, hence any failed requests don't show up in your web server logs.

- Their performance and any errors they cause can have a massive impact on your bottom line
Session Replay prerequisites
- OneAgent minimum version 1.169 on all monitored hosts in your environment.
- Real User Monitoring enabled for your application.
- An active Dynatrace Digital Experience Monitoring license
Firewalls configured to allow application/octet-stream content coming from your application; some beacons sent are binary.
- Dynatrace Managed deployments only: A secondary disk configured to store user session data.
- The web UI URL has a trusted certificate
Session replay - configure secondary disk
Data must be stored in a different volume, known as the additional volume; therefore, every node in the cluster must have such a volume allocated to it.

Most are estimated to be around 500kB, the default data retention period is 35 days, and it is always good to have some buffer.

Using these estimates, Dynatrace recommends that you calculate the secondary storage size by applying the following formula: Storage size = Sessions per day Average session size (500kB) Percentage of sessions to record Retention period (35) * Buffer (1.5)
Session Replay can significantly improve the way your team performs tasks such as:
- Resolving customer complaints by reproduces so that you know exactly what went wrong.

- Detecting usability issues by observing and identifying patterns.

- Filtering out the connection data of premium customers so that they receive enhanced support.
Session Replay features a number of settings, controls, and API calls that allow you to selectively record only those user sessions that are relevant to your business case:
- The Cost and traffic control setting, which allows you to decide the percentage of connections you want to save.

- The Opt-in mode, which can be used to decide if data connections should be recorded end to end by default or only when certain opt-in conditions are met.

- The API, which consists of two methods to enable or disable on your source code.
Does Session Replay consume a lot of storage?
- On average, around 100 KB of data is generated for every minute of a access.

Through Previews and Early Adopter releases, we have found that an average access consumes around 500 KB.
Do all sessions replay consume the same amount of storage volume?
No. Access is dependent on a variety of factors, including the size of the application HTML, the duration of the connection, and the interactivity of the users with the application.

On average, connection sizes vary from 100 KB to over 1 MB.
Are sessions replay recorded as videos?
- No. To save connections, monitors changes on the DOM tree of a web application.

- Every visual change of a web application has a corresponding change in the underlying DOM.

- Captures and recreates these changes.

- Because all of this is text-based data, small connection sizes are achieved through compact representation and compression.
What is the bandwidth "session replay" consumption like?
- Because compression takes place on the client side, is the same as the storage: around 100 KB per minute or 500 KB per connection.

- This is advantageous for recording connections from users on mobile devices with limited internet data or with connections that have limited bandwidth.
Session replay Does compression impact the client browser?
- Was designed to have less severe on the UI thread, which smash user experience.

- Most tasks, including an efficient compact algorithm, are executed by a worker thread that runs in the background and doesn't interfere with the UI.
Session Replay Are masking rules applied on the Dynatrace Server?
- are transmitted to the client. This ensures that, by default, confidential data does not leave the client browser.

- settings for recording as well as playback are configurable.
Export user session data
Dynatrace can be configured to continually send user data to a user-provided HTTP Webhook endpoint.

Once enabled, automatically sends JSON data for all monitored person in your environment to the configured HTTP endpoint.

The HTTP server that provides the Webhook must listen for HTTP PUT or HTTP POST requests on a URL specified as part of the configuration.

The data is sent in bulk to improve performance, with a flush every few seconds to keep the data rate near real-time.

The data format is one JSON document per line, so you must split the data by line to get valid JSON documents.
Export user session data that is streamed includes:
- All connections
- User actions
- High-level timing and error data
User Sessions Charting options
- Application
- Browser
- Bounce
- Converted
- Conversion goals
- Browser type
- JavaScript error count
- Location
- ISP
- OS
- Time
- Hour
- Screen resolution
- User action count
- Users
What sortable attributes are available for top users?
- Type
- User
- Location
- Avg. actions/session
- Avg. session duration
- Session count
- Errors and crashes
User session queries via the Dynatrace web UI
1 - From the navigation menu, go to User sessions and click User sessions query.

2 - Type the query and click Run query.
Timeframe selector with USQL
User session data can be filtered based on a selected analysis.
Autocomplete with USQL
Is available for query statements based on the currently entered text.

Is context-sensitive and based on the current cursor context.

It intelligently anticipates what text you may want to type next.
Keywords have been defined to access user session data:
AND, AS, ASC, BETWEEN, BY, DESC, DISTINCT, FALSE, FROM, GROUP, IN, IS, JSON, LIMIT, NOT, NULL, OR, ORDER, SELECT, STARTSWITH, TRUE, WHERE
The following functions have been defined to access user session data:
SUM, MAX, MIN, AVG, MEDIAN, COUNT, YEAR, MONTH, DAY, HOUR, MINUTE, DATETIME, TOP
USQL DateTime Format
yyyy-MM-dd HH:mm.
USQL Basic Operators for comparison
=, !=, <>, <, >, <=, >=, IS, and IS NOT.
USQL Limitations
- Dynatrace stores and retains Real User Monitoring (user actions and user sessions) for a limited period of time. See Data retention periods for details.

- The default result set is 50 but the number of results can be increased to a maximum of 5000 by using the LIMIT keyword.

- The number of potential maximum bucketed results is limited to a maximum of 100,000. The default is 10,000.

- This affects how TOP() is applied when DISTINCT or GROUP BY is used. If no TOP() is specified, 10,000 possible results are spread evenly across the specified columns.

- These default values can be overwritten by specifying a TOP() for each column. The multiplied TOP()- values cannot exceed 100,000 results.

- Joins aren't allowed.

- Only one table is allowed per SELECT.
Host unit
- The size of a host for licensing purposes (based on the amount of RAM provided by a host).

- We use the amount of RAM on a monitored server as a measuring stick to determine the size of a host (i.e., how many host units it comprises).
Host unit hours
Represents the consumption of a unit over a time period
Host unit hours calculation example
4 (host) x 24 (hours a day) = 96 (huh)
4 (host) x 24 (hours) x 10 (days)
900+ host unit hours consumed
Free-trial host unit hours
Are used for Dynatrace demonstration.

When you sign up for a Dynatrace demonstration, you receive a certain number of huh to evaluate Dynatrace.
Host unit hours :: If a host runs for less than 5 minutes
doesn't count against in your quota
Host-unit hours are counted in calendar hours
for example, 10:00 - 11:00 AM and not 10:23 - 11:23 AM).
Host unit hour :: You have a host with 16 GB RAM (which equals 1 host unit) running from 10:00-10:30 AM. At 10:30 you spin up another host of the same size
Dynatrace considers a single unit because don't run concurrently.
Host unit hour :: You start the first host at 10:00 AM and launch another host at 10:30 AM. Then, both hosts run together for 30 minutes and are shut down at the same time
Dynatrace considers this to be 2 units because both run at the same time.
Host unit hour :: One host of size 16 GB RAM is started and stopped three times within an hour:
12:10 - Server start
12:20 - Server stop
12:30 - Server start
12:40 - Server stop
12:50 - Start
13:00 - Stop
Such a scenario equates to 1 unit because true concurrency is taken into account.
Host unit hours :: You have a host with 16 GB RAM (which equals 1 host unit) running from 10:23-11:23 AM. Since the host is running for 2 calendar hours (10:00 - 11:00 AM and 11:00 - 12:00 AM).
it equates to 2 units.
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 the processes it's monitoring.
oneagentmon driver
A special device that appears in your Windows system during Dynatrace OneAgent installation.

It's indispensable for deep monitoring purposes, as it allows Dynatrace OneAgent to add its own library between the system and the monitored processes.
Preview disclaimer
- While planned, there is no guarantee that a feature will ever reach GA status.

- Features can be used free of charge during the period, however they may consume licensing units once they reach GA status.

Features aren't meant to be used in production environments.

Aren't covered by our Support team, but rather by product management. SLAs don't apply.

Qualifying customers are selected based on technical criteria. Final decisions are made by product management and there is no guarantee of participation.

- While participating, you agree to stay in touch and provide feedback.

- Are available to both Dynatrace SaaS and Managed customers.
Davis Assistant
Is the conversational interface for Dynatrace that enables you to ask common performance-related questions in chat applications and voice-enabled devices.

Enables you to easily gain actionable insights into your Dynatrace monitoring data using natural language responses and chart visualizations.

Supported chat applications and devices include Amazon Alexa, Google Assistant, and Slack.
How Davis detects the impact of a problem
Defines whether or not an abnormal situation is affecting infrastructure (INFRASTRUCTURE), software services (SERVICE), or user-facing applications (APPLICATION).

A fourth, special level (ENVIRONMENT) is used to classify a general problem in the monitoring environment.

These are used to report an interruption of your Dynatrace monitoring or ActiveGates.
72 hours
Is used as the default because this gives DevOps teams adequate time to analyze detected problems, even when they occur on weekends.
By default, the Problems dashboard tile as well as the Problems feed
Provide a rolling 72-hour history of open/closed n your environment.
Problems - Limitations to transaction storage
is limited to 14 days.

Therefore, you must perform all detailed analysis and triage within 14 days. For details on how the available granularity of timeseries data diminishes over time
Problem overview page main sections
- Number of Applications, Services, and/or Infrastructure components that are affected.

- The impact analysis section on the left includes details about the direct consequences. It may also provide information about the business impact.

- The Root cause analysis section on the right includes details about the underlying root causes.
Impact analysis
Each problem overview page contains of all direct consequences of the problem (for example, the slowdown of a service) that are revealed based on automated and multidimensional performance baselining.

While baseline violations serve as great trigger events for initiating deeper problem verification, not all real can be detected based solely on statistical alerts.

This is why many problems discovered by Davis (the Dynatrace AI causation engine) provide an section that shows you the causation that the problem has had on your customers and service calls.
Root cause analysis
To identify the problems, Dynatrace doesn't depend solely on time correlation.

It uses all the Dynatrace OneAgent-delivered context information such as topology, transaction and code-level information to identify events.

Using all available context information, Dynatrace can pinpoint the problems in your application-delivery chain and therefore dramatically reduce the alert spam for single incidences that originate.
Visual resolution path
Provides an overview of the part of your topology that has been affected by this problem.

If you click on tile, you will presented with an enlarged view of the way along with the Replay tab on the right (see image below).

This tab enables you to illustrate the problem lifespan in detail by clicking the play arrow at the top.
There are some use cases for which parameterization of automated baselining algorithms may be beneficial
- Setting higher thresholds for applications and services that are still in development or are in the testing stage.

- Setting lower thresholds for mission-critical services within your infrastructure (where default thresholds may be too tolerant).
Data captured from real user
- User clicks
- URL
- IP and locations
Data captured by session replay
- User input
- Images
- Content
- Attributes
- Form fields
- Interactions
Data captured by Server side requests
- URL
- URL Query parameter
- Client IP
- HTTP request/response header
- HTTP post parameter
- Exception messages
- Method arguments/return values
- SQL literals and bind variables
Cookies are used to:
- Monitor site performance.
- Analyze website usage.
- Track user behavior.
v1 session state cookie structure
7$4D3133F359A76AB05AAF39691696858A|6553c6d885d99eec|1|b271251279634e2d|1
Dynatrace stores backups of the following cookies:
- rxVisitor
- rxvisitid
- rxvt
- rxec
The Dynatrace Managed installer is comprised of the following components:
- Server
- Cassandra
- Elasticsearch
- An embedded ActiveGate
- NGINX
With the Cluster Management Console, you can:
- Create user accounts and groups
- Add new cluster nodes
- Add new monitoring environments
Before connecting your Dynatrace Managed environments with your mobile app, check the following requirements:
- In case server is running behind a corporate firewall, you must first set up a Cluster ActiveGate that is accessible from the internet.

- Make sure that your firewall is configured to allow incoming network connections to the configured Cluster ActiveGate domain on the configured port.

- If there's a firewall in front of the Cluster ActiveGate, make sure that it is configured to send the correct security certificates.
Capture performance data, Anonymize personal data and Crash reporting are
app mobile settings
In CPU analysis session, dynatrace offers the following capabilities that allow you to perform enhanced code-level analysis:
- Gain insights into processes and process group hotspots.

- Access background activity, service activity, single request executions, and specific requests.

- Break down and filter data by code execution, network I/O, disk I/O, lock time, and wait times over times.

- Break down and filter data by API over time.

- View forward stack traces and hotspots with reverse stack traces
Gain support for Java, .NET, .PHP, .Node.js, and Golang.
Perform code-level analysis
Diagnostic tools > CPU analysis
Diagnostic tools
- Memory dumps
- Exception analysis
- Top web requests
- Process crashes
- Top database statements
- CPU analysis
Analyze database statements
- Displays a chart indicating the top SQL and NoSQL ********* in your environment over time.

- The chart also highlights a few top based on execution count.

- The table following the chart lists the Top 100.
How database activity is monitored I
Dynatrace doesn't consider methods, but rather commits, queries, and modifications related.

By monitoring such calls, Dynatrace is able to deliver automatic root-cause analysis for performance problems.

For example, if your queries or commits slow down, we'll notify you immediately.

We'll even show you which services are impacted by the problem.
The infographics on the *database* service overview page provide insight into various aspects of databasedatabaseaphics on the *database* service overview page provide insight into various aspects of *database* performance, including
SQL queries or procedures, SQL modifications, SQL transactions, any detected problems or availability issues, hotspots, and more.

The exact list of included tiles depends on the technology you're monitoring.

Each tile contains Response time, Failure rate, and Throughput metrics.
To analyze the individual querys that contribute, click
View database statements
Click any statement to view the full details of that statement. For each statement, Dynatrace shows the number of
Executions/min, Total executions, Total time, Response time median, Response time slowest 10% of executions, and Failure rate.
To understand the response time distribution of the command, click the
Analyze Outliers
The Response time distribution page
shows the number of requests that fell within various requests ranges.

Select any column in the chart to analyze the specific requests that fell within that specific range.

This enables you to see if there are statemtns that are often called and contributes.
The statement with the highest failure rate is listed in the
Current hotspots section of the database service overview page.
Within the Processes section of the Host page
you'll see the most important running on, categorized in groups.
Processes that are well known applications:
- Java program servers (Tomcat, WebSphere, Weblogic, Glassfish, JBoss).

- All other Java programs.

- All .NET programs

- Databases: MS SQL, Oracle, MySQL, Cassandra, SQL server, CouchDB, MongoDB, PostgresSQL.

- Additional technologies: Node.js, PHP.

- Web servers: NGINX, Apache HTTP, IIS.

- Processes that use the Dynatrace OneAgent SDK for C/C++
Processes for which one of the following conditions is met for at least 3 of the last 5 one-minute intervals:
- Avg(CPU) > 5%
- Max(Memory) > 5%
- Network Traffic > 5%.
Where you can fast visualize all process groups and instances
Technologies
Business Impact
- Undertand behavior of your applications.

- Reduce infrastructure costs by otimizing workloads.

- Engineers spend less time troubleshooting leaving them more time to innovate.

- Better and faster releases
Full Stack monitoring
Understand all the relationships and interdependencies, top to bottom, from the end-user experiente to infrastructure health
Enable you to analyze any combination of request metrics and custom metrics (any number based request attribute).
You can use request names, instance information and any request attribute.
Multi-dimensional analysis charts
What is the maximum number of service calls which are based-lined
10000
With the Dynatrace Dynatrace OneAgent SDK, you can't
Create user sessions and user actions
Your business has other digital touchpoints outside of your applications where your customers interact with your brand and can't install Dynatrace OneAgent on devices, what you sugest for this case?
OpenKit
Automatic hotspot analysis
- CPU intensive requests
- Most time consuming requests
- Slowest requests
Current hotsposts
- Requests with slow response time
- High consumption of request resources
- High failure rate
- High CPU consumption
Content capture settings
- W3C resource timing for third party/CDN
- Timing for JavaScript files and images on non W3C supported browsers
- JavaScript error report
- Timed action support
- Visually complete & Speed index
What is average response time?
Represents a normal transaction only when the answer always the same (that is, all transactions run at equal speed) or the answer distribution is roughly bell curved.
How automated baseline calc works?
Compute the normal performance and sends alerts only when an application slows down or produces more errors than usual. Most approaches rely on averages and standard deviations.
Application detection rules limit
1000
Custom metrics are consumed per?
component
A File count parameter actively collected for two hosts equates to
2 custom metrics
A File count parameter actively collected for five different folders across ten hosts equates to
50 custom metrics
A File count parameter actively collected for five different folders (with each folder representing a separate dimensional value) equates to
5 custom metrics
Custom metrics aren't factored into your consumption when no data is written to them for...
1d
Free tier of custom metrics for Dynatrace SaaS and managed environment
100
How many custom metrics are provided for each of your allotted host units in free tier model?
10
Custom metrics in host units hours free tier
n/a
What is maximum free tier limit of custom metrics?
10.000
What is a maximum number of user tag (identifier) rules per application?
twenty
Frequent issue detection configuration
- within applications
- within transactions and services
- within infrastructure
Credential Vault
Provides a secure central storage for data that can be used in Synthetic monitors.
Windows services availability monitoring
Out-of-the-box availability attendance of services.

'Service name' and 'Display name' by select 'Create rule'.

In a large-scale environment, select a host group to simplify management.

Alerting can be enabled for configured services.
User experience score
is session-based and is used to determine the practice delivered across applications within a single session
Calculated for each session.
Reflect the overall performance, usability, and detected errors of each session.
Classified as either Satisfying, Tolerable, or Frustrating.
Types of injection
Automatic, Manual insertion & Retrieve via api
Injection format
Code snipet, inline code & Javascript tag
Waterfall graphs
Display every request and resource downloaded for an action, which can be an entire page load (load action) or the update of a specific in-page context without navigating to a new URL (XHR action).

Resource- and page-level analysis is based on W3C timings.
Initial quota for log monitoring in Dynatrace SaaS
0.5GB of yearly storage
Initial quota for log monitoring in Dynatrace Managed
5 GB per year
Max log data examination
500 MB
You can examine the log files for only the past
7d
You can retain log data for as little as
5 days and up to 90 days
Analyze request metrics like request names, instance information and any request attribute.
Diagnostic tool > Multidimensional analysis
Dynatrace OneAgent monitoring capabilities
Real User, mobile app, server-side service, network, process, host, cloud , vm, docker container, root-cause analysis
Apdex ratings
are application-level scores used to determine the performance of an application
With the JavaScript tag API, you can
- add user tag
- define custom user actions
- report custom errors
- add session and user actions properties
Symbolication
Converts hexcodes and stack traces captured by Dynatrace into human-readable formats.

By uploading files, you can see clear text method names in the stack trace instead of hex codes or cryptic names provided by the obfuscator.
Network zones
Are Dynatrace entities that represent your network structure.

They help you to route the traffic efficiently, avoiding unnecessary traffic across data centers and network regions.​
Diagnostics
- Memory dump analysis
- Crash analysis
- Exception analysis
- Top database statements
- Top web requests
- CPU analysis
Hyperlyzer
- This Dynatrace multidimensional visual interface lets you analyze multiple dimensions of the top three findings of your application's usage.

- You can see details on where your users are located, what browser versions they're using, their operating systems, and the number of different user actions your application has received.
Tomcat Process group availability monitoring

Open a new problem:
- if service requests are impacted
- if any process becomes unavailable
- if minimum threshold is not met
Connecting Azure monitor
- AD tenant permissions to register a new app
- Subscription permissions to assign a new app
- A Service Principal to acess APIs
- ActiveGate v1.161+
Cloud Foundy monitoring
- Enable Dynatrace Garden container monitoring
- Obtain Dynatrace PaaS token and environment
- Upload and deploy the Dynatrace BOSH add-on
Docker Container Monitoring
- Obtain your Dynatrace OneAgent installer URL
- Run OneAgent as a Docker container
Enable Kubernetes or Red Hat OpenShift Monitoring
- Create Dynatrace API and PaaS Tokens
- Install and Configure the Dynatrace OneAgent Operator
Enable Heroku Monitoring
- Copy Environment ID
- Create a new PaaS Token
- Add the Dynatrace Buildpack
Enable VMware Monitoring
- Install (and configure if needed) an ActiveGate
- Connect the Dynatrace and VMware platforms
By default, the length of database statements visualization is limited to:
4KB (KiloBytes)
With code-level database monitoring you can:
- See the impact of your statements on the response times of your services.
- Find expensive statements based on the service calls or user actions from which they originate.
- Find out which services talk most frequently.
- See how much load is placed by individual services.
- Understand why some statements are slow.
- Be notified of increased SQL statement costs and execution.
Scope and usage of services - Entry points:
- Represent the first touch of a transaction with a monitored server-side technologies and are the starting traces of PurePaths on the server-side.

- Usually represent technologies on top of a monitored web server or public API.
Scope and usage of services - Used by applications:
- Are called by web programs, mobile apps, or custom programs (i.e., all programs that are monitored with Real User Monitoring).

- All Used by programs technologies are also Entry point services.
External dependencies:
- Calls to public networks
- Calls to unmonitored hosts
Scope and usage of services - "External dependencies:"
- Represent outgoing calls to systems that aren't monitored with the current Dynatrace environment.
Scope and usage of services - Calls to public networks
- Represent outgoing connections that are resolved to a public IP address and are therefore usually outside of your company network.

- A connection to a payment provider like paypal.com is an example of an external dependency.
Scope and usage of services - Calls to unmonitored hosts
- These represent connections that resolve to a private (internal) IP address and are usually under the responsibility of your organization.

- Therefore dedicated monitoring of these dependencies with Dynatrace OneAgent, or via Custom device monitoring, is recommended to gain visibility into these parts of your environment.
Scope and usage of services - Background activity:
Represent requests that are executed within not visible threads.
Scope and usage of services - Internal only:
Are only called by other monitored technologies. Therefore these technologies don't behave as entry points and they don't have any direct relation to applications.
Remoting services categories:
- Method invocation (RMI)
- Procedure call (RPC)
In the world of Java, Remote Method Invocation (RMI)
is a common means of communication used by JVMs. As there may be many dynamically-created object servers within a single JVM, Dynatrace creates only a single service for each process group.
Dynatrace tracks and monitors each class as a separate request type.
Dynatrace tracks remote procedure calls by
SDKs, Akka, and AWSLambda. Unlike RMI, Dynatrace creates a separate RPC service for each service endpoint.
O* default service
is created when Dynatrace detects a call to a span attachment.
This is just a placeholder that's required to build a valid tree structure.
Note that Dynatrace currently doesn't support detection for spans.
Web server naming issues
In some cases don't have well-defined virtual hosts, names, or sites. May simply be named "localhost". This can result in multiple similar that contain multiple web site instances.
To remedy, configure process-group detection settings.
Web server name terms
- Virtual host
- Server block
- Site
Virtual domain name hosting combines
web requests from multiple hosts, domains, and IP addresses into a single configuration on a web server.
Apache HTTP Server allows you to configure www.dynatrace.com, www.dynatrace.at, and www.dynatrace.us all within the same
virtual host.
NGINX uses
server block concept.
In case of a server block, one needs to configure a server_name.
Site is a concept established in
Microsoft IIS. In kubernetes-based environments, Apache and NGINX web servers are often configured only as "localhost" or just an IP address.
Context root
Within any given web container you may have multiple applications in multiple directories.
For example /admin leads to the admin application while /shop leads to the online store.
In the Java world this is called as a follow.
Microsoft IIS refers to this concept as a Virtual directory.
Most web servers don't even include this as an explicit concept.
Web application ID
- For Java servlets this is done by defining a display-name in the web.xml file.

- For Spring boot you have to define the spring.application.name, which may be in the application.properties file or the application.yml file.

- For Java technologies that don't allow for application naming (and to provide default application naming) you can define the Java command line property.

- For Node.js you can define a name in the package.json file.

- For other technologies, or to provide a default name, you can use the environment variable.
This won't override the naming options mentioned above—it serves as a default for instances when no is available.
*Web services* are detected based on technology-specific *Web service* frameworks. Web servicesWeb service* are detected based on technology-specific *Web service* frameworks. Web services are defined by Web Services Description Language (WSDL),
which is part of your deployment. Defines services, how services are called, and service names. Dynatrace picks up service names along with targetNamespace values and combines these values to uniquely identify each service.
Once merged
the data of individual grouped services can no longer be distinguished—monitoring data is then only available in aggregate for all the grouped services.
Once you create a merged service
original are no longer updated as data sources.
While historical data remains available (for example, for charting), no new data is tracked for the original. All new aggregated data will be assigned to and associated with the new.
If you split a service from a merged service ("unmerge" the service)
the historic data will be available only for the new appointment. All newly captured data will be associated with the new standalone appointment.
Code-level visibility isn't possible if
- A service is of a technology type for which deep monitoring isn't supported.

- A service is of an unrecognized or unsupported technology.
Other reasons services may be classified as opaque
- process is offline though still makes calls to it.

- A process never started processing a request

- A process hasn't completely restarted following Dynatrace OneAgent installation.

- The framework processing the request at the specific port is not currently supported by OneAgent.

The framework is supported, but OneAgent has run into a technical problem.
Reports :: Dynatrace score
- Applications
- Services
- Infrastructure
- Top problem root causes (3)
Reports :: Application score
- 3 Most used
- Apdex
- Problematic users actions
- User actions affected by problems
- Top gainers by user actions
- Top losers by user actions
- Top 6 geolocations by user actions
Reports :: Services score
- Failure rate
- Problematic calls
- Top 10 services by load
User actions types
Load, XHR & custom
User action duration components
Network time, Server time & Frontend time
Max Key user actions per environment
500
Mark as key user action gives you the option to:
- Pin to dashboard.
- Change the Apdex and anomaly detection configuration.
Max key user actions per applications
100
Action name detection
inner HTML, caption, hint, HTML elements such as button and anchor
With the key user action feature, you can customize the Apdex thresholds for each of these user actions. You can use this feature to monitor key actions with a
dedicated dashboard tile and track historic trends.
SLO
You can review the current health status, error budgets, the defined target and an additional warning target, along with the evaluation window of all your objectives.
Service-Level Indicator (SLI)
Used to measure the successful service delivery.
Typically refer to metrics such as service success rate, crash-free mobile app users, successful synthetic test runs, or response time.
SLO :: Target
Defines the planned goal to achieve in terms of service delivery.

This could be, for example, that 99.99% of all service calls must return without an error, or that 95% of all service requests must be fulfilled in under 2 seconds' response time.
SLO :: Evaluation period
Is necessary to standardize communication concerning the result. Without this, the notions of availability are subjective.
SLO :: status
The current evaluation result, expressed as a percentage.

The semantics of this percentage (for example, 99.3% of all service requests are successful, or 99.99% of all website users are "satisfied" in terms of Apdex rating) and the target defined for this percentage are up to the SRE team.
SLO :: error budget
The remaining buffer until the defined target is considered as failed.

For example, if defines a 95% target and its current status is evaluated as 98%, the remaining problem is the difference between the status and the target.
An SRE team is responsible for
finding good service-level indicators (SLIs) for a given service in order to closely monitor the reliable delivery of that service.
SLIs can differ from one service to the other
as not all services are equally critical in terms of time and error constraints.
Service-level availability SLO
is measured by dividing the number of successful service calls by the total number of service calls
User experience SLO
which is based on the Apdex measurement, representing the percentage of people who are SATISFIED out of the total number of people who are using a web or mobile application
Mobile crash-free users SLO
which measures the percentage of users within your device applications
Synthetic availability SLO
which represents the percentage of successful robotic tests related to the total number of executed tests
A service performance SLO represents
the percentage of "fast" service calls from the total number of service calls, where "fast" is defined with a custom condition.
Problems home dashboard elements
- Severity
- Status
- Impact
- Alerts
- Context
- Tags
- Closed
- Opened
- Entities
- Root cause
- Start Date
- Duration
- Alerting profiles
Synthetic home monitor dashboard itens
- Status
- Type
- Device profile
- Location
- Application
- Tags
Synthetic home browser monitor profile dashboard elements
- Analyze sessions
- View report
- Availability
- Total downtime
- Locations
- Visually complete for load actions
- Visually complete for XHR actions
- Total duration
- Location
- Availability overage
- Events and actions
:: Type, Performance (Average) & Details
- Properties
- Problems
- Events
- Errors
- Monitored applications
:: Name, Load actions, XHR Actions, Custom actions & Actions/min
- Worldmap
Synthetic home application dashboard filters
- Continent
- Country
- Location
- Region
7 Days reference period applies
- Applications
- Databases
- Services
Synthetic Availability report
- Subscribe weekly
- Subscribe monthly
- Disponibility
- Performance
- Locations
- Once every (time)
- Outages monitored
- Total downtime
- Monitor runs
- Slowest geolocation
- Slowest day
- Performance violations
- Outages by geolocation
- Top findings
- Best and worst performinc geolocations
- Performance trends
Availability and performance trends
This section of the report charts data trends over time
Outages by geolocation
- This section of the report displays, by plaves, detected outages and instances of slow performance during the week.
- A world map displays places and indicates the best- and worst-performing locations.
Synthetic home HTTP monitor profile dashboard elements
- Availability
- Response time
- Locations
- Total outages
- Total downtime
- Response size
- Problems
- Properties
:: Frequency, Locations, Requests Pre/post-execution scripts
- Status codes
- Show status code of
- Show data for
- Requests
:: Method, Request name, Request URL, Pre-post-execution scripts, Response time & Details
- Events
- Services covered by this mxxxxxx
- Applications covered by this mxxxxxx
HTTP Monitor settings
- Setup
:: Name & Set cookies
:: Assign to a web application
:: Connect another application
- Requests
:: Visual mode & Script mode
:: Add request
- Frequency and locations
:: Monitor my website every (1,2,5,10,15,30 & 60 minutes)
:: locations selected
- Outage handling
:: Generate a problem and send an alert when is unavailable at all configured locations.
:: Generate a problem and send alert when unavailable for one or more consecutive runs at any location
::Alert if (x) /x locations is unable to access my web application (on the first, 2, 3, 4 or 5 times consecutively.
- Performance thresholds
:: Performance thresholds enabled
:: Add new performance threshold
Browser clickpath Monitor settings
- Setup
:: name. device(desktop, iphone, samsung)
:: Screen size, Bandwidth (download, upload, latency (No throttling, DSL, GRPS, wifi), User agent
:: Select a key performance metric
:: Connect another application
- Recorded
:: Add synthetic event
- Frequency and locations
::Check my website every (5,10,15,30min,1h,2h,4h)
:: location(s) selected
- Outage handling
:: Generate a problem and send an alert when is unavailable at all configured locations.
:: Generate a problem and send alert when unavailable for one or more consecutive runs at any location
:: Alert if the selected location unable to acess my web application (on the first, 2, 3, 4 or 5 times consecutively.
:: Ignore specific status codes (400 to 599)
- Performance thresholds
:: Add threshold
- Advanced setup
::Enable additional headers, Block specific requests, Set cookies, Bypass Content Security Policy of pages, Capture performance metrics for pages loaded in frames, Enable custom JavaScript Agents settings
- Metrics
:: Enabled metrics for this Mxxxxxx
:: Enable metrics for this environment
Settings > Preferences > Data privacy and security
- Mask end-user IP addresses and GPS coordinates
:: Mask all IP addresses
:: Mask only public IP addresses
- Mask personal data in URIs
- Mask user actions (web applications only)
- Log all audit-related system events
Web application settings > General
- Name
- Real User Monitoring (on/off)
- Analyze xxx% of user sessions
- Select Key performance metric
::Visually complete, User action duration, Speed index, DOM interactive, Load event end, Load event start, HTML downloaded & Time to first byte
- Key performance metric thresholds
:: Satisfactory (0to3s), Tolerable (>3to12s), Frustrating (>12s)
Fallback metric
:: Satisfactory (0to3s), Tolerable (>3to12s), Frustrating (>12s)
- Config error impact on Apdex
Web application settings > Data privacy
- Global settings
:: Mask end-user IP addresses and GPS coordinates
:: Mask personal data in URIs
:: Mask user actions (web applications only)
- User tracking
:: Use persistent cookies for user tracking (on/off)
- Data-collection and opt-in mode (on/off)
- 'Do Not Track' end-user browser settings
:: Comply with 'Do Not Track' browser settings (on/off)
:: Capture anonymous user-session data for "Do Not Track" enabled browsers (radio button)
:: Disable Real User Monitoring for "Do Not Track" enabled browsers (radio button)
Web application settings > Capturing > User tag
- Add tag (identifier) rule
:: Expressions type to capture: (CSS selector, JavaScript variable, Meta tag, Cookie value, Query string & Server side request attribute)
:: CSS selector (Specify a CSS selector. This mechanism will capture the first match's innerText/textContent value. To retrieve a specific attribute value of the element, append the '@' symbol, followed by the attribute name. i.e. '#someDomElement@someAttribute'_
- Define case sensitivity behavior
:: Ignore case (on/off)
:: Apply cleanup rule (on/off)
Web application settings > Capturing > User actions
- Add placeholder
:: Source (Page URL, Page URL: Anchor & Path, Source URL, Source URL: Anchor & Path, Xhr URL: Anchor & Path, Page title, Element identifier, User interaction, CSS selector, JavaScript variable, Meta tag, cookie value, Top Xhr: Anchor & Path & Custom action name.
:: Preview of your placeholder
- User actions naming rules
:: Split user actions by domain (on/off)
:: Case insensitive naming (on/off)
:: Use values of first detected Load action (on/off)
- Add naming rule
:: Add condition (Input, Operator)
- Show preview
Web application settings > Capturing > Sessions and action properties
- Add property
::Property packs & custom defined property
- Property usage quotas
Web application settings > Capturing > Async web requests and SPAs
- JavaScript framework support
:: AngularJS and Angular (on/off)
:: Dojo (on/off)
:: ExtJS, Sencha Touch (on/off)
:: ICEfaces (on/off)
:: jQuery, Backbone.js (on/off)
:: MoonTools (on/off)
:: Prototype (on/off)
:: ActiveXObject detection (on/off)
- Generic support
:: Capture XmlHttpRequest (XHR) (on/off)
:: Capture fetch() requests (on/off)
Web application settings > Capturing > Content capture
- JavaScript framework support
:: W3C resource timing for third party/CDN (on/off)
:: Timing for JavaScript files and images on non W3C supported browsers (on/off)
:: JavaScript error report (on/off)
:: Timed action support (on/off)
:: Visually complete and Speed index (on/off)
- Configure thresholds for Visually Complete and Speed Index
:: Thresold (xx pixel)
:: Inactivity timeout for load actions (xxx ms)
:: Mutation timeout for XHR and custom actions (xx ms)
:: Excluded URL list ( url path)
:: Ignored mutations list (query CSS)
Web application settings > Capturing > Advanced setup
- Advanced settings
:: Content resource settings, Monitoring exclusions
JavaScript library settings, Cookie and header settings, Advanced JavaScript tag settings
Advanced event handlers, Reset settings
- Content resource settings
:: Send W3C resource timing metrics for each resource file (on/off)
- Configure thresholds for top findings
- Exclude/Include IP addresses from monitoring
:: These are the only IP addresses that should be monitored (on/off)
- Exclude XHR requests from monitoring
:: Specify a regular expression to match all URLs that should be excluded from becoming XHR actions./
- Exclude/Include browsers from monitoring
:: Add browser exclusion rule
- JavaScript library
:: Specify location for JavaScript library file: (server path/)
:: Specify path where JavaScript tag should send monitoring data: (url path)
:: Custom configuration properties (key value pars)
:: Request path ID settings
- Cookie and header settings
:: Use the Secure cookie attribute for cookies set by Dynatrace (on/off)
:: SameSite cookie attribute (Not Set, None, Lax, Strict)
:: Optimize the value of cache control headers for use with Dynatrace real user monitoring (on/off)
- Real User Monitoring for AWS Lambda Functions (enter a regular expression)
- Advanced JavaScript tag settings
:: Enable instrumentation of unsupported Ajax frameworks (on/off)
:: Special characters to escape (additional special characters)
:: Max. character length for action names (xx chars)
:: Max. number of errors to be captured per page (qtd error numbers)
:: Set alternative for data-dtname (For example: aria-abel)
- Additional event handlers and wrappers
:: Use mouseup event for clicks, Click event handler, Mouseup event, Blur event, Change event, toString method
:: Max. number of DOM nodes to instrument (xxxx)
- Wrappers for addEventListener and attachEvent
:: Click, MouseUP, Change, Blur, TouchStart & TouchEnd, (ALL on/off)
:: Global event capture (MouseUp, MouseDown, Click, Doubleclick, KeyUp, KeyDown & Scrool (ALL on/off)
:: Additional events to be captured globally as user input: (For example, dragstart, dragend)
- Reset settings
Web application settings > Session replay behavior > Session replay
- Enable session replay (on/off)
Web application settings > Session replay behavior > Conversion goals
- Add goal
:: Name
:: Type of goal (Destination, User Action, Session Duration & Number of user actions) begins with, ends with & contains
:: Type URL of path
:: Case sensitive (on/off)
Web application settings > Session replay behavior > Usability analytics
- Enable rage click detection (on/off)
Web application settings > Metrics
- Create metric
:: Metric
:: Metric name
:: Metric key for API usage
:: Only calculate for user actions matching the following filters
:: Split by (on/off browsers & geolocations)
Web application settings > Errors
- Ignore HTTP errors in Apdex calculations (on/off)
- Add HTTP error rule (Match by error code, by errors that have failed image requests & by errors tath have CSP violations ALL on/off)
:: Filter by URL (url begins with..)
:: Capture settings (capture this error, Include error in Apdex calculations & Include error in Davis ai Problem detection and analysis (ALL check on/off)
- Custom errors
:: Ignore custom errors in Apdex calculations (on/off)
:: Add custom error rule (same options above)
- JavaScript errors
:: Ignore JavaScript errors in Apdex calculations
Web application settings > Anomaly detection
- Use global anomaly detection settings (on/off)
- Detect key performance metric degradations (on/off)
- Detect traffic drops (on/off) (Alert if the observed traffic is less than xx% of the expected value)
- Detect traffic spikes (on/off) (Alert if the observed traffic is more than xxx% of the expected value.)
- Detect increases in failure rate (automatically or using fixed thresholds)
- Alert if the percentage of user actions affected by JavaScript errors increases by xx% absolute and by xx% relative.
- To avoid over-alerting do not alert for low traffic applications with less than xx actions/min.
- Reset to defaults
- Reference period Reset
Web application settings > Injection
- Select the type of injection
:: Automatic, Manual or Retrieve via API
:: Select the format (OneAgent JavaScript path, Code snippet & Inline code
- Add custom rule
Mobile app settings > Instrumentation wizard
- Android
- iOS
- tvOS
- Cordova
- React Native
- Flutter
Transactions and services home filter options
- External services
- Kubernetes:: cluster, namespace, namespace label, workload, workload label
- Name
- Problem impact
- Process group
- Request attribute
- Service type
- Tag
- Technology
Transactions and services - Service type home filters
- Background Activity
- CICS service
- Custom service
- Enterprise Service Bus service
- IMS service
- Key value store
- Messaging service
- Queue listener service
- RMI and RPC service
- Web request service
- Web service
User sessions filter value options
- Application & type
- Browser monitor, browser family, type & version
- City, Continent, Country & Region
- App version, Crashes, Device & Manufacturer
- OS family & version
- Bounce, Conversion goal, converted, errors, IP, ISP, Live, Screen resolution, Session duration, Session replay, User tag, User type & Users
- Date property, Double property, Long property & String property
- Rage click count & User experience score
- User action count, User action duration & User action name
Network Zones benefits
- Compressing traffic
- Optimizing traffic routing
- Preventing unrelated traffic in between data centers and regions
Settings > Monitoring overview
- Monitor another host (button)
- Install ActiveGate (button)
- Set up Agentless or AMP monitoring (button)
- Monitor a mobile app (button)
- Monitor a custom application (button)
- Download Dynatrace Agent or ActiveGate installer(link - include previous versions of OneAgent - installer, build and revision)

- Tabs:
:: Applications (remove and edit application)
:: Hosts (Monitoring Off/On and edit option)
:: Process groups (Enable / disable deep monitoring and edit option)
Settings > Naming rules
- Add new rule (button)
:: Rule name
:: Host name format
:: Rule applies to entities matching the following properties (All host groups and All technologies)
:: Conditions (Host characteristics and equals)
- Preview (button)
- Create rule (button)
- Filter by rule name (move up/down, Delete, Disable/Enable and Edit)
Service Flow & PurePaths filters - Topology
- Called service
- Called by
- Instance
Service Flow & PurePaths filters - Request property
- Request
- HTTP method
- HTTP response code
- Request attribute
- Proxyed by
- W3C trace id
- Web request URL
- URL host
Service Flow & PurePaths filters - Timing
- Response time
- CPU time
- Suspension time
- Wait time
- Lock time
- Disk I/O time
- Network I/O time
- Time spent in database calls
- Time spent in database calls to services
- Processing time
Service Flow filters - Other
- Number of calls to services
- Number of calls to databases
- Purepath diagnostic messages
Service flow - Passing transactions (right side window menu)
- Avg. response time
- Avg. time spent in called services
- Requests
- Failed requests
- Calls to other services
Service flow - Infrastructure (right side window menu)
- Num of Services instances
:: Avg. response time
:: Requests
:: Failed requests
:: Running on
Settings > Davis data units pools
Define the maximum is allowed to be consumed within one month or year.
- Metrics
:: Enable limit
- Log Monitoring
:: Enable limit
- Serverless
:: Enable limit
Network overview - filter menu options
- CF Foundation
- Data center
- Host group
- Operating system
- Monitoring mode
- Name
- Problem impact
- State
- Technology
- Type
- Tag
Network Overview
- Traffic, Connectivity & Retransmissions
Network Overview - Traffic
- In
- Out
Network Overview - Connectivity
- refused
- timeout
Network Overview - Retransmissions
- received
- sent
Network overview - Environment details
- Hosts
- Interfaces
- Processes
Network overview - Hosts details
- Traffic, Retransmissions & Connectivity
Network overview - Interfaces details
- Traffic, Retransmissions, Connectivity, Packets, Dropped packets & Errors
Network overview - Processes details
- Traffic, Retransmissions, Connectivity, Handshake RTT & Throughput
Host details page
- Infographics overview
- Dynamic measure display
- Problem history
- Availability
- Detected processes
- Events log
- Log files
Service details page
- Infographic overview
- Dynamic requests
- Static requests
- Problem history
- Hotspot Analysis
- Architecture dependencies
- Log events
Databases home filter options
- Cloud provider
- Database vendor
- Name
- Problem impact
- Tag
All data exchanged between Dynatrace OneAgent, ActiveGate, and Dynatrace Cluster
is encrypted in transit.
Data is serialized and deserialized using
Google Protocol Buffers.
Dynatrace SaaS uses
TLS 1.2 (SSL Labs Grade A+).
In Dynatrace Managed, you can configure TLS versions
as well as cipher suites and you can use your own SSL certificates.
Dynatrace SaaS uses Amazon Elastic File System (EFS) and Amazon Elastic Block Store (EBS)
with AES 256 encryption.
Encryption keys are managed by Dynatrace
using AWS Key Management Service (KMS).
Dynatrace Managed customers must configure their own
hard disk encryption and manage encryption keys on their own.
In Dynatrace SaaS, you can manage your users by setting up
user groups and permissions and SAML.
In Dynatrace Managed, users are managed by
configuring user groups, SAML, OpenID, and LDAP.
LDAP authentication limitation
does not support multiple domains
Are SAML users added automatically to Dynatrace Managed?
are included following successful authentication
Every 24 hours Dynatrace SaaS performs
data backups to a different AWS data center in the same geographical region.
The maximum recovery point objective (RPO) for a full cluster
is 24 hours
Dynatrace Managed offers a built-in backup mechanism
which you must configure.
Operational status and incidents are always available at
dynatrace.status.io
In Dynatrace SaaS, new features are delivered every
two weeks.
In Dynatrace Managed, updates are delivered via Dynatrace Mission Control. New features are delivered every
4 weeks.
Dynatrace Managed - Audit logs
- Any change to Dynatrace configuration and any change to API tokens
- Logins and Logouts
Dynatrace Managed - Enable audit logging
Settings > Preferences > Data privacy and security > Log all audit-related system events
Dynatrace Managed - Audit logs are retained for
30 days and automatically deleted afterwards.
Dynatrace Managed - You can also enable audit logs via
Data privacy API
Audit logs API - GET audit log
Works on Dynatrace SaaS & Managed Dynatrace Environment
SaaS - Dynatrace API - Default Access Payload limit
1 mb
SaaS - Dynatrace API - Default Payload limit for Configuration - Mobile Symbolication API
100 MB
SaaS - Dynatrace API - Default Payload limit for Extensions and Plugins
50 MB
SaaS - Dynatrace API - Environment - Request throttling
50 per minute
SaaS - Dynatrace API - Synthetic endpoints - Request throttling
1000 per minute
SaaS - Dynatrace API - Configuration - Request throttling
200 per minute
Dynatrace SaaS - When you reach the limit for Dynatrace API
requests return the response code 429.
There is no rate limit in Dynatrace API
for Dynatrace Managed instalations
Dynatrace API - Response code 200
OK
Dynatrace API - Response code 201
Created
Dynatrace API - Response code 204
Not content
Dynatrace API - Response code 400
Bad request
Dynatrace API - Response code 401
Unauthorized
Dynatrace AP - Response code 404
Not found
Dynatrace API - Response code 429
Too many requests
Cluster
- The Dynatrace monitoring infrastructure.

- Contains one or more nodes that are set up using the Dynatrace Managed installer.
Cluster ActiveGate
- It is downloaded from your Dynatrace Managed and installed within your infrastructure.

- Similar to a proxy, reduces bandwidth requirements by encrypting and compressing network communication.
Dynatrace Managed - Mission control - Data exchange - Installation
Frequency: Once during installation and during every upgrade
Cluster request: License key
Response: Account name, license name, OneAgent installation flag (true/false), OneAgent download URL
Dynatrace Managed - Mission control - Data exchange - Registration
Frequency: Once (after first startup)
Cluster request: License key, cluster ID
response: Registration status, username, password
Dynatrace Managed - Mission control - Data exchange - License
Frequency: Once every 5 minutes
Cluster request: No cluster request
response: License status, cluster ID, license key, license details, license model
Dynatrace Managed - Mission control- Data exchange - Health check
Frequency: Once every 5 minutes
Cluster request: Cluster ID, privacy settings, time zone, traffic size, update/maintenance window. Each cluster node adds technical details including OS name and version, number of CPU cores, CPU load, total RAM, free RAM, total disk storage, used storage, server state, master node flag (true/false), and startup time stamp. Each Cluster ActiveGate adds its version, OS name and version, status, certificate issuer, and type (e.g., beacon forwarder).
response: Health status, message
Dynatrace Managed - Mission control - Data exchange - Consumption
Frequency: Once each hour
Cluster request: Cluster ID, consumption timeframe. Each environment adds the number of new problems, Real user monitoring sessions, synthetic monitors. Every host adds a category, a list of monitored technologies, and monitoring timeframes. For each synthetic monitor, the ID, description, type, success count, failure count and action count are transmitted. See Export licensing data.
response: Status, remaining Real user monitoring sessions, consumed Real user monitoring overage, host units overage, remaining synthetic monitors, consumed synthetic monitors overage. For each environment, its ID, consumed RUM sessions, consumed synthetic monitors, and host units are returned.
Dynatrace Managed - Mission control - Data exchange - Heartbeat
Frequency: Once each minute, or every 5 minutes if remote access is disabled.
Cluster request: Cluster ID, node ID, source type (e.g., server)
response: Remote UI request flag (true/false), Websocket URLs
Dynatrace Managed - Mission control - Data exchange - Updates
Frequency: Once each hour
Cluster request: No cluster request
response: For cluster updates: version, description, download URL, size. For Dynatrace OneAgent and JavaScript tag updates: label, version, download URLs. For ActiveGate updates: label, version, download URLs
Transactions and services home - Maximum current values show
1k
Host > {Host Name} {...} > Analyze process connections
- Number of processes involved in each communication
- Transfer rate
- Number of newly established connections per minute
- When click in each connection process node you'll see network Transfer, Connectivity and Retransmissions rates.
How to exclude disks and network traffic from host monitoring?
- Select Hosts on the navigation menu and select the host you want to configure.
- In the host menu ("..."), select Settings to open the Host settings page.
- Depending on what you want to exclude, select Exclude disks or Exclude network traffic.
SPA
- Is a web application or website that interacts with the user by dynamically rewriting the current web page with new data from the web server, instead of the default method of the browser loading entire new pages.

- The goal is faster transitions that make the website feel more like a native app.

- In single-page application, all necessary HTML, JavaScript, and CSS code is either retrieved by the browser with a single page load, or the appropriate resources are dynamically loaded and added to the page as necessary, usually in response to user actions.

- The page does not reload at any point in the process, nor does it transfer control to another page, although the location hash or the HTML5 History API can be used to provide the perception and navigability of separate logical pages in the application.
Settings > Anomaly detection
- Application
- Services
- Database services
- Infrastructure
- Extension events
- NAM events
- Custom events for alerting
- Frequent issue detection
If you don't see performance data for some of your customers on the world map, it may be because those customers have
private IP addresses
How you can map private IP addresses to geographic regions to make them visible on the map?
Settings > Web and mobile monitoring > Map IP addresses to locations
In Multidimensional analysis you can view max
top 100
In user sessions overview page you can view
last 50 results and page for + 50
View all Dynatrace IPs used for outbound connections
Deploy Dynatrace > OneAgent > Download OneAgent > Linux (bottom of page)
Real User Monitoring - Users type
- Real
- Robots
- Synthetic
Web application details application page - Load Actions and XHR actions
- Impact of user actions on performance
- Composite metrics across response times
- Top 3 included domains
- Problems
- Availability
- Top 3 user actions
- Top errors
- Events
Web application details application page - Errors
- Errors by type: Request errors, JavaScript errors & Custom errors
- Errors during user actions: Errors during user actions & Errors between user actions
- Errors by origin: 1st party errors, 3rd party errors & CDN errors
- Top errors: Requests, JavaScript & Custom
- Composite metrics across response times
- Top 3 included domains
- Problems
- Availability
- Top 3 user actions
- Events
Application details - Errors by type
- Request
- JavaScript
- Custom
Application details - Errors during user actions
- during
- between
Application details - Errors by origin
- 1st party
- 3rd party
- CDN
Application details - Top errors
- Requests
- JavaScript
- Custom
Application details - User Behavior
- Active sessions
- Actions per session
- Entry/Exit actions
- Bounce rate
- Conversion goals
Smartscape topology home itens
- Applications
- Services
- Processes
- Hosts
- Data centers
- (...) Hide inactive and Hide unconnected)
When does a user session start?
when the first user action is initiated.
When does a user session end?
- After 30 minutes of browser inactivity.

- When closes their browser. Note that the only finish when the browser is closed and remains live in the UI until 30 minutes of inactivity.

- Once the limit of 200 actions per access is reached.

- By calling the JavaScript API function dtrum.endSession(). This function can be used within your application to end user automatically when, for example, the user logs out.
How long does it take for a user session to be visible in the user session search?
Typically, is visible in the search within 4 minutes. However, this could sometimes exceed to 10.5 minutes.
How are user actions grouped into user sessions?
Dynatrace stores some information in cookies and local storage.

This enables the correlation of clicks and calls into one access.

This information is erased however when (1) the browser is closed, (2) the person clears their browser cookies, or (3) the person cleans up their local storage.
Consider another example: A user session is initiated, but after a few minutes the user walks away and leaves their browser window open
If person were to close their navigator before taking their break, a new sit will start when the person returns to the application, regardless of how long they were away from their computer.
How is user session duration calculated?
is the elapsed time between initiation of the first user action in a sit and the completion of the last user action in the sit.
How to differentiate live user sessions from completed sessions
are colored light purple and the arrow head at the end of the timeline indicates that new actions can be added.
For complete user access, there is no arrow head.
Can you analyze a single web session across different domains?
No, for technical and security reasons.
Suppose your user visits two completely different domains during a single "session". How would Dynatrace capture this, given that both domains are instrumented with Dynatrace Real User Monitoring?
- The access starts with the page load for the web page of the first domain, and it ends when you click a link that leads you to a web page with a different domain (the second domain).

- The other access starts with the first page load on the second domain, and it ends when any of the criteria for ending a user session is met.

Why this happens:
- Technical: cookies can't be shared across domains (except for subdomains).

- Security: it's a security feature of browsers and a limitation that all vendors share.
Bounces and conversions
are available for completed user sessions.
Key performance metrics
- User action duration
- Visually complete
- Speed index
- DOM interactive
- Load event end
- Load event start
- HTML downloaded
- Time to first byte
How do I request updates to the MaxMind database when IP addresses don't resolve correctly?
You can apply update their by submitting the form at https://support.maxmind.com/geoip-data-correction-request/.

You can check your address against the database at anytime using the form at https://www.maxmind.com/en/geoip-demo.
For web applications, Dynatrace uses the
MaxMind Geo2 Database to map and resolve IP addresses to geographical locations.
In cases where you don't have access to your web server and therefore can't install Dynatrace OneAgent on the host, you have these options
- Set up agentless Real User Monitoring if you have access to your code (for example, when using Heroku Platform or Google App Engine).

- Set up the Real user monitoring browser extension if you cannot access your code (for example, when Dynatrace SaaS-hosted are provided by a 3rd party vendor.
Define applications for Real User Monitoring:: Best practices and recommendations
- Team ownership so you can easily make use of management zones for access restrictions.

- Avoid renaming the My web application placeholder as it includes all user actions on all domains that are not included in an application rule.

- Separating based on top-level domains works best as Dynatrace cannot correlate user actions across top level domains with specific user sessions. This correlation is done via a cookie and therefore only works if the cookie can be set on the same top level domain.

- Low traffic should be grouped together. If you create based on a domain that has less than 10 actions per minute, Dynatrace won't automatically detect anomalies for this newly created.

Are processed in sequence for each request. More means more processing time and are processed within the Dynatrace OneAgents, you should try to have the settings for the most used have the most traffic at the top of the list.

- The more specific application should be defined first, while the more generic should be at the bottom of the list.

- Depending on your requirements, you can adjust the monitoring consumption and configure Real User Monitoring accordingly.
The application rules are processed in sequence for each request. More rules means more processing time and as the rules are processed within the Dynatrace OneAgents
you should try to have for the most used that have the most traffic at the top of the list.
Define applications for Real User Monitoring - Suggested approach Auto-injection
When can be easily identified based on domains and you want to create from already captured monitoring traffic.
Define applications for Real User Monitoring - Application detection rules :: Auto-injection
- When you want to create new or when dividing your traffic based on top domains isn't sufficient.

- Use this to define more complex patterns to group your monitoring traffic.
Define applications for Real User Monitoring - Manual approach (aka "agentless monitoring") :: Manual insertion
When you don't have access to the host but you have access code.
Define applications for Real User Monitoring - Browser extension approach :: Browser extension injection
When you don't have access to either the host of your web or the application code
Define an application based on suggestions
1 - Select Applications from the navigation menu > My web application.
2 - Scroll down to find the Top 3 included domains panel > View full details.
3 - Expand a domain entry in the Top domains list by selecting the arrow button in the Transfer domain column > Create new application.
(Alternatively, you can add the domain to an existing application by selecting Transfer.)
How to configure Real User Monitoring for XHR (AJAX) actions
1 - Select Applications from the navigation menu and
select the application you're interested in to access the application's overview page.

2 - Click the Browse (...) button in the upper right corner and choose Edit to access the settings for the specific application > Capturing > Async web requests and SPAs.

3 - In Generic support sessions, select Capture fetch() requests and select Capture XmlHttpRequest .

4 - In the JavaScript framework support select relevant for your web application: Angular, Dojo, EXTJS, Sencha Touch, ICEfaces, jQuery, Backbone.js MooTools, Prototype, and ActiveXObject detection.
Enable the timed action support setting
- Depending on the XHR (AJAX) framework or architecture of your application, you may additionally need to Activate this resource.

- This adjust is necessary in situations where an application doesn't trigger XHR (AJAX) calls directly in event handlers of HTML elements.
User action names are generated automatically
based on triggered load or XHR URLs and are often difficult to read and remember.
When your application handles a lot of user requests and interactions per day
tracking them becomes difficult when you don't have the means to group them logically.
User action naming rules give you the option to
generate consistent and readable that can be easily grouped and tracked throughout the application.
Action naming rules can be created and customized for each application individually and then used throughout Dynatrace in
- user experience charts
- graphs
- conversion goals (for example, add-to-shopping- cart and newsletter-sign-up)
- key user actions
- top consumers list
Placeholders allow you
to add dynamic elements to custom naming rules.
Placeholders are useful in cases where you want to have dynamic input values (i.e:, the URLs of blog posts visited by your users) included in user action names or when you want to remove or replace certain parts of an input value
for example, connection session IDs and group them under a common nomenclature name.
Placeholders consist of the following three elements:
- An input value, such as a page URL

- A processing step that extracts or replaces parts of the input (optional)

- The name, which is used in the user action naming rule
To make placeholders easier to use, Dynatrace provides a set of pre-defined placeholders, such as
pageUrl, sourceUrl, xhrUrl, Top XHR URL, and pageTitle.
To help you make the most of placeholder, we've introduced the following processing steps:
- extract
- replace
- replace text
- replace IDs
- extract and replace with regular expression
User tracking
- When enabled, Dynatrace Real user monitoring sets a persistent cookie in computer that detects if the browser has been used previously to access your application.

- When disabled, the Returning vs. new Real user monitoring metric no longer works because Dynatrace is no longer able to correlate anonymous connections with tagged sessions.
With opt-in mode enabled, the injected Real User Monitoring JavaScript code won't capture any data or set cookies. Data capture and cookie usage can, however, be enabled for
individual users using the JavaScript API call dtrum.enable(). This allows you to implement an setting that enables your customers to comply with the content privacy standards of their region.
During the course of Dynatrace monitoring—even following Real User Monitoring code snippet injectionn* into your application—if your customers don't have a Dynatrace cookie set in their browser
no data will be captured. You must explicitly call the JavaScript API call dtrum.enable() from each of your customers' browsers to activate data capture.
Real User Monitoring detects the following interaction types in your application:
- Click
- Double click
- Mouse down
- Mouse up
- Key down
- Key up
- Scroll
- Touch start
- Touch end
- Change
Dynatrace also provides a JavaScript API call that can disable monitoring once it's been enabled
using a dtrum.enable().
Using the call dtrum.disable()
you can implement a dialog that enables your end users to stop sending monitoring data to Dynatrace, even after it's been explicitly enabled. This API requires Dynatrace OneAgent v1.145 or above.
Opt-in mode isn't
enabled by default.
Capture anonymous user sessions for "Do Not Track"-enabled browsers
(Enabled by default) Collect activity from the browser, but excludes all personal information that could lead to the identification of the people. The IP address is masked and no client tag information is sent.
Comply with 'Do Not Track' browser settings
is enabled by default for both new and existing applications.
Composite metrics across response times
helps you figure out from a high level perspective where your performance focus should lie.

You can identify, for example, whether the duration up to the time to first byte is an issue for your application or you should focus on user perceived loading performance, indicated by Speed index and Visually complete.
Top 3 included domains
that contain the largest number of actions that have been automatically detected by Dynatrace OneAgent in your environment.
Top 3 user actions
list shows you the three slowest.

Are sorted based on priority (high priority are listed first) and total time consumed (duration multiplied by number of interactions).
What data is displayed in the Waterfall analysis view?
- is primarily built around W3C timings.
- Document requests
- XHR requests
- Resources
Document Requests
- Displays all content that is identified as the page load of the user action. This includes the initial HTML, as well as any other content that's displayed in frames.

- Each entry contains the details that are captured by W3C navigation timings.
XHR requests
Displays all resources that were sent via *** or fetch(). These entries contain all the details that are accessible through the W3C resource timings, in addition to the JavaScript callback execution time.
Resources
Displays all W3C timing details.
Top findings for waterfalls
help you understand the above-the-fold user experience of your real users.

Initial page loads drive the first impressions of new visitors to your web application.

Further, top findings provide an easy way of understanding which web requests impact key performance metrics and are therefore potential candidates for optimization.
For each user action viewed in Waterfall analysis, the following top findings are automatically identified and presented. example:
- Uncompressed text resources
- Resources larger than 100kb
- Resources that have a browser cache rate lower than 50%
- Slow first party, third party, or CDN resources (> 200 ms)
- Contacted third party and CDN domains
- First party, third party, and CDN resources
Dynatrace aggregated waterfall allows you
get a collective view of multiple executions of the same user actions from various real users.

These resources are calculated from the user action executions within the analysis timeframe and are bucketized into 3 summarized itens;

view displaying the slowest 10%, the fastest 10% and +-5% of the median.

This helps you identify requests and patterns that relate to either high or low performance.
Rarely occurring resources
To keep the aggregated Waterfall analysis view down to a reasonable and readable size, that occur in less than 30% of user action instances are moved to a group.

You can expand this group to view.

Note all the detail that's returned in the roll-over highlight pane.
Top segments
This section includes a breakdown of Browsers, Users, and Geolocations and shows metrics for these dimensions for the specific user action
Choose the right performance metric for each application condition
For many traditional web, "User action duration" is considered the best metric available for web-performance optimization, as it focuses on the amount of time from user input to complete page load, example: Visually complete

In case SPAs, based on Angular, Ember, React, and other JavaScript frameworks don't depend on loading a new page following each click.
Visually complete means that all elements within the visible area of a web page are 100% loaded
- Elements
- Images
- IFrames (only images)
Visually complete has the following benefits
- Lets you see exactly how long it takes your end users to see the information they're looking for.

- Provides a true business-relevant metric from the perspective of the user.

- Gives 100% visibility into actual real user experience, regardless of device.

- Aligns IT and business in connecting user experience with business outcomes.

- Accelerates performance improvements.

- Optimizes decisions across development, operations, and user experience.

- Can be combined with powerful waterfall charts for understanding and improving page rendering times.
Speed index calculates
by measuring the progress of the loading of a web page between certain markers, along with the percentage of elements that remain unloaded at a given point in time.
Speed index is only
applicable only for load actions because it uses the whole page as a reference for calculating.
Configuration settings for enhanced Visually complete
- Threshold
- Inactivity timeout for load actions
- Mutation timeout for XHR and custom actions
- Excluded URL list
- Ignored mutation list
Visually complete is calculated when
a apparent element on a page changes and the change is propagated with each subsequent load and XHR user action (but not asynchronous web requests that do not affect the DOM).
Visually complete and Speed index metrics not shown
- Ensure that Visually complete is the key performance metric used for XHR and load actions.

- Confirm support for your browser.

- Safari is not supported because it does not support resource timings.

- Check the JavaScript injection point.
Dynatrace SaaS - Data retention to Services: Distributed trace and code insights
10 days
Dynatrace SaaS and Managed - Data retention to Timeseries metrics (Key user actions and requests)
5 years
Dynatrace SaaS and Managed - Data retention to Davis problems and events
1 year
Dynatrace SaaS and Managed - Data retention to Session replay
Configurable, with maximum 35 days of retention time
Dynatrace OneAgent Diagnostics
Fully automated for troubleshooting for Dynatrace SaaS and Managed environments.
Data retention to Dynatrace OneAgent diagnostics (Support archives and analysis results)
- Dynatrace SaaS: 30 days
- Managed: Configurable, default 30 days
Dynatrace OneAgent Diagnostics workflow
- Automatically pinpoint a related issue in highly dynamic environments, at a specific point in time.

- Easily collect summary the data for a specific entity, and automatically get potential solutions for detected anomalies.

- Directly provide Dynatrace Support all the details they need to diagnose the issue
Contents of Dynatrace OneAgent Diagnostic data
Folders:
:: host, monitored_entities, agent_registration_entries,

JSON files:
archive, monitoring_state

- Include zip file with: process group detection, auto-injection problems, and extension configuration.
Status: Collecting of the Dynatrace OneAgent diagnostic data wasn't possible within 20 minutes
- it automatically tries again.
- If the retry also fails, we suggest that you contact Dynatrace support via chat.
State: Collecting of the Dynatrace OneAgent diagnostic data appears to be frozen
Select Refresh to check.
Dynatrace OneAgent diagnostics uploads the diagnostic data
to the Dynatrace S3 bucket that is configured for the environment/cluster by Dynatrace.
Data retention to Synthetic
Dynatrace SaaS: 35 days
Managed: Configurable with maximum 35 days
Data retention to Services: Requests and request attributes
Dynatrace SaaS: 35 days
Managed: Configurable, with maximum 365 days
Memory dumps
are immediately deleted from the disk once they're uploaded to ActiveGate.

When an upload isn't possible, up to 20 GB are stored on the disk for up to 2 hours.
Real User Monitoring (RUM) data capture
- User actions (default)
- IPs and locations (default)
- URIs (detault)
- User tag of user sessions
- Session and action properties
Service request monitoring data capture
- Client IPs (default)
- URIs (default)
- HTTP request/response headers (default)
- URL query parameters (default)
- Exception messages (default)
- SQL literals (default)
- HTTP post parameters
- SQL bind variables (Dynatrace managed-only)
- Method arguments/return values
Session replay data capture
- all HTML source code and the mutations
- mouse movements and scrolls
- Password form fields (configurable - masked)
- Form fields (configurable - masked)
- Images
- Content
- Attributes
- Interactions
In Dynatrace, masking happens in different stages:
- in capture
- in storage
- in display
Mask at capture
before it is sent to Dynatrace Cluster.
Mask at storage
before it is sent to the disks and, therefore, never displayed as text.
Mask at display
Data is stored as text in the data store. Happens on the server side and is dependent upon the end-user's preferences before being displayed.
Levels of data protection - has different levels of protection in place concerning personal data.
- Scrubbing of content at the point of capture
- Scrubbing of content prior to storage
- Masking of content on display
Scrubbing of data at the point of capture
In this case, the content in question don't leave the monitored process or the end user's browser.
Scrubbing of data prior to storage
In this case the content in question is processed by Dynatrace to allow for better analysis, but the original content is scrubbed prior to storage.
Scrubbed content portions are replaced with the string <masked>.
Masking of data on display
In this case, content is stored but only presented to users who have the View sensitive request content permission.
All other users will see that the content point exists but the personal content is masked out with asterisks (*).
Each Dynatrace OneAgent provides a ruxitagentloganalytics.conf
where you can set configuration options for logs
Custom chart types
- Line
- Stacked area
- Stacked bar
- Pie
- Top list
- Single value
Dynatrace provides different methods for defining maintenance windows
- Console
- Configuration API
The scope of an alerting profile is defined by
- The management zone.
- Severity rules.
- Event filters.
For each alerting profile, you can specify
20 severity rules max.
Root-cause analysis
Dynatrace doesn't depend only on time correlation but follows a context-aware approach to detect interdependent events across time, processes, hosts, services, applications, and both vertical and horizontal topological monitoring perspectives.
To avoid over-alerting and reduce notification noise, the automated anomaly detection modes
don't notify on fluctuating applications and services that haven't run for at least 20% of a full week (7 days).
Alerting on response time degradations and error rate increases
begins once the baseline cube is ready and the application or service has run for at least 20% of a week (7 days).
Dynatrace application traffic anomaly detection is based on the assumption that most business traffic follows predictable
daily and weekly patterns
Alerting on traffic spikes and drops begins after
a learning period of one week because baselining requires a full week's worth to learn daily and weekly patterns.
You can also set up automated tagging of the hosts in your environment using
- Automated rules
- Environment variables
- Smartscape and topology API
Dynatrace OneAgent example command-line parameters for tags
./oneagentctl --set-host-tag TestHost --set-host-tag role=fallback --set-host-tag Gdansk
You'll find the oneagentctl in
opt/dynatrace/oneagent/agent/tools
Synthetic - Set rules for response validation
- Helps you verify that your application loads the expected content by checking if the return contains certain text

- Pass if or Fail if determines the basic test.

- Text contains specifies the text to look for in the response. Texts are case-sensitive.

- Interpret content match as regular expression treats the specified text as a regular expression.
If the pass criteria aren't met (or the fail criteria are met), the monitor will faile and the execution will be aborted.
Synthetic - Follow redirects
By default, up to 10 from an original request until it reaches the final destination.

Turn this option off to monitor only the first response of the migrate chain.
Synthetic - Script timeout
5 minutes
Synthetic - Event timeout
60 seconds
Can I turn on Synthetic on an existing ActiveGate installation?
no, needs exclusively for this proposit
Synthetic - Events
- are all the interactions you record and are therefore simulated during the playback of a browser clickpath.

- are important from a functional perspective but don't generate any performance data.

- with timings, or that trigger actions, are the basis of performance data.
Synthetic - Block specific requests
- Matching the specified patterns will be barricade during the execution of the monitor.
Synthetic - Byte Limit Exceeded The attempt to download the object was blocked because the reported size of the object was greater than the current limit.
The default are 2 MB per page and 10 MB per test
Synthetic - Availability report (view report)Max Time frame period select options
1 y max ou custom
Synthetic - Availability report (view report)Subscription type and timeline selection period
- Weekly
- Monthly
Access environment
- Allows read-only
- Can't change settings or install Dynatrace OneAgent.
Environment permissions
- Access environment.
- Change monitoring settings.
- Download & install OneAgent.
- View logs.
- View sensitive request data.
- Configure capture of sensitive data.
Monitoring admin
- has full environment access.
- Can change settings.
- Can download and install Dynatrace OneAgent.
Deployment admin
- can download and install Dynatrace OneAgent.
- Has read-only access to the environment.
- Can't change settings.
Confidential data admin
can view personal content (for example, method arguments) and configure request-content capture rules.
Monitoring viewer
- can access the environment in read-only mode.
- Can't change settings.
- Can't download or install Dynatrace OneAgent.
Log viewer
- can access and view the contents of files.
- Reserved for users who need access to sensitive file data.
- No other access rights.
Environment Users Group
- Monitoring admin.
- Deployment admin.
- Confidential data admin.
- Monitoring viewer.
- Log viewer.
Default group for users
- Account manager.
- Finance admin.
- Account viewer
Account manager
- has full account access.

- Can view and edit company data, enter credit card data, review invoices, create and edit groups, and add users to groups.

- Also has access to environment consumption data, Help, and Support.
Finance admin
- can enter credit card data and review invoices.

- Has access to environment consumption data, Help, and Support.

- Can't edit groups or assign users to groups. No access to company/billing address info.
Account viewer
- has access to environment consumption data, Help, and Support.

- No access to credit card data, invoices, or company/billing address info.

- Can't edit groups or assign users to groups.
Change monitoring
Change all environment settings.
To install OneAgent, you must provide the Download/install OneAgent permission.
Manage support tickets
Allows access to all that have been created for this environment.
View logs
Allows access to sensitive file data.
View sensitive request data
- Allows viewing of potentially personal data captured by Dynatrace, including downloading memory dumps.

- Users who do not have this permission see that the data point exists but the personal data is masked by asterisks (*****).
Download/install OneAgent
- Allows perform on hosts.

To change/edit settings, you must provide the Change monitoring settings permission.
Configure capture of sensitive data
- Allows configuration of request-attribute capture rules.

- These can be used to capture elements such as HTTP headers or Post parameters for storage, filtering, and search. Also allows manually triggering memory dumps.
Replay session data
Allows reproduce of recorded user sessions with playback masking rules applied at the time.

Note that any data masked during recording is never captured and, therefore, always masked during execution.
Replay session data without masking
- Allows replay of recorded user sessions without playback masking rules applied.

- Note that any data masked during recording is always masked during replay.
Manage security problems
Allows management of problems reported by Dynatrace Application Security.
Access Account
- Allows view environment data (host hours, sessions, synthetic monitors) and Dynatrace Help (documentation) links.

- Allows access Dynatrace ONE (to view and create support tickets) and the Dynatrace Answers user forum.

- There is no access to billing or user/group management.
Edit billing & account info
- Allows access to payment data (credit card details), (invoices), and contact information (company contact data).
Manage users
- Allows access to user administration (add, edit, remove users to groups) and group management (create, edit, delete groups).
Export CSV list of users
Select your account > Identity management > User management and then select Export
SCIM
- Automates the exchange of user identities between different domains and systems.

- You can configure to manage user identities in cloud-based applications and services.
How many SCIM authentication tokens can I generate?
up to 10
Dashboards timeframe - Last 2 hours and below
Refresh interval: 1 minute
Dashboards timeframe - Last 2 hours to last 6 hours
Refresh interval: 5 minutes
Dashboards timeframe - Last 6 hours to last 24 hours
Refresh interval: 15 minutes
Dashboards timeframe - Last 24 hours to last 72 hours
Refresh interval: 30 minutes
Dashboards timeframe - Last 72 hours and below
Refresh interval: 1 hour
Dashboard tile: Custom charts
- Custom
Dashboard tile: text
- Header
- Markdown
Dashboard tile: Infrastructure
- Host health
- Network metrics
- Network status
- Docker
- Vmware
- AWS
Dashboard tile: Services
- health
- request
Dashboard tile: Applications
- Top web applications
- Application health
- User behavior
- User breakdown
- World map
- Key user actions overview
- Bouce rate
- Top conversion goals
- Conversion goal
- Javascript errors
- Resources
- Most used 3rd parties
- Mobile app
- Custom applications
- Live user activity
- Web application
- Key user action
- User sessions query
Dashboard tile: Synthetic
- Browser monitor
- Synthetic monitor health
- Third-party monitor
- Http monitor
Dashboard tile: Databases
- health
- performance
Dashboard tile: Integrations
- Data center services health
Dashboard tile: Analysis
- Problems
- Smartscape
Dashboard tile: Service-level objectives
- Service-level-objective
Dashboard tile: Text
Use this tiles (Header and Markdown) to explain your dashboard contents.
This is particularly important if you're making dashboards to share with others.
Dashboard tile: Header
to put a bold label over another.
Dashboard tile: Markdown
to customize and describe: what it does, how to use it, and so on.
Limitations: 1,000 characters
Dashboard tile: Host health
- Displays the number (operating system instances, whether physical and virtual) in your environment compared to the number in your environment that are currently affected by problems.

- Each instance equates to a Dynatrace OneAgent installed in your environment.
Dashboard tile: Network metrics
- Displays health for traffic flowing through your monitored hosts.

- Shows current traffic volume and quality of communication of both new (Connectivity) and established sessions (Retransmissions).
Dashboard tile: Network status
- Displays current traffic flowing through your monitored hosts.

- Shows traffic volume, number of nodes (Talkers) exchanging traffic, and number of nodes experiencing performance problems (Processes and Hosts).
Dashboard tile: Docker
Displays current number of containers and images compared to last week, plus current number of hosts.
Dashboard tile: VMware
- Displays current basic indicators related to the virtualized infrastructure in your environment, including the number of VMs, migration events, and the corresponding trends, as well as the number of ESXi hosts (standalone or managed by attached vCenter servers) against the number of ESXi hosts in your environment that are currently affected by problems.

- If there are multiple vCenter or ESXi hosts attached, all gathered data can be aggregated or presented for a selected entity.
Dashboard tile: AWS
Displays quick insights and health indicators of three services running under your account:
- Elastic Compute Cloud (EC2) instances
- Elastic Block Storage (EBS)
- Classic Load Balancer (ELB)
Dashboard tile: Service health
Displays the number in your environment against the number of that are currently affected by problems.
Dashboard tile: Service or request
Displays current key performance indicators related to the selected ******* or request (requests per minute, failure rate, and response time) in a resizable tile format.
Dashboard tile: Top web applications
Displays load details related to up to three in your environment that have the highest user-action rate.
Dashboard tile: Application health
Displays the total number in your environment versus the number that are currently affected by problems.
Dashboard tile: User behavior
Displays key indicators related to the selected application (active sessions per minute, actions per session, and session duration) over the timeframe.
Dashboard tile: User breakdown
Displays a type breakdown (doughnut) by real connections, robots, and monitors, and charts new users versus returning over the timeframe.
Dashboard tile: World map
Displays a geographic map of the selected metric for the selected application.
Dashboard tile: Key user action overview
Displays an of the selected application's and any corresponding open problems.
Dashboard tile: Bounce rate
Displays a comparison of the current rate with yesterday and the number of entry actions.
Dashboard tile: Top conversion goals
Display the overall rate and your top 5 objectives for the selected application.
Dashboard tile: Conversion goal
Display the overall conversion rate and your top five objectives for the selected application.
Dashboard tile: JavaScript errors
Displays indicators related to the selected application (errors per minute, percent affected user actions).
Dashboard tile: Resources
Displays load details for application-specific grouped by first-party, third-party, and CDN.
Dashboard tile: Most used 3rd parties
Displays load details related to the three content providers that your application uses most frequently.
Dashboard tile: Mobile app
Displays key performance indicators related (users, crash-free user rate, and number of crashes).
Dashboard tile: Custom application
Displays key performance indicators related to the configuration defined selected (users, crash free user rate and number of crashes).
Dashboard tile: Live user activity
Displays the number of current overall as well as your applications with most online users.
Dashboard tile: Web application
Displays key performance indicators related: Apdex rating, user actions per minute, and number of JavaScript errors per minute.
Dashboard tile: Key user action
Displays performance indicators related to the selected application and action: user action duration, user actions/min, and number of errors/min.
Dashboard tile: User Sessions Query
Create advanced statements on completed connections with USQL.
Dashboard tile: Service level objective
- SLO status: numeric value displayed in green (good), yellow (warning), or red (bad).
- Error budget: numeric value displayed in green (good), yellow (warning), or red (bad).
- Target: numeric value
- Legend (colors) and labels are optional
Dashboard tile: Browser monitor
Displays key performance indicators related (availability, duration and location status).
Dashboard tile: Synthetic monitor health
Displays the number of active in your environment against the number in your environment that are currently affected by problems.
Dashboard tile: Third-party monitor
Displays key performance indicators related (availability, duration and location status).
Dashboard tile: HTTP monitor
Displays key performance indicators related (availability and duration).
Dashboard tile: Database health
Displays the number in your environment against the number of DB that are currently affected by problems.
Dashboard tile: Database performance
Displays key indicators related to the selected DB (commits per hour, statements per minute, and response time).
Dashboard tile: Data center service health
Displays the total number in your environment against the number of data center services that are currently affected by problems.
Dashboard tile: Problems
Displays the number that are currently watched and active against the number of resolved in your environment.
When is active, count is displayed in red.
Dashboard tile: Smartscape
Synthetically visualizes your environment components based on analysis.
The tile display constantly cycles through the five layers: applications, services, OS processes, hosts, and datacenters. For each layer, the tile shows the total number in your environment and, in red, the number currently affected by problems.
Dashboard Weekly subscribers
receive the report every Monday at midnight.
Dashboard Monthly subscribers
receive the report on the first Monday of the month at midnight.
Navigation start
The moment right after the prompt for unload terminates on the previous document in the same browsing context (if there is no previous document, this value is the same as PerformanceTiming.fetchStart)).
Request start
The moment the user agent sends the content to obtain the actual document, from the server, relevant application caches or from local resources (if the transport layer fails after the start of the content and the connection is reopened, this property will be set to the time corresponding to the new content).
Time to first byte
The moment the initial data of a response is received from the server, relevant application caches, or a local resource.
HTML downloaded
The moment the last byte of the current page is received, or before the transport connection is closed (whichever occurs first).
DOM interactive
The moment the parser completes its work on the main document, before a page's readiness status is set to "interactive" (i.e., before a page is ready to receive further user input).
DOM content loaded
The moment the user agent fires the this event at the document.
DOM complete
The moment the user agent sets the current document readiness to "Finished".
Load event start
The moment the is sent for the current document. If has not yet been sent, it returns 0.
Load event end
The moment the current page is completed. If this has not yet been sent, or is not yet completed, it returns 0
User action duration
The moment the page load is completed.
The duration of a user action can be broken down into
Network time: the time required for data transfer
Server time: the time consumed on the server side
Frontend time: the time required for the browser to render the page
Server consumption
responseStart - requestStart
Network consumption
(requestStart - actionStart) + (responseEnd - responseStart)
Frontend time
direct from the W3C navigation timings
Application cache
The time spent checking any relevant application data saved. It includes the time before the connection to the server is established.
DNS lookup
The time spent on the domain name for the current document.
TCP connect
The time spent on establishing the connection to the server including SSL.
Secure connect
The time spent on making the established connection to the server. This includes the SSL handshake and SOCKS.
Request
The time spent on receiving the response.
Processing
The time between DOM loading and Load event start.
OnLoad
The time spent on processing the load event.
OnDOMContentLoaded
The time spent on executing onDomContentLoaded handlers.
Response end
The elapsed time from when the first byte of the server communication is received until either when the last byte of the current document of the communication is received or when the communication completes, whichever happens first.
Redirect time
The time spent on subsequent HTTP requests.
Dynatrace provides extensive Node.js monitoring capabilities:
- Heap and process metrics
- Heap dumps
- CPU sampling (see known limitations)
- Event loop metrics
- Insights into inbound and outbound HTTP calls
- Dedicated support for a variety of databases (includes query capture)
- OneAgent SDK for custom tracing
ActiveGate Extensions - Where can I find plugin logs?
Linux - /var/lib/dynatrace/remotepluginmodule/log/remoteplugin

Windows
%PROGRAMDATA%\Dynatrace\remotepluginmodule\log\remoteplugin on Windows
ActiveGate Extensions - Length of custom property value string
200
ActiveGate Extensions - Maximum number of custom properties reported per host, process group instance, custom device
20
ActiveGate Extensions - Length of custom property key string
100
ActiveGate Extensions - Number of metrics including dimensions per minute, per endpoint
100.000
ActiveGate Extensions - Number of events per minute, per endpoint
100
ActiveGate Extensions - Number of device groups created per minute, per endpoint
500
ActiveGate Extensions - Length of event title string
1024
ActiveGate Extensions - Length of event description string
10.240
ActiveGate Extensions - Number of dimension values per metric
100
What is the ActiveGate extensions license model?
We provide you with a SDK free of charge.

You don't need a special document to develop and deploy your own custom add-on.

Alternatively, you can have one of the Dynatrace partners develop for you, in case fee depends on your contract.

Whichever approach you take, after you successfully deploy and start using, you'll be charged for the custom metrics your reports.
ActiveGate :: Default installation directories
- Distribution directory: /opt/dynatrace/gateway_<id>
- Install/Binaries directory: /opt/dynatrace/gateway
- TEMP directory: /var/tmp/dynatrace/gateway
- ActiveGate configuration: /var/lib/dynatrace/gateway/config
Log files directory: /var/log/dynatrace/gateway
Why use Dynatrace Extensions?
The additional data made accessible means better visibility and an ability to act proactively.

- Also lower your maintenance costs by enabling you to have one platform instead of many.
To create a basic Dynatrace Extension
1 - Export extension assets
2 - Create YAML file
3 - Create ZIP archive
4 - Sign
To add extension to your Dynatrace environment
1 - Upload extension
2 - Enable extension
I have uploaded and configured the ActiveGate Extension but receive a 'Plugin doesn't exist on given host error'.
Dynatrace doesn't propagate automatically.
You need to upload package to Dynatrace Server and to each ActiveGate you want to run it on.

Each one should be placed unpacked in its own folder in ******_deployment directory in the installation directory.
By default, /opt/dynatrace/remote*****module/*****_deployment on Linux or
C:\Program Files\dynatrace\remote*****module\*****_deployment on Windows.
How do I deploy an ActiveGate extension?
You have to upload the add-on.
I have a technology monitored by Dynatrace OneAgent and want to match Custom device group to the same technology tile. How can I do that?
Open the Process Group details, expand Properties section and look for the program in the Main property.

Add this value to programs field in your plugin.json file.
Dynatrace OpenKit available libraries on GitHub
- Java
- NET
- C/C++
- Node.js
The main requirements for using the Dynatrace OneAgent SDK are:
- Access to the source code of the application (and willingness to change the code).
- As the OneAgent *** communicates directly with OneAgent.
- Needs to be installed and running on the host that runs the application. Container environments are supported.
With Dynatrace OneAgent SDK you can:
- Trace incoming and outgoing remote calls
- Trace database requests
- Trace incoming and outgoing web requests
- Trace in-process asynchronous execution
- Trace queues and messages
- Capture request attributes
Dynatrace OneAgent SDK on GitHub
- Language independent documentation APIs and concepts.
- Java
- C/C++
- Node.js
- .NET
- Python
Dynatrace OpenKit Frameworks
- Java 6, 7, 8
- .NET Framework 3.5, 4.0, 4.5, 4.6, 4.7
- .NET Core1.0, 1.1, 2.0.
- NET UWP
- .NET PCL 4.5
- .NET Standard 2.0
- C/C++ Windows Visual Studio 2015/2017
- C/C++ Linux GCC 5.0.0+ or CLang 3.8.0+
- Node.js 12+
- JavaScript ES5+
Dynatrace OneAgent extensions
- ActiveMQ & Apache Solr
- Cassandra, CoreDNS, Couchbase, CouchDB & Elasticsearch
- Hadoop & HAProxy
- Kafka
- Memcached, Microsoft SQL Server, MongoDB & MySQL
- PHP-FPM & PostgreSQL
- RabbitMQ & Redis.
- Spark
- Tibco EMS
- WSO2 API Manager
ActiveGate extensions
- Citrix NetScaler & Citrix Virtual Apps and Desktops
- DataPower
- F5 BIG-IP LTM
- BM iSeries (AS/400) - Preview
- IBM MQ
- Juniper Networks - Preview
- SAP ABAP platform
- Windows Server2003+
Mobile App Real User Monitoring Frameworks
- AFNetworking
- Apache Cordova
- Custom WebViews
- DexGuard
- PhoneGap
- ProGuard
- OkHttp
- Xamarin
- React Native
- Flutter
Real User Monitoring auto-injection technologies by Dynatrace OneAgent
- Apache HTTP Server
- IBM HTTP Server
- Java servlet-based web applications
- Microsoft IIS
- NGINX
- Node.js
- Oracle HTTP Server
Browsers latest's versions compatible for user session recording
- Android Browser
- Google Chrome
- Microsoft Edge
- Internet Explorer
- Mozilla Firefox
- Opera
- Safari
Browsers for user - Session recording
is not supported for IE11 that has been configured with the IE7 compatibility mode.
Dynatrace OneAgent diagnostics benefits
- Automatically pinpoint a related issue in highly dynamic environments, at a specific point in time.

- Easily collect the data for a specific entity, and automatically get potential solutions for detected anomalies.

- Quickly resolve common issues on your own, reducing the amount of time spent on troubleshooting.

- Directly provide Dynatrace Support all the details they need to data the issue
Davis data units - Free tier
- Every new Dynatrace SaaS environment and each Managed license receives 200,000 free of charge.
View DDU consumption details per environment
Settings > Accounting > Davis data units overview
Davis data unit volumes
- are purchased in 1 million units based on 1-3 year contract terms, with the full amount of licensed units renewing at the beginning of each year.
What happens if I change the configuration from Full-Stack to Infrastructure Monitoring mode?
Will the included metrics adapt immediately?
The change should only take a few seconds, with no negative impact on your consumption.
What happens if I send the custom metrics in a higher frequency, like every 10s?
- We recommend that you ingest at a 1-minute interval.

- When more data points are ingested, more DDUs are consumed.
Do Kubernetes metrics (CPU usage/limit/resources) consume DDUs even when Dynatrace OneAgent is not installed?
- Are automatically monitored

- These cadent are part of our core and are included per host unit.
Can I select which services from AWS or Azure are monitored to control my DDU consumption?
- Yes.
- All "supporting technologies" are available
- Also, by leveraging tag filtering, you can opt-out of individual "Core" (those services that are automatically enabled).
What happens if I monitor remote sources using ActiveGate extensions? Will these metrics count against included host-unit metrics?
- Don't consume.
- Are only available for servers and process measured that are monitored by Dynatrace OneAgent.
Before install Dynatrace OneAgent, how i can verify if my hosts SO's and technologies are compatible with dynatrace oneagent?
https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-oneagent/oneagent-technology-support/oneagent-platform-and-capability-support-matrix/
Can I change the retention period for log monitoring?
- There is no longer a way in Dynatrace SaaS, only in managed
What is the DDU weight of one log event?
0.0005
Are there any host-included DDUs available for Log Monitoring?
- No. Dynatrace only offers host-included metrics.
- For this always consumes DDUs, which are deducted from your available quota.
Is the Dynatrace Terraform provider available?
Yes.
https://registry.terraform.io/providers/dynatrace-oss/dynatrace/latest
Timings vary in different analysis types
- PP: PurePath
- RT: Response time.
- SF: Service flow.
- MH: Method hotspots.
The custom.properties file on my Environment ActiveGate doesn't have the [aws_monitoring] property listed in Help.
versions 1.159 and earlier
[collector] AWSAgentEnabled = true
AWS Monitoring - I have more than one ActiveGate.
- Confirm that all that have AWS monitoring enabled can connect to AWS.

- In case of role-based setup: Ensure that all that have AWS monitoring enabled have the role attached.

- Choose one you want to monitor your AWS account with.

- Any type will work as long as it can connect to AWS.

edit the custom.properties file and set the following property to true:

Versions 1.159 and earlier
[collector] AWSAgentEnabled = true

ActiveGate version 1.161 or later
[aws_monitoring] aws_monitoring_enabled = true
On all the other, set the property to false.
My ActiveGate is behind a firewall.
Add *.amazonaws.com to your connection list of allowed domains.
AWS Monitoring - I create and attach the role for ActiveGate, but it doesn't assume the monitoring role
An error might occur when attaching a role to an EC2 instance. In such cases, you can use curl to retrieve the instance metadata to verify if the role is listed there. Use the following command:


curl http://169.254.169.254/latest/meta-data/iam/info
If the attached role is still not listed in the instance metadata, it often helps to reattach it.
Dynatrace module integration
- token for NAM
- token for Dynatrace Appmon
Lock wait - RT
The time during which the code is blocked.
It usually caused by interval time prior to entry into a synchronized code block or by interval time to acquire a spinlock.
Wait time - PP - SF
The set during which the code actively stand by for something (for example, Object.xxxx() or a similar functionality).
- Suspension time - PP - SF - RT
The set during which any code execution is halted.
It is usually caused by garbage collection.
Database requests - by clicking the list box in the top right corner, you can sort database statements by
average execution time, percentage of calls, invocations, and contribution.
While Service flow visualization is helpful for understanding the sequence of
call chains, it doesn't necessarily show the order in which calls were made relative to one another across services.
Referring pages
Shows the HTTP identifiers that contributed to the specific backtrace flow.
Stacktrace
Shows in which part of the code a request was executed.
Practical steps you can take to use Dynatrace to improve the performance of your databases.
- Check the health
- Understand how is accessed
- Understand the load and individual response time of each service instance
- Check the number of connections
- Check your network
Oracle database metrics accessible through Dynatrace
- Performance charts
- Time breakdown charts
- PGA memory charts
- SGA memory charts
- Most time consuming statements
Do I need a plugin to use Oracle database insights?
No, database insights is a default Dynatrace feature starting with version 1.173.
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. Dynatrace maps Availability Zones.

- Or a set of vCenter-based virtual hosts that transmit data to Dynatrace via a single ActiveGate.
You may have multiple vCenter servers or standalone ESXi hosts associated.
Environment topology
A Smartscape visualization of the hosts, processes, services, applications, and data centers.
Monitoring data sent via Dynatrace OpenKit is encapsulated into an entity that represents your application called
a custom application.
With the Dynatrace OneAgent SDK, you can
- Trace incoming and outgoing remote calls
- Trace database requests
- Trace incoming and outgoing web requests
- Trace in-process asynchronous execution
- Trace queues and messages
- Capture request attributes
Dynatrace passwords must meet the following requirements
- Minimum length: 12 characters
- A mix of uppercase and lowercase letters
- At least one number or special character
- There is no enforced expiration.
Environment users
These are who work with Dynatrace to monitor the health of the hosts, services, and infrastructure in their application environments.
Account users
These are who are involved in managing domain details such as company addresses, billing, payment information, and user management.
Does Dynatrace support Just-in-Time and are SAML users added automatically to Dynatrace?
Yes, and federated connections are created or updated on the fly based on attributes following successful authentication.
Are multiple domains and subdomains supported for authentication?
Yes, but you need to perform verification and create a configuration for each separately.
Each configuration can use the same IdP metadata and settings.
How can I rotate SAML certificates?
Can contain more than one, not all of which need to be valid.
This is very useful because the current one is going to expire.
How you can add new employed to access Dynatrace Console?
Accounts > {your account) > Identity management > User Management > Invite User
With oneagentctl you can
- Restart Dynatrace OneAgent
- Change OneAgent communication settings
- Set a new port range
- Enable or disable Log Monitoring
- Change host group assignment
- Custom host name, tags and metadata
- Set a custom ingestion port and network zone
3rd Party integrations - Problem notifications
- Email
- Webhook
- ServiceNow
- Jira
- OpsGenie
- PagerDuty
- VictorOps
- Microsoft Teams
- Slack
- xMatters
3rd Party integrations - Test automation frameworks
- Load testing tools
- LoadRunner
- JMeter
- Neotys
3rd Party integrations - Deployment automation frameworks compatible
Ansible tower
ActiveGate uses embedded modules to run a number of monitoring processes
- API-based cloud and virtualization monitoring
- Oracle database insights
- Extensions
- Synthetic tests from private synthetic locations
- Mainframe monitoring
ActiveGate Extension Plugin Language
Python
Extension SDK
Provides you with all the resources and means necessary to develop your own plugins
ActiveGate extension capabilities and benefits
- Define new technologies
- Understand the health of monitored device groups
- Identify an underperforming group element
- Analyze your group element health
- Resolve problems before your users are impacted
- Enhance Dynatrace root cause analysis
Extension simulator
To facilitate your development, the SDK comes with a tool that can execute an plugin without the need for you to run an ActiveGate, Dynatrace OneAgent, or connect to Dynatrace Server.
Viewing JMX metrics in Dynatrace
Are available for all Java-based processes monitored by Dynatrace OneAgent.
Python Virtual Environment
We recommend that you install the Extensions SDK using this Platform.
Plugin execution time
one minute loops.
Infrastructure metrics - process to host level
every 10 secs
Mobile native user sessions* - data are flushed on a
1-min time interval
Dynatrace monitors database statements via frameworks
ODBC, ODATA, JDBC & ADO
Measurements for ESXi host health
- CPU
- Memory
- Disk (storage I/O)
- NIC (network)
Measurements for ESXi - memory health
- Usage (percentage of total used by processes)
- Compression rate (compression saves, but requires additional CPU cycles).
- Swapping (rate at which is swapped between disk and active)
Measurements for ESXi - Disk health
Throughput (total number of bytes read and written per second)

IOPS (I/O operations per second)
Read/Write latency (time from I/O request submission to I/O request completion.
This is the average delay of read/write operations in milliseconds.)

Command queue latency (the average time spent in Kernel queue per SCSI command)

Aborted commands (the number of aborted SCSI commands. This value serves as the basis for host storage overload incidents.)

Number of datastores (number of datastores connected. Includes metrics for free and used space.)
ESXi - Read/Write latency
time from I/O request submission to I/O request completion.

This is the average delay of disk read/write operations in milliseconds.
ESXi - Command queue latency
the average time spent in Kernel queue per SCSI command
ESXi - Aborted commands
the number of terminate SCSI commands.

This value serves as the basis host storage overload incidents.
ESXi - Number of datastores
Total connected to your vCenter.
Includes metrics for free and used space
ESXi- CPU ready time
Should remain below 10%.
Measurement over 10% indicates that competing for available resources and unable to execute all of its tasks.
The VMware vCenter dashboard tile shows the number of migrations
have occurred during the past 24 hours and allows you to compare this number to the same 24-hour one week earlier.
Docker container - Limitations
- Dynatrace OneAgent only has access to the disks that are mounted within the container that it runs in.

- Deep monitoring for native (i.e., non-containerized) processes on hosts is disabled.

- Because of this, the JMX extension can only work with the processes that run inside.

- Capturing of application crashes and core dumps via oneagentdumpproc isn't supported.

- OneAgent isn't registered in the system's autostart.

- All the command-line parameters of the installer are supported, with the exception of INSTALL_PATH and DATA_STORAGE.
Connectivity issues between Dynatrace and your cluster - There was an error with the TLS handshake
The certificate for the communication is invalid or expired. If you're using a self-signed certificate, check the mitigation procedures for the ActiveGate.
Connectivity issues between Dynatrace and your cluster - There was a communication error when trying to connect to {url}
Check if you entered the correct endpoint address, double-check the port used and make sure the ActiveGate can reach and connect to the endpoint.
Connectivity issues between Dynatrace and your cluster - Invalid bearer token
- The request has been rejected by the Kubernetes API.

- Verify the bearer token. Make sure it doesn't contain any whitespaces.
Connectivity issues between Dynatrace and your cluster - Could not check credentials. Process is started by other user
- There is already a request pending for this integration with an ActiveGate.

- Wait for a couple minutes and check back.
Deploy Dynatrace OneAgent Operator on Kubernetes - Prerequisites
- Generate an API token and a PaaS token in your Dynatrace environment.

- Make sure you have the Access problem and event feed, metrics, and topology setting enabled for the API token.

See Support lifecycle from platform integration.
Deploy Dynatrace OneAgent Operator on Kubernetes
(sample):

$ kubectl create namespace dynatrace

$ kubectl apply -f https://github.com/Dynatrace/dynatrace-oneagent-operator/releases/latest/download/kubernetes.yaml

$ kubectl -n dynatrace logs -f deployment/dynatrace-oneagent-operator

$ kubectl -n dynatrace create secret generic oneagent --from-literal="apiToken=API_TOKEN" --from-literal="paasToken=PAAS_TOKEN"

Save commands above as custom resource file cr.yaml and run

$ kubectl apply -f cr.yaml
if you want to monitor environments that are larger than:

- 50 Kubernetes clusters per Dynatrace environment
- 500 nodes per Kubernetes cluster
- 50,000 pods per Kubernetes cluster
Contact Dynatrace ONE
Integrating your Kubernetes clusters with Dynatrace
(sample):

1 - Create a dedicated namespace:
$ kubectl create namespace dynatrace

2. Create a service account and role
$ kubectl apply -f https://www.dynatrace.com/support/help/codefiles/kubernetes/kubernetes-monitoring-service-account.yaml

3. Get the API URL for later use
$ kubectl config view --minify -o jsonpath='{.clusters[0].cluster.server}'

4. Get the bearer token for later use
$ kubectl get secret $(kubectl get sa dynatrace-monitoring -o jsonpath='{.secrets[0].name}' -n dynatrace) -o jsonpath='{.data.token}' -n dynatrace | base64 --decode

5. Connect to Dynatrace
Settings > Cloud and virtualization > Kubernetes > Connect new cluster

Provide a Name, API URL, and the Bearer token for the Kubernetes cluster.

6. Configure ActiveGate
If your environment uses proxies or self-signed certificates, you need to adapt your ActiveGate configuration.
Deploy ActiveGate in Kubernetes
(sample):

- Create a PaaS token

1 - Create a dedicated namespace
kubectl create namespace dynatrace

2 - Create a secret holding the environment URL and login credentials for this registry.
kubectl create secret docker-registry dynatrace-docker-registry --docker-server=<YOUR_ENVIRONMENT_URL> --docker-username=<YOUR_ENVIRONMENTID> --docker-password=<YOUR_PAAS_TOKEN> -n dynatrace

3 - Create a file named ag.yaml (download from https://www.dynatrace.com/support/help/technology-support/cloud-platforms/kubernetes/monitoring/deploy-activegate-in-kubernetes/) with the following content, making sure to replace
<YOUR_ENVIRONMENT_URL> and <YOUR_ENVIRONMENTID>with your own values as described above
<ANY_UNIQUE_ID> with any unique value. This ID will be used by the ActiveGate to generate a unique name in the UI.

4 - Deploy ActiveGate
kubectl apply -f ag.yaml

5 - Set up Kubernetes integration
Kubernetes page - metrics
- Actual CPU/Memory usage of cluster nodes (Min, Max, Median).

- Total of CPU/Memory requests of containers running on cluster nodes (Min, Max, Median).

- Total of CPU/Memory limits of containers running on cluster nodes (Min, Max, Median)—limits might be overcommitted, ie. over 100 %.

- Available CPU/Memory resources for running additional pods/workloads on cluster nodes (Min, Max, Median).

- Total CPU that can be allocated for pods (since a part of CPU is typically reserved by the system).

- Max Memory that can be allocated for pods.
Kubernetes workloads with the cloud application view - The cloud applications view covers workloads like:
Deployment, DeploymentConfig, ReplicaSet, DaemonSet, StatefulSet, StaticPod, and ReplicationController
Your customer wants an excel report file with daily synthetic consumption, how do you proceed?
Account > {CUSTOMER_TENANT} > License details > View Consumption > DEM units > Export chart data
In license details > view consumption > Export chart data, what content is placed in excel report file?
- Start and end date.
- Max Host Units, Max Full Stack Host Units, Max Cloud Infrastructure Host Units, Max Cloud Container Host Units, Host Unit Hours.

- DEM Units, Sessions (DEM units), Synthetic actions (DEM units), Sessions with replay data (DEM units), Mobile sessions (DEM units).

- Davis data units, Metrics (Davis data units), Logs (Davis data units), Events (Davis data units), Serverless functions (Davis data units) & Log Analytics.
Kubernetes deployment strategies
- DaemonSet
- Operator
- Helm Chart
Davis Assistant integration
- Amazon Alexa
- Google Assistant
- Microsoft Teams
- Slack
- Custom
What data captured by Dynatrace is stored in Davis Assistant?
- Caches a minimal amount of data from the REST API for a short period of time (about 10 minutes or less) to reduce the number of API calls made to your Dynatrace environment and thereby improve response times.

- Closed problems are cached for 30 days. Open problems aren't cached.

- Application, service, host, and process-group data is cached for 10 minutes.

- Other data accessed through the Dynatrace API is cached for less than a minute.
Where is Davis Assistant hosted?
In Amazon Web Services in the US East (N. Virginia) region.
What Dynatrace data can Davis Assistant access?
- Any from the API that the configured API token has permission to access.

- This may include details of problems, time series data such as response times, environment Smartscape topology information, events collected by Dynatrace, and some configurations, including custom event thresholds and maintenance windows.
Davis Assistant data security
TLS with a 2048-bit RSA certificate issued by Amazon.
Davis Assistant Web
https://assistant.dynatrace.com
Generate a token
Settings > Integration > Dynatrace API
Token permissions
- Access problems and event feed, metrics, and topology, ActiveGate certificate management, Anonymize user sessions for data privacy reasons, AppMon integration for hybrid deployments

- Capture request data, Change data privacy settings, Create and read synthetic monitors, locations, and nodes, Create support alerts

- Davis Assistant integration, Download OneAgent and ActiveGate installers, Dynatrace NAM integration.

- Import data and events from external sources, Log import, Mobile symbolication file management.

- Read audit logs, Read configuration, Read log content, Read synthetic monitors, locations, and nodes, Real User Monitoring JavaScript tag management, REST request forwarding.

- User sessions, Write configuration, Upload plugins using the command line, Read entities using API V2, Write entities using API V2, Read network zones using API V2, Write network zones using API V2.

- Read Credential Vault entries, Write Credential Vault entries, Read metrics, Ingest metrics, Read ActiveGates, Write ActiveGates.

- Read synthetic locations, Write synthetic locations, Read problems, Write problems
Token settings
- Create API in new format
- Enable personal access
Dynatrace API - DataExport
Grants access to various calls of Environment.
Dynatrace API - ActiveGateCertManagement
Allows to configure certificate on private ActiveGates.
Dynatrace API - UserSessionAnonymization
Grants access to Anonymization
Dynatrace API - AppMonIntegration
Allows to import monitoring data for previous dynatrace versions.
Dynatrace API - CaptureRequestData
Grants access to Request attributes.
Dynatrace API - DataPrivacy
Grants access to Data privacy and data privacy calls of Web application configuration.
Dynatrace API - ExternalSyntheticIntegration
Grants access to the Synthetic.
Dynatrace API - SupportAlert
Allows creation of support alerts for crash analysis.
Part of PaaS token.
Dynatrace API - Davis
Davis
Dynatrace API - InstallerDownload
Allows to download installers via Deployment.
Dynatrace API- DcrumIntegration
Integration with NAM.
Dynatrace API - DataImport
Allows to import data and events from external sources.
Dynatrace API - LogImport
Allows to push data stream for storing without using Dynatrace OneAgent.
Dynatrace API - DssFileManagement
Grants access to Mobile Symbolication.
Dynatrace API - auditLogs.read
Grants access to the audit log.
Dynatrace API - ReadConfig
Grants access to GET calls of Configuration.
Dynatrace API - LogExport
Grants access to Log Monitoring.
Dynatrace API - ReadSyntheticData
Grants access to GET requests of Synthetic.
Dynatrace API - RumJavaScriptTagManagement
Grants access to Real User Monitoring JavaScript code.
Dynatrace API - RestRequestForwarding
Allows to fetch data from remote Dynatrace environments for multi-environment dashboarding.
Dynatrace API - TenantTokenManagement
Allows to create and delete as well as view their metadata.
Dynatrace API - DTAQLAccess
Grants access to User sessions.
Dynatrace API - WriteConfig
Grants access to POST, PUT, and DELETE calls of Configuration.
Dynatrace API - PluginUpload
Allows to upload Dynatrace OneAgent extensions via command line tool.
Dynatrace API - entities.read
Grants access to GET requests of the Monitored entities and Custom tags.
Dynatrace API - entities.write
Grants access to POST, PUT, and DELETE requests of the Monitored entities and Custom tags.
Dynatrace API - networkZones.read
Grants access to GET requests of the Network zones.
Dynatrace API - networkZones.write
Grants access to POST, PUT, and DELETE requests of the Network zones.
Dynatrace API - credentialVault.read
Grants access to GET requests of the Credential vault.
Dynatrace API - credentialVault.write
Grants access to POST, PUT, and DELETE requests of the Credential vault.
Dynatrace API - metrics.read
Grants access to GET requests of the Metrics v2.
Dynatrace API - metrics.ingest
Grants access to the POST ingest data points request of the Metrics v2.
Dynatrace API - activeGates.read
Grants access to GET requests of the ActiveGates.
Dynatrace API - activeGates.write
Grants access to POST and DELETE requests of the ActiveGates.
Dynatrace API - syntheticLocations.read
Grants access to GET requests of the Synthetic nodes v2.
Dynatrace API - syntheticLocations.write
Grants access to POST, PUT, and DELETE requests of the Synthetic nodes v2.
Dynatrace API - problems.read
Grants access to GET requests of the Problems v2.
Dynatrace API - problems.write
Grants access to POST, PUT, and DELETE requests of the Problems v2.
Dynatrace API - slo.read
Grants access to GET requests of the Service level objectives API.
Dynatrace API - slo.write
Grants access to POST, PUT, and DELETE requests of the Service level objectives API.
Personal access token
you can generate for API usage without admin rights. Available scopes are bound to your permissions, that is, you can only use the API counterparts of features you're already authorized to use.
Dynatrace tokens types
- API and personal access grant access to the Dynatrace API.
- PaaS allow download of OneAgent and ActiveGate installers.
- Tenant allow OneAgent to report data to Dynatrace.
- Module grant access to module integrations.
Dynatrace OneAgent - the minimum required space usage is
200 MB * 3 = 600 MB (logs, alerts, crash reports).
Dynatrace OneAgent - The default required space is
1 GB * 3 = 3 GB (logs, alerts, crash reports).
Dynatrace OneAgent - Log Files - cleanup process
that runs every minute keeps the size within reasonable constraints.
Dynatrace OneAgent - Emergency cleanup log files
when free disk space reaches the low disk threshold (3% by default, configurable through anomaly detection settings), delete all the data from directories managed by the aging mechanism except the latest installer data and OS module.
Dynatrace OneAgent aging mechanism rules
ensures that the disk space used is constantly within predefined limits.
Dynatrace OneAgent - The file aging mechanism checks data and subdirectories in the main log directory and removes the oldest data when:
- The total size is above 1 GB.
- Any is older than 14 days.
- Contains more than 1000 (newest are preserved)
Dynatrace OneAgent aging mechanism - file removal rules for {log-dir}/process
- use more than 300 MB in total
- is older than 14 days
- more than 1000 files.
Dynatrace OneAgent aging mechanism - file removal rules for {log-dir}/installer
- use more than 30 MB in total
- any is older than 180 days
- more than 1000 in directory (newest are preserved; oldest are removed)
Dynatrace OneAgent aging mechanism - file removal rules for {log-dir}/dumpproc
- more than 100 MB in total
- is older than 14 days
- more than 1000 in directory (newest are preserved; oldest are removed)
Dynatrace OneAgent aging mechanism - file removal rules for {data_storage_dir}/supportalerts
- more than 10 files
- use more than 1 GB in total
- any is older than 7 days
Dynatrace OneAgent aging mechanism - file removal rules for {data_storage_dir}/memorydump
- is older than 2 hours
- use more than 20 GB in total
Dynatrace OneAgent aging mechanism - file removal rules for data_storage_dir}/crashreports
- They have already been reported to Dynatrace
- contains more than 100
- use more than 1 GB in total
- directory is older than 3 days
Aging mechanism for Dynatrace OneAgent in application-only monitoring mode - Log rotation
- Each module limits its number to 5
- Each of one is limited to 10 MB.
Log aging - Dynatrace OneAgent purges the log files at startup when:
- is older than 14 days
- The combined size of all exceeds 300 MB
- more than 1,000
To prevent unnecessary delays in your application's startup, the Dynatrace OneAgent bulk purge limit is set to delete a maximum of
50 of the oldest files.
Settings > Server-side service monitoring > Deep Monitoring > Troubleshooting > Capturing off
- Has immediate effect and turns the specific feature.

- Doesn't require a process restart. However, upon startup/restart of a process, the respective feature will still added to your application.

- Even while the feature is inactive, it can still have an impact on startup.

- The upside is that you can re-enable the feature without restarting any processes.
Settings > Server-side service monitoring > Deep Monitoring > Troubleshooting > Instrumentation off
- This setting has the same immediate effect as Capturing function.

- However, upon restart/startup of a process, the feature won't be added to your application.

- This means that the feature will have no impact on your application.

- The downside is that, if you re-enable the feature later, you'll need to restart the affected processes.
Settings > Server-side service monitoring > Deep Monitoring > Real-time updates to Java and PHP services
- Enable this setting to have changes to your custom services and request attributes applied in real-time with no restart required.

- While convenient, CPU spikes may occur when changes are deployed.

- With this disabled, affected processes must be restarted before changes are applied.
OpenTelemetry and OpenTracing
- Automatically tap into span data and benefit of full end-to-end view of transactions in hybrid deployments where not all services provide data.

- Dynatrace OneAgent enriches span data with code-level details and brings data to Davis, for analytics and root cause determination.
Troubleshooting deep monitoring
- Enable you to disable certain functionality at a fine-grained level to facilitate issue resolution.

- This can be useful for identifying the root cause of a problem, all the way down to a specific feature.

- These settings also enable you to disable certain features that may be leading to problems while still retaining all other functionality while the Dynatrace Support team works on a permanent fix.
In situation is detected whenever a single Dynatrace SaaS environment loses the connection to its Dynatrace OneAgents.
As no other environments are affected on the same Dynatrace SaaS cluster, it's highly recommended that you check the following issues within your own network configuration
- Verify whether a recent change in your environment or firewall configuration blocks the outgoing communications.

- In case you are routing traffic through an ActiveGate, check the operational status of your ActiveGates.

- Finally, in case you don't find any issues within your own datacenter, verify dynatrace.status.io for a general issue in your region.
Monitoring interruption within a Dynatrace cluster
An alert is sent out to all affected environments.
Alert example for a interruption on a Dynatrace SaaS region.
Monitoring unavailable
When Dynatrace detects that a certain process is the root cause of a detected problem, an
Analyze process logs link is displayed on the corresponding Problem page.
Stored logs have a defined data transfer quota. You start with a total of
5 GB per year of data transfer for all your monitored files.
The stored logs quota is
5GB*30/365 days which gives approximately 500MB (0.5GB) of yearly.
Important characteristics of using log monitoring for troubleshooting
- Process and operating system are auto-discovered.
- You can examine a maximum of 500 MB data.
- You can examine the files for only the past seven days.
- You can examine files one at a time in the context of your topology.
Important characteristics of monitoring logs and storing log files on Dynatrace server:
- For Dynatrace Managed, the initial quota is a total of 5 GB per year of data transfer.
- For Dynatrace SaaS, the initial quota is 500MB (0.5GB) of yearly.
- You can retain data for as little as 5 days and up to 90 days.
- You can create alerts based on text pattern occurrences.
- You can bookmark search queries.
- You can parse columns and examine the top N occurrences.
- You have access to the application programming interface (API)
By default, log files are auto-discovered and analyzed if they are in:
- Windows System
- Windows Security
- Windows Application
/var/**/sys**
/var/***/messages
A log file must meet all of the following requirements in order to be auto-discovered:
- Must be opened by an important process.
- Must exist for a minimum of one minute.
- Must contain a supported time stamp.
- Must be at least 0.5 kb in size.
- Must have been updated (written to) in the last 7 days.
Binary log and unsupported time stamp
- Will be detected automatically but will not be analyzed and will not be stored (only the file status will be reported).
The log file must be in the actual log or logs folder or in it's sub folders (valid path sample):
- c:\**\*_file.txtc:\**\NewFolder\**_file.txt
The log file must be in the actual log or logs folder or in it's sub folders (invalid path sample):
- c:\**\NewFolder\NewFolder\**_file.txt
If you don't want Dynatrace to automatically discover new log files on a specific monitored host, set:
AppLogAutoDetection = false
What might prevent logs to appear on the server?
- Detected over 200 rotated files groups for a process.
- Fast growing files are skipped.
- File name or path doesn't match typical naming.
- There are symbolic links in the file or the paths.
- File size is below 500 bytes.
Additional limitations for automatically detected log files:
- File cannot be deleted earlier than a minute after creation.
- Files must be appended (old content is not uploaded).
- Files must have text content.
- Files must be opened constantly (not just for short periods of adding entry).
- Files must be opened in write mode.
Once 200 reported rotated log file groups is reached
auto detection is turned off for this process.
Fast growing logs files are skipped.
- In a scenario where a file expand very quickly (at a pace over 10 MB/s), it's content not be monitored.

- The Dynatrace OneAgent will continue to send the file as long as both, the network and the server, can handle such load.

- Note that 10 MB/s with typical compression is approximately 10 Mbps of upload traffic.
File name or path log doesn't match typical log naming.
- The agent checks if files match correct pattern that is typical for files.

- If there is no match, the file will not be reported and sent to the server.

- This is needed to avoid false positives on detection of files, and to prevent pulling non-log data from hosts.

- To remedy this you can set rules in the agent configuration, AutomaticFile property (Monitoring configuration file).
There are symbolic links in the log or the paths
- This limitation applies to custom files in which the user points to a path that contains unstructured pattern.

- The physical way of the file pointed link must meet criteria for a file.

- Otherwise, could be used to read non-log data from host.
ruxitagentloganalytics.conf - AppLogContentAccess
- Enables access to file content on this host.
- If set to false, the file will be displayed in the user interface, but the content won't be accessible.
- Note that the Dynatrace OneAgent will still auto-detect log files unless the flag AppLogAutoDetection is set to false.
ruxitagentloganalytics.conf - AppLogRemoteConfiguration
- Enables the manual setting of data to be accessed and monitored.

- If set to false, it won't be possible to add files manually using the settings interface.
ruxitagentloganalytics.conf - AppLogAutoDetection
- Enables auto-detection of files on this host.
- If set to false, files won't be auto-detected.
ruxitagentloganalytics.conf - FilesInGroup
- Defines how many files can be open by the specified process group.Syntax:
FilesInGroup=[process_group_ID], [warning_number_of_files], [maximum_number_of_files]
ruxitagentloganalytics.conf- EntryFilter
- Defines the filter for a file entry.
- A matching definition for process group, file path, and line prefix will make this entry available on storage.Syntax: EntryFilter=[process_group_ID], [log_path], [LAQL]
ruxitagentloganalytics.conf - LogEntryPrefix
- Defines the prefix of the fileentry.
- If a match is found, the file line will be considered a log entry.
ruxitagentloganalytics.conf - MainLoopInterval
- Sets the time interval (in seconds) of Dynatrace OneAgent file operations.
- Defines how often the OneAgent will detect, analyze, and store files.
ruxitagentloganalytics.conf - AutomaticFile
- Defines which files will be included in or excluded from the analysis and storage.
- AutomaticFile=Path, Include|Exclude
ruxitagentloganalytics.conf - JSONTimestampFieldNames
- Defines a list of fields in a JSON-formatted log entry that will be used as a time stamp for automatic JSON parsing.
- This is a global configuration for all JSON log files.
- If more than one field is found, the first one will be used.
Mask sensitive information in logs
- Features the ability to don`t show any confidencial information by modifying the configuration file on each of the Dynatrace OneAgents
Examples of valid log file date formats
- 2018 04 06
- 2018/04/06
- 2018-04-06
- 2018.04.06
- 2018-04-06T18:46:19Z
Examples of valid log file time formats
12:23:34.123
12:23:34.123GMT+0100
12:23:34.123 GMT+0100
0:00:00 GMT
0:00:00 GMT+0100
00:00:00
12:13:01+0100
12:13:02.123
12:13:03.123123+0100
12:13:02,123
12:13:03,123123+0100
12:13:04GMT
12:13:05GMT+0100
12:13:06GMT+01
12:13:09+0100
12:13:10+01
12:13:12+0200
12:13:13.123pm
12:13:14.123 AM
12:13:15.123PM+01
12:13:16.123 AM+02
12:13:17CEST
12:13:18 CET
00:13:19
Examples of valid log file time stamps
2018-04-06 09:54:04.839 UTC
2018-04-06 11:01:19,625
2018/04/06 11:06:23 UTC
Apr 6 12:23:52
Apr-6 13:35:57.621
The time stamp date log can be separated using either of the following:
(space)
/ (slash)
- (dash).
(period)
T (Combined date and time in UTC, ISO 8601 format)
,(comma)
@ (ampersand)
Log Monitoring enables you to store all logs centrally within external storage. This makes log data available independent of log files themselves. This can be beneficial in the following situations:
- Short log retention periods
- Volatile file center
- Legal requirements for keeping files archived centrally for long time periods.
- Analyze multiple files simultaneously
- Parse JSON files.
- Generate metrics from file content
Dynatrace SaaS - Log storage requirements and costs
Are based on the average size of your cloud-based storage, including the amount of streamed file data and the defined retention period.
Dynatrace Managed - Log storage requirements and costs
- You must provide a common Network File System (NFS) mount point (path) that is identical throughout the cluster and available from all cluster nodes.

- Are calculated based only on the amount of ingress file data (GB/day), not total storage size, so retention time doesn't influence storage values.
HTTP monitor metrics
- Response time
- DNS lookup time
- TCP connect time
- TLS handshake time
- Waiting
- Download
HTTP monitor metrics - Response time
- Measures the event performance.
- Is the sum of DNS lookup time, TCP connect time, TLS handshake time, Waiting, and Download.
HTTP monitor metrics - Waiting
- Amount of time taken for the server to respond with the first byte—This is the Time to first byte minus (DNS lookup time + TCP connect time + TLS handshake time).
Pre- and post-execution scripts for HTTP monitors code
custom JavaScript
There are three main problem types for browser monitors or HTTP monitors:
- Global outage
- Local outage
- Performance threshold violation
Global outage occurs
when all locations experience a failure simultaneously.
A local outage occurs