Web Page Requests by URI Stopped Capturing
The Built-in business transaction Web Page Requests by URI stopped capturing data today. This powers several of our response time/load graphs which are now blank. What would cause this "new measurements available" and how do I re-enable it?
I figured it out. The ASP.NET sensors properties need the Request Header user-agent 'Parameter and Attribute' added. We had removed this looking for ways to reduce the information we were capturing. Didn't grasp the consequence.
Hi Jason
Thanks for giving us the update on this. As you figured out correctly our Built-In Business Transaction rely on some of the out-of-the-box captured data such as the user-agent string. We use this to e.g: identify requests from Bot's (Google, Bing, ...)
To help a little with your job on reducing data that you capture. Here are some best practice tips
a) reduce the length of SQL
b) dont capture bind values unless really needed
c) exclude exceptions that you dont need -> go to the exception dashlet and check which exceptions are thrown very often and which dont give you a lot of value
d) dont capture stack traces for exceptions or at least lower the stack depth
e) make sure you do not capture http parameters that you do not need
f) make sure you do not capture method arguments you do not need
The next dynaLearn webinar we host next week will actually talk about just these topics. you may want to check it out: dynaLearn Webinar Update - Next Webinar on Fine-tuning dynaTrace - July 11
cheers
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 