Web applications consist of web pages that are served by web servers and web containers, for example Tomcat. The web requests that are sent to a specific Tomcat server are an example of a server-side service. Web and mobile applications are built upon services that process requests like web requests, web service calls, and messaging. Such "server-side services" can take the form of web services, web containers, database requests, custom services, and more. Services may in turn call other services such as web services, remote services, and databases services.
Processes are essentially containers that host services. When you look at processes you see topology information, whereas services give you code-level insight. For example, you might have a Tomcat process that hosts a web application in the form of a server-side service. While processes are host-centric—associated with a single machine in your environment—services are request-centric and therefore typically span across multiple machines in a data center.
Click the Services tile to view all the services in your environment that are monitored by Dynatrace
To learn about the metrics and insights that Dynatrace offers for the monitoring of server-side services, see What's included on each service page?
Dynatrace automatically detects and names your applications' server-side services based on basic properties of your application deployment and configuration. For details, see How does Dynatrace detect and name services?