Static response time threshold in Application Overview
I was wondering if it's possible to set a static threshold/baseline for all applications or system profiles on a server. By default, the baselines are calculated dynamically which does not work for this application. Traffic switches between two stacks (defined as system profiles) every week or two. While traffic is on profile A, profile B will have a low response time. When a traffic switch happens, profile B's response time will increases and dynaTrace shows a lot of red. It will then take dynaTrace a few days to learn the new threshold all the while showing red because of the increase in response time on the profile.
It is possible to configure base lines manually but you have to drill down to Splitting level within the application overview to do it.
Tom
Hi Tom
You bring up a good point. Right now you can really only set it on a per splitting base. This can become very cumbersome if you have lots of splittings. I will check internally if there is any shortcut for this
Andi
Thanks, Andi.
Please let me know at your earliest convenience if there can be an easier way to do this. This is a big concern for my customer.
Thanks,
Tom
Just got word from the engineering team. There is not an easier way to do this through the application overview.
BUT - if they have static thresholds why not just set that Static Threshold on the Result Measure of that BT and instead of using the Application OVerview and the baselining (which you dont really need if you have static baselines anyway) - simply create an Incident that triggers when the threshold is exceeded?
Wouldnt that actually make more sense?
This question sparked from our production support team. They tend to use the application overview to monitor application health and we have numerous monitors throughout our offices with this view. With the autolearning baseline on this view, after traffic switches there tends to be a lot of red for response time which causes tickets to be opened or emails sent to the dev team. I'd like to avoid this while still allowing our teams here to use the application overview. I could suggest resetting the baselines after traffic switching - that will likely be the easiest way to avoid lots of red response time after traffic switching.
That sounds like a practical solution
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! 