This project contains files for building and running the Dynatrace Server component of the Dynatrace Application Monitoring enterprise solution for deep end-to-end application monitoring in Docker. Ready-made images are available on the Docker Hub.
![]()
Note: the
dynatrace/server image has been designed to run in low-traffic, resource-constrained demo and trial environments. Dynatrace does not support its use in production or pre-production grade environments of any kind.
How to install Dynatrace AppMon Server?
By default, we use root user for running containers. It is a bad practice so, if you can, you should run them as non-root. Go to the
Running Dynatrace Appmon Server as non-root paragraph for running and configuration instructions.
Running Dynatrace Appmon Server as root
If you don't need to use a non-root or dedicated user to run Dynatrace Appmon Server, you can quickly bring up an entire Dockerized Dynatrace AppMon environment by using Docker Compose with the provided
docker-compose.yml file like so :
To integrate with Dynatrace, you can use the Dynatrace client to install and configure the Moogsoft alert plugin on your Dynatrace server. Then you set up an incident rule in Dynatrace to forward incidents to the Moogsoft alert plugin. Content of downloads/OnPrem/dynaTrace/7.2/7.2.0.1697. Dtagentconf.exe; dtagentconf.exe.config; dynaTrace-7.2.0.1697.zip; dynatrace-adk-7.2.0.1697-cross.jar.
In order to browse logs produced by the service you can use:
Running Dynatrace Appmon Server as non-root
For the security reasons, as Docker co-uses the host kernel, all Dynatrace Appmon services are recommended to be run as non-root user. Therefore, you should operate on dedicated user on your host machine and set
CUID (User ID) and CGID (Group ID) variables in .env file for your user. By default it uses root. During image builds, user with the same ids will be created and used for running containers.
After you change user/group id variables, you may run Dynatrace Appmon Server in two ways:
or
Configuration
Configuration relies on supplying docker-compose with environment variables defined in .env file. Some variables need to be passed to Dockerfile via ARG for correct building an Server image, that's way it is recommended to change variables only in .env file.
Ports are also defined in .env file based on current Communication Connections
List of used ports for server:
Licensing
The examples above leave your Dynatrace environment without a proper license. However, you can conveniently have a license provisioned at container runtime by specifying a URL to a Dynatrace License Key File in the
DT_SERVER_LICENSE_KEY_FILE_URL environment variable. If you don't happen to have a web server available to serve the license file to you, Netcat can conveniently serve it from your command line, exactly once, via nc -l 1337 < dtlicense.key , where 1337 is an available port on your local machine. A sudo may be required depending on which port you eventually decide to choose.
Dockerized Dynatrace ComponentsDynatrace Client Download
See the following Dockerized Dynatrace components and examples for more information:
Dynatrace Free DownloadProblems? Questions? Suggestions?
This offering is Dynatrace Community Supported. Feel free to share any problems, questions and suggestions with your peers on the Dynatrace Community's Application Monitoring & UEM Forum.
Dynatrace Client 7.1LicenseDownload Dynatrace Client 6.3
Licensed under the MIT License. See the LICENSE file for details.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |