You can modify service settings both globally—across all services—or for individual services.
How to define service settings globally
Go to Settings > Server-side service monitoring to find settings for capturing web requests, database calls, and custom services. These settings define rules that apply to all services detected in your system.
With global service settings you can:
Define entry points (a method, class, or interface) for custom services that don't use standard protocols (in Custom service detection).
Create merged services in order to logically group separately detected services into the same service (in Merged service monitoring).
Customize and enhance the default names of your services (in Service naming rules).
Create advanced filters based on request attributes (in Request attributes).
How to define individual service settings
Go the overview page of a service, by clicking Transactions and services and selecting the service you want to configure. On the services' overview page, click the Browse button (...) and select Edit.
With individual service settings you can:
Edit the default display names of services and add descriptions to improve tracking (in Naming and Web request naming).
Fine tune HTTP error detection rules (in Error detection). You can specify custom HTTP error codes that your application can use to signal failed service calls. Dynatrace marks all service calls that respond with these HTTP error codes—or that are exited via code level exceptions—as failed.
You can also configure how sensitive Dynatrace should be to 404 HTTP errors (broken links). When some service calls in your application are exited via exceptions and are still successful you can make them invisible to Dynatrace. You can define exception classes or patterns that don’t indicate failed service calls.
Switch off unwanted alerts about response time degradations, failure rate increases or changes in load behavior (in Anomaly detection).