Mute monitoring of service requests

Dynatrace monitors all server-side server requests end-to-end. When the performance or success rate of a specific request degrades, Dynatrace raises an alert. However, not all high-load requests are important and not all slow requests should raise alerts.

A good example of these are heartbeat requests. Heartbeat requests commonly arrive in high volume and frequency. These requests can distort the overall median response times of services. Such requests can trigger response-time alerts that distract you from the performance of the important requests that actually affect the user experience of your applications.

Dynatrace enables you to mute alerts for such problematic service requests and exclude them from the service chart so that you can focus on the performance of requests that affect your customers.

Mute a request

  1. Select Transactions & services from the navigation menu.
  2. On the Services page, select the service that receives the request you want to mute.
  3. Select View requests.
  4. Select the request you want to mute.
  5. On the request Details page, open the browse menu () and select Mute.

The request’s Details page displays the message This request has been muted. Going forward, Dynatrace will not alert on this request and record its data separately.

Muted service requests remain accessible (and even remain visible in request lists for a limited period of time) but their response times are no longer factored into overall metrics and charts.

Adjust reference periods for alerting

In some cases, muting a high-volume request can result in fake response-time degradation alerts. This only happens in rare cases and the reason is the displayed shift in the median and the corresponding change in the underlying request distribution. If this happens, it’s best to reset the reference period for alerts on this service. By doing this, Dynatrace will establish new performance baselines that exclude the muted request.

To adjust alerting reference periods for your specific service

  1. Select Transactions & services from the navigation menu.
  2. On the Services page, select the service that receives the request you’ve muted.
  3. On the service page, open the browse menu () and select Edit.
  4. Select Anomaly detection.
  5. In the Reference period section, select Reset.

List and unmute muted requests

Data for muted requests is still being recorded, but in a separate place.

To list all muted requests

  1. Select Transactions & services from the navigation menu.
  2. On the Services page, select the service that receives the request you’ve muted.
  3. In the Muted requests section, select View muted requests.
    Here you have access to all previously muted requests.

To unmute a request

  1. Select the muted request.
  2. On the Details page, open the browse menu () and select Unmute.

The request is removed from the muted request list, new data is recorded normally again, and alerting is re-enabled for that request.