Service detection and naming
Dynatrace automatically detects and names your applications' server-side services based on specific properties of your application deployment and configuration.
- To improve out-of-the-box detection, see how to set service detection rules
- To enhance service detection across your environment, you can configure improvements
- If the default naming scheme doesn't suit your needs, you can customize the naming of your services
As service landscapes can become quite complex, Dynatrace automatically categorizes services based on their dependencies to other entities like services or applications. To learn more on Dynatrace service types, refer to Service types.
Relationships with process groups
Dynatrace automatically groups related processes into process groups. When Dynatrace detects multiple process groups, it assumes that the process groups represent separate applications, or at least separate logical parts of a single application. Process groups therefore represent boundaries for the services they contain.
When Dynatrace detects the same service in multiple processes within the same process group, it represents the service as a single service running on multiple processes or hosts. Conversely, if Dynatrace detects a seemingly identical service in multiple process groups, it represents the separate service instances as separate services, even though the services appear to be the same. For this reason it sometimes makes sense to customize how Dynatrace detects process groups.