Answer by Jerry L. ·
When your viewing methods in a purepath and you see a light gray M, then that is a method picked up via the auto sensor. Right Click on it and select create measure, this will allow you to defined a measure on the method(essentially) this will start the process of establishing a custom sensor as you follow the dialog box. Note: that you cannot hot sensor place in the dotnet world so the worker process will have to be recycled to capture data. Again you only really want to include these methods if you want to obtain some kind of data related to there execution(count/CPU) or obtain some kind of method return value.
Answer by Yuwen L. ·
Thank you so much for the explanation, I got your point with the way to use predefined measure. As for Sensor, My Application is .net Application, I have not heard of how sensors can be placed, also, how to define custom sensor? again, we are in windows .net world.
your help is truely appreciated.
Answer by Jerry L. ·
So I am assuming you used the default measure-(selected one that is already defined in DT). I usually don’t change those since we have some things that may or may not be dependent upon them. I usually create my own (copy/with a new name) to use as measure with my custom thresholds.
The Auto Sensors is a snapshot of threads and methods that allow us to provide a complete view of the execution path. We do not have any byte code injection on those methods. So the timings are not exact and often carry the elapsed time from the previously byte code captured method. If they are determined to be providing a contribution to the overall execution time they are included in the purepath display.
Now you could add a custom sensor and thus get a specific execution time, but the thought is that these methods are so fast that getting the timings would take more resources than the methods themselves. The only time I would add them as a custom sensor is if in fact I needed an exact timing or I wanted to capture a return value from the method.
The rest of our sensors are the out-of-the-box sensors for known technologies like JNDI, JDBC, thread-tagging, Servlets, etc. These are instrumented and have exact timings.
I focus my attention around the:
Exec Total – overall time consumed by method (from entry to exit)
Exec – time within specific method itself
Elapsed –time from entry thru purepath to eclosing (end of purepath)
In the upper right corner of the purepath display you have a Show all Nodes or Show Only Relevant Nodes. This will bring all methods captured by auto sensors into view. If is suspect one of those methods captured by an auto sensor is the culprit, then I will add customer sensor and gather exact timings for it. Depending upon the JVM and the release you can Hot Sensor Place and add the instrumentation without a restart of the application
Answer by Yuwen L. ·
thank you Jerry, I appreciate it. I will take a look.
Finally, I figured our how to Add Dashlets to Dashboard, I am from .net world, not that familiar with Java based UI.
however, I do have questions:
1) when a measure being added to a chart, I can edit the measure's threshold, however, when I save it, it says it will update the transaction: Web Request Response(this is the measure that I selected), however, when I say yes, it did not save any way, do I have to create a custom measure to specify the threshold?
2) can you shed some light on the auto sensor vs none auto sensor? I am still not that confident on understanding the execute time and time elapsed on purepath tree? basically how to make use of the information from the purepath tree.
Answer by Jerry L. ·
Can you import this session file?
I have the BT's and measures in the session file. You can just copy the BT from the session file to your application profile.
Then open the dashboard which should use the BT/Measures I have defined
Answer by Yuwen L. ·
Hi, Jerry:
Would you please show me how to create the dashboard like yours? for some reason, I am not able to place the dashlets I created on a dashboard like yours, the dashlet showed up as individual tabs, btw, I chose custom chart as dashlet type.
Thanks
JANUARY 15, 3:00 PM GMT / 10:00 AM ET