Welcome!

APM Blog

Subscribe to APM Blog: eMailAlertsEmail Alerts
Get APM Blog via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Blog Feed Post

Custom anomaly detection for key requests

A key feature of Dynatrace is its ability to continuously monitor every aspect of your applications, services, and infrastructure and to automatically learn the baseline performance metrics related to these components. Dynatrace also automatically learns the baseline response times and failure rates of all requests that are vital to the success of your business. Now, for the first time, you can adjust anomaly detection settings for individual web requests.

By understanding the baseline performance of individual service requests Dynatrace can intelligently analyze highly divergent response times of multiple requests within the same service. For example, while the service request orange.jsf may have a median response time of 200 ms, the request orange-booking-payment.jsf within the same service may be faster, with a median response time of 25 ms. Dynatrace understands such differences and will raise an alert if either request begins to respond more slowly than these established baselines.

Parameterized anomaly detection for key requests

There are several use cases for which parameterization of automatic baselining algorithms may be beneficial at the request level:

  • To set lower response-time thresholds for specific, business-critical service requests.
  • To set higher response-time thresholds for volatile service requests that are non-business critical.
  • To set a fixed threshold rather than a relative threshold for requests that have a defined SLA.
  • To set a fixed threshold rather than a relative threshold for requests that have a defined timeout point.
  • To disable alerting for specific, non-business critical requests.

Each of these use cases can now be achieved for web requests. The first step is to manually identify specific requests as key requests.

Specify a specific web request as a key request:

  1. Open the navigation menu and select Transactions & services.
  2. Select the relevant service from the list.
  3. On the service page, click Show all requests.
  4. Scroll down and select the request you want to edit.
  5. On the request page, click the Priority link to reset the priority from Normal to High. All requests that have High priority are key requests.

Now adjust the anomaly detection settings for the service that this request is associated with.

Adjust anomaly detection settings for the service:

  1. Open the navigation menu and select Transactions & services.
  2. Select the relevant service from the list.
  3. On the service page, click Browse (…) button.
  4. Click Edit.
  5. On the Service settings page, click Anomaly detection.
    A new Set threshold on key transactions section has been added to the bottom of this page.
  6. Select the key request that you’re interested in.
  7. Now adjust the anomaly detection settings for this particular web request. For full details, see 
    Threshold settings.

The post Custom anomaly detection for key requests appeared first on Dynatrace blog – monitoring redefined.

Read the original blog entry...

More Stories By APM Blog

APM: It’s all about application performance, scalability, and architecture: best practices, lifecycle and DevOps, mobile and web, enterprise, user experience