Dynatrace automatically detects application types such as Tomcat, JBoss, Apache HTTP Server, MongoDB, and many others technologies. To create process groups, Dynatrace uses specific process properties. For Tomcat, Dynatrace uses CATALINA_HOME and CATALINA_BASE to distinguish between different Tomcat clusters. For JBoss, Dynatrace uses JBOSS_HOME and the JBoss cluster configuration. For generic Java processes, Dynatrace uses the JAR file or the main class used to start the process. There are also many specialized detection mechanisms. For example, Dynatrace can detect:
- IBM WebSphere clusters and domains
- Oracle WebLogic clusters and domains
- Cassandra clusters
- Tibco BusinessWorks engines
- Kubernetes apps
- OpenShift apps
- Cloud Foundry apps
- Azure Web Apps
- And more…
On each process overview page you'll find the properties if you expand Properties and tags.
What does this mean for services?
Process groups are the basis for service detection, because each process group is considered to be a logical cluster or single deployment. When Dynatrace detects the "same" service in separate process groups, it treats them as separate services (for example, one process might be used in staging and the other in production).
If you instruct Dynatrace to merge two separate process groups into a single process group, this will result in the services running on those processes to also be merged.
Customize process groups
To serve your particular needs when monitoring your processes, Dynatrace allows you to: