BT Split by URI and Parameters setup in the ASP.NET Sensor Properties

Hi Mark

Good to hear you got some more insight during todays dynaLearn Webinar.
It seems you undertand the concept as what you describe works exactly as you say. Here are the steps.

Step 1: Filter Measure for PP Duration
You create a new PurePath Duration Measure and give it an upper threshold of 10000ms. Give it a name such as "PurePath longer than 10000.

Step 2: Creat a URI Pattern Measures
Just as we did today during the Webinar. Create a Measure that returns a certain portion of your URL using the URL Pattern Measures Type.

Step 3: Create measures to capture Cookie or Parameter
Depending on what type of information you want to capture from the user, e.g: JSession ID or Parameter - simply create the measures for it

Step 4: Putting it all together into a Business Transaction
Create a new BT and use the PurePath Duration Measures as a filter and the two other Measures as Splitting measure.
In your case you need these BTs for Diagnostics Purpose only. For that reason - and - because you may end up getting lots of splitting values (many JSession IDs, ...) you want to check the box "Suppress storage in Performance Warehouse).

Step 5: Analyze Data
Just open the Business Transaction through the Cockpit and watch the actual users that run into an issue. You will see one line per JSession/Parameter combination.

I hope this helps and confirms that you already got it right with your question

Andi

Mark,

You can create a BT the way you have described it. To do so, follow these steps:

1. Define threshold of 1000ms for the purepath duration.

2. Create a measure by using Server Side Performance ->Transaction based measures->Business Transaction Evaluation/Filter/Grouping Values->Web Requests (Cookie Value). Give a name to this measure. In the cookie field, put LoginKey. Then go to the Details tab of the dialog box and select the checkbox Grouping Measurement and choose Value from the dropdown box.

2. Open the new business transaction dialog box.

3. Put the purepath duration as the filter criteria.

4. Put the above defined measure as the Splitting Results.

Once the BT is created, you will be able to group the purepath by LoginKey that exceeds 1000ms threshold.

Hope this helps.

Asad

Thanks guy, got it working like a charm now.  This will be very helpful.  With this information, we will be able to breakdown URI and Clients with high PP Response times.

quick question, Does BT only show current view, what I mean is that it's probably depending on the PP information, correct.  So if you don't have continuous storage on, then it's probably only going display what's currently in the buffer, correct.

Mark,

BT has two components:

1. PP Information - This requires the PP to be stored in continuous storage. If you don't have continuous storage, BT will only show data from memory.

2. Measure - Like other measures, BT is a measure of its own. This mean that you can plot BT in a chart. For this, the data is persisted in a relational database. Of course, no PP data is shown as part of the measure. Only time series data.

Asad