non-web (Batch Java) BT configuration question
Instrumented the entry method to execute and start Pure Path.
Created a method timer measure on that entry method with Thresholds
Configured a BT (server) with a filter of Timer measure. But in doing this, the BT only captures PurePaths that exceed the Threshold.
If we want to capture/measure all transactions, how would I specify a filter for this?
Hi Mary Ann,
If you create the measure Methods -> Invocation on the entry method and set the threshold to 1. You would then make sure the count aggregation is chosen in the BT Filter.
This will give you every PurePath where that method is called.
Thanks,
David
thanks David, let me give that a try and will post my findings!
Adding an invocation filter worked fine so now I have all of the Pure Paths. I still have the defined Method execution time measure defined upon which I created an incident when the sever time is exceeded. At this point there is no user (by user I mean me) applied connection between the Business Transaction using the invocation filter to the execution time measure for the method. Is there any value or is it more or less correct to add this measure to the Calculate Results section of the BT?
I do not want to cause uneeded calculations to occur that may result in increasing overhead, but I want to approach this in the mpst effective manner.
BTW, I have a more complicated online scenario for which I will submit another question for soon
Hi Mary Ann,
Good to know that things are mostly working the way you would like them to.
To answer your next question, you are probably all set with using the default PurePath Response Time/Count measures (the check box) in the BT. This will show you the response time of that PurePath. You could use the method time measure you already have created. The thing with using this is how you have it set up. If the method gets called multiple times in the PurePath, you need to decide if you want to have the average of all of the times it's called or just the first; there is the check box "Only Analyze first occurrence in the PurePath" in the measures config.
You can test to see which results measures you want by unchecking the Store Results in Performance Warehouse in the BT config. Then you can add the results you want to see which you would like the most. The results are kept in server memory only so it only lasts a short time and you won't have historical data. Doing this allows you to test without causing any new measures in the Performance Warehouse.
Thanks,
David
David,
Thanks so much for your responsiveness and for the Performance Warehouse recommendation, which will be useful.
So I assume that you are saying that if I do not hook the measure to the BT, the resulting information will be short-lived, and not be stored in the Performance Warehouse? That makes sense, since storing it is specified in the BT 
If the method only gets called once per execution (it is an entry point to a batch java job), are there overhead benefits to checking only analyze first occurrence per purepath?
What we ultimately want to achieve is the following (learning in steps, of course): For a specified set of Business Transactions (BT's), Measure the response time, alerting via email when 99.3 of responses do not respond on or below a specified time in ms. For now, I am using the measure I described and an average for alerting..... This is not an immediate need, just curious if you encountered anyone with a similar requirement. If I can set a baseline and not let the DT application derive it, maybe I can use that..... what do you think?
Hi Mary Ann,
You are welcome, glad I could help.
I do not know enough to answer your overhead question, but if I had to guess, it would be negligible because the method is only called once in the PurePath. Maybe someone else with more knowledge can answer this?
Unfortunately, I do not know of anyone with similar requirements as you have but there may be others on the community who have.
Best of luck,
David
Community Member of the Month
April 2018
Announcing Dynatrace's Community Member of the Month for April 2018, Babar Q.! Click here to read more!