Licensing details

Configuring a proxy server to connect to eServices

If you cannot connect to eServices from the Client, you may need to configure a proxy server.

  1. From the Client, choose Settings > Dynatrace Client.
  2. Click Services in the left pane of the Client Preferences dialog box.
  3. Under Proxy for access to external services, select Manually configure proxy and enter the host, port, and authentication method.

Firewall and network configuration

See here for enabling network access to eServices for online licensing.

Licensing models for supported technologies

This section outlines how Agents are licensed for different technologies and how the allowance per Agent type and UEM visits volume per AppMon Server is enforced by the Server.

For finer legal details, actual pricing of Agents, bundles and packs, and information currency, the price book precedes this documentation. For information on other details such as what AppMon edition and version is licensed, the type of license, and the validity time frame, see the Licensing page, the Client Settings menu > Dynatrace Server > License vertical tab, eServices or talk with sales.

There is a three day licensing grace period and you can generate an emergency license in eServices.

See System requirements and the Deployment Guide for technical limit details.

Most technologies are licensed on Agent-per-process bases, with a certain number of each Agent type licensed per AppMon Server.

Restrictions such as the maximum number of cores a DB Agent is licensed for may apply, and there are notable exceptions like UEM (visits-based), DB (per DBMS instance) and mainframe CICS and IMS (region-based).

Technology License Comment
Java Per Java Virtual Machine (JVM) Each JVM with an injected Agent consumes one Java license on the AppMon Server.
.NET Per Windows operating system instance (WOSI) Even when more than one .NET Agent runs on a WOSI, only one .NET license is consumed.
Web Server Per Agent in Apache, IIS, NGINX or IBM HTTP server No license is necessary for Web Server (master) Agent services / daemons, but this is also the reason that slave / core Agents deliver host monitoring data.
PHP Per (parent) process ID (PID) Considered as children: module worker processes and threads, CGI and FastCGI If PHP-FPM (FastCGI Process Manager) is used and configured as one pool of FPM workers and another virtual host and pool (parent 2), then two licenses are used.
Node.js Per process Node.js spawns one process per CPU core to handle requests.
UEM Consumes a UEM visit See Manage UEM Visits Volume for a discussion of UEM visits-based licensing and which visits reduce the licensed visits volume.
Mobile / Android and iOS Consumes UEM visits The Agent generates events which become part of a visit, all licensed based on UEM visits. No other Agent license is required.
Native (ADK) Per process Each instance of a C++ program requires a license.
No further license is required for a native part, if an app already has a license.
Rich / fat clients Per instrumented client Rich / fat clients based on Java, .NET or native require licenses for the respective technology, but pricing is different and technical limits apply.
Database Per DBMS instance Oracle: A license is consumed for each DB instance with a maximum of eight CPU cores per license. Every other instance or eight cores consume another license. CPU count is retrieved as the cpu_count value of v$parameter.
SQL Server: A license is consumed for each DB instance with a maximum of eight CPU cores per license. Every other instance or eight cores consume another license. CPU count is retrieved as the cpu_count value of sys.dm_os_ss_info.
MySQL: A single license is consumed for each DB agent - no limitation on the number of CPU cores.
DB2: A license is consumed for each DB agent, with a maximum of eight CPU cores per license. Every other agent or eight cores consume another license. CPU count is retrieved as the CPU_ONLINE value of SYSIBMADM.ENV_SYS_RESOURCES of current partition.
See Database Agent Troubleshooting for more details on how the CPU cores are retrieved from the Database.
Infrastructure / Host Monitoring Per host (Agent) Hosts explicitly instrumented with a Host Monitoring Agent consume such a license.
Java, .NET, Web Server, PHP and native (ADK) Agents deliver monitoring data and need no additional license.
IBM WebSphere Message Broker (WMB) / IBM Integration Bus (IIB) Per process / execution group  
Mainframe / z/OS CICS and IMS Per region (CICS / IMS)
Per JVM if Java is instrumented on z/OS
Each CICS or IMS region with an injected Agent consumes one z/OS license.

If a JVM is instrumented on z/OS it consumes a Java license.
No zLocal or zRemote Agent is necessary for Java.
NoSQL Per (Agent in) Java Virtual Machine (JVM) Special NoSQL Agents are consumed first for Cassandra JVMs.
More expensive Java Agents can optionally jump in.

As of 2017 May, HBase instrumentation has been discontinued.
Hadoop   As of 2017 May, instrumentation has been discontinued.
Browser Per browser instance
Only maintenance licenses are issued.
Browser Agents are end of life. They can be used if compatible with the browser version in question.

Merging and splitting licenses

You can merge multiple licenses into a single license to increase the number of Agents allocated for the single license. Conversely, you can split a single license into multiple licenses and redistribute the number of allocated Agents across the multiple licenses. In either case, you must contact the license management beforehand. The Licensing Team then instructs you to deactivate the original license or licenses, and then perform a standard license activation.