You won't find it - max slow operation threshold is a virtual and auxiliary metric that may smoothies be useful on reports. It represents the highest slow operation threshold value when report aggregates data for operations that in software services definition have different thresholds set up.
Consider a software service SS that has two user-defined operations: URL-A and URL-B. Slowness threshold for URL-A is 15 sec, for URL-B it's 5 sec. When a report is created for software service SS, you can report on total number of operations and number of slow operations for SS. Those numbers will be deterministic. But one can ask "so what does it mean ''slow'' for SS?". The answer is not deterministic because it's different depending on which URL (A or B) has been loaded. Max slow operation threshold helps to understand the sense of slowness for the whole software service if there's no simple deterministic answer.
Hope this helps
As we try to migrate from v12 to v17 our user community has SLA request to be set to 3 secs .... it looks like the metric currently set to 8 secs in v17, while in our v12 environment I was able to set this metric to 3 secs. This 8 sec value seems to be the primary metric threshold being used from the Slow Operations metric. Unless I am mis-reading the reports, this is causing the daily reports comparison of Slow Operations from v12 to v17 to be drastically different. Any thoughts?
Operation time threshold setting is in the same place in 17 as it was in 12.4. Per software service and per URL settings should have been migrated during the upgrade. If they weren't, it might be a bug?