how to create a measure to return the number of purepaths that is shorter than 100ms and longer than 40ms?
I'm trying to create a chart to show the number of special purepaths related to host CPU. I created a measure using "Web Request Response Time" template and set Lower Severe to 40ms and Upper Severe to 100ms. Then I configured the Series to use "Count" as aggregation.
It does create the chart. But when I change the aggregation to min or max, the displayed data showing the condition (shorter than 100ms and longer than 40ms) doesn't work.
Please help.
Thanks,
Yifan
You will need a business transaction with two filter criteria. One filtering out all PPs that are shorter than 40ms and another one that filers out everything that took longer than 100ms - the remaining PPs are the ones you look for.
Best, ROman
You'll want one of the measures to have an upper severe of 40 and the other will have the lower severe of 100
I tried business transaction using the filters. However, the split doesn't work with agent. I have 3 agents with same agent name but from different hosts. When I chart with measure different, there're an split option of "Agent Host" which works perfectly. But with BT, the default split option "Agent" doesn't work in our case. Could you explain why one measure with Lower Severe of 40ms and Upper Severe of 100ms doesn't work? I'm always confused by what the "Lower Severe", "Upper Severe", "Lower Warning", "Upper Warning" mean.
Thanks,
Yifan
Hi Yifan,
Lets tackle your problem one by one - once the filter is working try getting the split criteria set up. You'll need two filter criteria like this, as Rob wrote on with upper 40 and one with lower 100:
As for the split - what do you want to distinguish the PPs by?
Best, Roman
EMEA Community Member of the Month - November 2018
Announcing Dynatrace's EMEA Community Member of the Month for November 2018, Mathieu C.! Click here to read more! LATAM Community Member of the Month - November 2018
Announcing Dynatrace's LATAM Community Member of the Month for November 2018, Rene S.! Click here to read more! 
