Problem description

 Starting with DC RUM 12.1, CAS reports show an additional operation, named All other operations. 

How to check what's inside All other operations?

Explanation

The following example describes the situation when there is a small difference between all and All other operations entries in CAS reports (so almost everything is assigned to All other operations).

If company's internal policies allow to make changes to AMD monitoring configuration, with potential performance degradation, then the following scenario is able to show what's inside the All other operations. This one is based on the HTTP decode, but may be used to any other that relies on auto-learning mechanism. Changes are to be made to the specific software service configuration, via RUM Console, when AMD configuration is opened, and specific software service is being edited.

  1. On the URL autolearning tab, set the learning to All.
    Save the configuration and publish it. The effect should be visible within 1-2 sampling intervals since the change.
    1. If All other operations for the last monitoring interval in CAS drop significantly, the answer is that the URLs from 'all other', are not frequent enough to be reported.
      If there is any specific URL that DC RUM users may be interested in, it can be added on the Monitor specific URL tab.
    2. If the numbers do not change, go to step 2.
  2. On the Monitor specific URL tab, set the following regular expression to be monitored:
    (.*)
    with 'use active content type only.
    Save the configuration and publish it. The effect should be visible within 1-2 sampling intervals since the change.
    1. If All other operations for the last monitoring interval in CAS drop significantly, the new URLs that appeared end up with extensions that are not acceptable - for example jpg. If such a URL appears, then it means that some jpg elements come with text/html response.
    2. If the numbers do not change, go to step 3.
  3. On the Monitor specific URL tab, set the following regular expression to be monitored:
    (.*)
    with 'all content types'.
    Save the configuration and publish it. The effect should be visible within 1-2 sampling intervals since the change.
    The number of All other operations for the last monitoring interval in CAS should be now down to 0. This means that traffic that is monitored, gets response for URLs, which is not in the current 'active content type' configuration. In order to go on with investigation, there is a need to capture some traffic for the software service, and analyze the response content types which are in there.

Root Cause

Since the very beginning, AMD was capable of counting how many requests were made to the server and listing the most frequent operation names, together with number of their occurrence.

In earlier releases, there was no 'All other operations' row, so if there was a need to calculate how many requests did not have operation names, you had to subtract the sum of requests for named operations, from the number of requests reported per server.

Due to the URL aging mechanism on CAS, the number calculated for today was different from the one calculated the next day. In that case, to have the number constant, additional operation name has been introduced.

  • No labels