Showing results for 
Show  only  | Search instead for 
Did you mean: 

A lot of all other operations



i am using 12.4.5 for a customer POC. when i try to create a table to show user operation, i see about half of the operation are identified as all other operations. I have already configure the software service to monitor all http urls (, also changed the url autolearning configuration as below:
- changed number of reported URLs to be 1000

- Percentage of new URLs to be 30%

- Size of candidates pool to be 10
- Page loads threshold to be 35%

Anyone knows if there is any other configuration i need to change or any reason why there are so many all other operation?






Please read the below knowledge base to get rid from the all other operations.

I hope this will resolve your problem.




Hi Clare.

Babar points to a good page that will help you to see less of All Other. But if you want to boil it down to something, it's most likely something in the URL that is unique to each and every request. In order to address this,, one way is to follow the pages recommendation and then identify what in the URL it is that is shifting for each request. This part of the URL can then (usually) be adressed with a RegEx or a decode setting that either obscures (removes) the piece that causes issues, or simply decodes it by f.ex. execute Base64 or whatever it is that is obfuscating it.


Hi Clare,

I aggree with Ulf - the page Babar points out is a very good starting point.

I often see a lot of "all other operations" when one of the following situations are present:

  1. the application has some kind of session or page IDs in the URL. Because of this each URL seems to be unique for our monitoring and doesn't make it through the auto learning. In this case it helps to cut out the IDs by putting in some regex for monitored URIs.
  2. the application uses some kind of content types that is different from "text/html" or "text/plain". Often this is "text/xml" or "application/*" . You can activate "monitor all content types" for a specific URI.

Maybe add a rule for (http.*) to the monitored URI page and activate "monitor all content types" for this rule.

You can also take a trace and analyse it to identify if one of the situations I described is visible.

Best regards,