In Dynatrace, response time/error rates/loadings of services are monitored by dynamic and automatic baselines.
On the other hand, however, infrastructure monitoring is on the basis of not those baselines but pre-defined or user-defined static thresholds.
I wonder why Dynatrace doesn't use automatic baselines for infrastructure monitoring.
Are there any reasons for this?
Answer by Wolfgang B. ·
Within Infrastructure metrics you can go with the 'automatic' mode as well but that does mean that Dynatrace decides on a good default threshold. You can overwrite the automatic mode by setting your own static thresholds.
You are right that we do automatically baseline all key performance metrics, error rate and traffic in a dimensional baseline cube (time to first byte, speed index, response time, visually complete, DOM interactive) as well as the service response time and error rates.
Within infrastructure metrics the automatic mode in many cases means to use the best practice standards that the individual vendors propose, such as thresholds introduced by AWS, VMWare, etc.
Answer by Dave M. ·
The static threshold technique is evolving with the new AI 2.0:
Answer by Kohei S. ·
Oh, is that so?
The reason why I consider that infrastructure monitoring uses only static thresholds is the following URL.
This page seems to say that automated baseline can be used only for applications or services monitoring and infrastructure metrics aren't monitored with baselines.
Maybe, am I misunderstanding this description...?
Answer by Sebastian K. ·
According to my experience infrastracture metrics by default are using baselines and static thresholds as well... we’ve got reports from Dynatrace not only when static threshold were used but when change from pattern was to big as well. Why do you assume that there are only static thresholds?
Merge database services 1 Answer