Service monitoring settings
You can modify service settings both globally—across all services—or for individual services.
Define service settings globally
Go to Settings > Server-side service monitoring to find the available settings for detecting and naming web requests, database calls, and custom services. These settings define rules that apply to all services detected in your system.
With global service-monitoring settings you can:
- Define entry points (a method, class, or interface) for custom services that don't use standard protocols (see 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 detected services (in Service naming rules).
- Create advanced filters based on request attributes (in Request attributes).
Define individual service settings
To access monitoring settings for an individual service:
- In the Dynatrace menu, select Services.
- Select the service you want to configure.
- On the service overview page, open the browse menu (…) and select Edit.
With service-specific monitoring settings you can:
- Edit the default display names of services and add descriptions to improve tracking (in Naming and Web request naming).
- Fine-tune web request 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
You can also configure how sensitive Dynatrace should be to
404HTTP errors (broken links). If some service calls in your application exit due to exceptions—but those calls are still successful from the perspective of your organization—you can define exception classes or patterns that don’t classify such service calls as
- Switch off unwanted alerts about response time degradations, failure rate increases, or changes in load behavior (in Anomaly detection).
When both global and individual service naming rules apply, the system shows only one naming rule. Preview Rule might display different output than how the system actually behaves.