MyObservability
Service Management
- Creating custom Services
- Managing custom Services
- Service Error & Anomaly Detection Settings
- Configuring Web Request Naming
- Key Requests
- Creating Request Attributes
Creating custom services
Dynatrace allows you to define any method, class or interface as the entry point of a custom service to be monitored.
- Custom services can have multiple entry points
- Methods of a specific class or implementations of an interface can be used as entry point.
- Each non-recursive call to such a method represent a single request.
- Custom services do not associate transactions - they create a new entry point.
- Dynatrace stitching is done via the x-dynatrace header.
Validate & Save changes
Managing custom Services
Custom queueu messaging services:
Dyantrace automatically detects eventbase message handlers. However if application does not use such message services, you can choose to create custom messaging services.
Service Error & Anomaly Detection Settings
Dynatrace provides rules to manage both service errors and anomalies.
Anomaly Detection:
- Detect response time degradations.
- Detect increase in failure rate.
- Detect service load drops: Alert if the observed load is lower than the expected load by a specified margin for a specified amount of time.
- Detect service load spikes: Alert if the observed load exceeds the expected load by a specified margin for a specified amount of time.
Configuring Web Request Naming
Dynatrace provides end-to-end tracing of web requests, tracking each URL path separately. Some cases it might be too granular. By using request attributes and naming rules, you can better define business transactions for monitoring and web request names that are readable and east to track.
Key Requests
Certain requests in your web application environment require special attention, like a login request or shopping cart checkout request either because they are critical measure of the success of your business or they may provide vital technical functionality that your application relies on.
Dynatrace provides advanced monitoring functionality for such “key requests”, so that you can monitor them with extra care.
While details request histories are kept for 10 days by default. key requests are maintained for 35 days. and granularity levels persist much longer than standard requests.
Trend lines are retained forever.
Dynatrace assumes that requests that contribute less than 1% to the overall load of a service are less important than high-volume requests. This means low volume requests won’t trigger an alert unless they effect the service’s overall response time or failure rate.
By tagging important low-volume requests as key requests, this ensures that they have standard alerting thresholds.
To tag a specific request as a key request,
Creating Request Attributes
You can request certain data values (Metadata) like revenue etc
Deep service monitoring
Dynatrace OneAgent automatically traces each detected transaction end-to-end, capturing all related WebRequest calls, database calls, remote calls, exceptions, and more. Use the settings below to exclude certain URLs or exceptions from capture to reduce network bandwidth, storage requirements, misleading alerts, or other monitoring noise.
- Exclude noisy and unnecessary exceptions
- Exclude specific incoming web request URLs
- Real-time updates to Java and PHP services
- Distributed tracing
Main Page: Services
Next Page: Monitoring Services
Dynatrace : Main Page