# New Baselines Changes **URL:** \ **Category:** Alerting\ **Tags:** problems-classic\ **Created:** [August 7, 2020, 2:27pm UTC](https://community.dynatrace.com/t/new-baselines-changes/20006 "2020-08-07T14:27:13Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![emily](https://avatars.discourse-cdn.com/v4/letter/e/8c91f0/32.png) [@emily](https://community.dynatrace.com/u/emily)\ **Post date:** [August 7, 2020, 2:27pm UTC](https://community.dynatrace.com/t/new-baselines-changes/20006/1 "2020-08-07T14:27:13Z")
Hello – I’m trying to better understand the new baselining feature that was described in this blog post:[https://www.dynatrace.com/news/blog/dynatrace-innovates-again-with-the-release-of-topology-driven-auto-adaptive-metric-baselines/](https://urldefense.proofpoint.com/v2/url?u=https-3A__www.dynatrace.com_news_blog_dynatrace-2Dinnovates-2Dagain-2Dwith-2Dthe-2Drelease-2Dof-2Dtopology-2Ddriven-2Dauto-2Dadaptive-2Dmetric-2Dbaselines_&d=DwMF-g&c=3_5eq9zYXWRS8ywqccmjfTRKM8mRLoQp6HBg1Tdb_Pc&r=KkNX8ZjrKCAzqRwzssk290b_QkiSsAXh71WtbusR7Xs&m=w57B8zKALAKolrvv-RVPq0RlQOOl9TKRgcAgETp6iDg&s=5lO0jV5wuZwVGD3bCeKUDiX2rK9gLeZG7KKirB7JRV0&e=) I was very excited when I saw this, however I’m having difficulty understanding the details now that I’m looking at it in the tool. Some questions: - Are the thresholds being adjusted automatically on a daily basis? Hourly? By this I mean the duration for which a specific threshold would be constant - Why do the baseline lines in the preview appear at different levels on the 12 hour, 1 day, and 7 day tab? - What is the real way to understand the aggregation – for instance if I have 5 containers and I’m monitoring CPU% across them with aggregation set to “average” what is really happening? Is the threshold set so that if one container breaches the average CPU% of the 5 containers it triggers a Problem? - It seems like the baseline shown in the preview is not the same as the baseline indicated in Problems that are triggered from the alert – is there a reason this would be the case? Thanks for any info. ---
**Author:** ![wolfgang\_beer](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/wolfgang_beer/32/14717_2.png) [@wolfgang\_beer](https://community.dynatrace.com/u/wolfgang_beer)\ **Post date:** [August 7, 2020, 2:43pm UTC](https://community.dynatrace.com/t/new-baselines-changes/20006/2 "2020-08-07T14:43:30Z")
Hi Emily, I think some of your questions are answered in my help page here: > **[Auto-adaptive thresholds for anomaly detection](https://docs.dynatrace.com/docs/dynatrace-intelligence/anomaly-detection/auto-adaptive-threshold)** > > How Dynatrace adapts thresholds for multiple entities within the scope of an anomaly detection configuration. In detail: - Auto-adaptive baselines are updated once a day. - No, appears on the same level, as it shows the current state of the baseline using last 7 days of historic data to calculate the baseline. So it is a moment snapshot of the calculated baseline. - In current state we do not aggregate over entities. The baseline is calculated once a day for every entity that is within the entity filter. So if you select CPU usage metric for 5 hosts, you get 5 baselines updated every day and possibly 5 alerts if baseline is breached. Our plan is to introduce baselines on aggregates with end of this year as well, so that you have both options. - Yes the alert always uses the last updated baseline value for each entity. So again, for 5 hosts you get 5 baselines, one for each host depending on the metric level. You can easily check that by creating a baseline for one host or one service alone, which should be exactly the value shown in the config screen. Best greetings, Wolfgang ---
**Author:** ![emily](https://avatars.discourse-cdn.com/v4/letter/e/8c91f0/32.png) [@emily](https://community.dynatrace.com/u/emily)\ **Post date:** [August 10, 2020, 2:34pm UTC](https://community.dynatrace.com/t/new-baselines-changes/20006/3 "2020-08-10T14:34:51Z")
Hi Wolfgang, Thank you for your response! Can you please confirm my new understanding: - “Auto-adaptive baselines are updated once a day.” So this means the baseline is at a single value (e.g. 1ms) for 24 hours and then could shift to a new value (e.g. 9ms) for the following 24 hours based on subsequent data? Also when during the day does this change happen? (e.g. Midnight) - “In current state we do not aggregate over entities.” So the current selection for the aggregation picklist has no impact in the current release? Thanks Again! Emily ---
**Author:** ![wolfgang\_beer](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/wolfgang_beer/32/14717_2.png) [@wolfgang\_beer](https://community.dynatrace.com/u/wolfgang_beer)\ **Post date:** [August 10, 2020, 2:39pm UTC](https://community.dynatrace.com/t/new-baselines-changes/20006/4 "2020-08-10T14:39:08Z")
- Yes exactly, this current model adapts once a day, based on 7 days of historic data. - The current selection of aggregate refers to the ‘subminute’ aggregate that is used per single line. As e.g.: host cpu metric is collected 6 times a minute for each host, with this selection you can control which line you would like to baseline, the line of the avg of those 6 measurements per minute, the max, min, or count (makes not much sense here). ---
**Author:** ![emily](https://avatars.discourse-cdn.com/v4/letter/e/8c91f0/32.png) [@emily](https://community.dynatrace.com/u/emily)\ **Post date:** [August 10, 2020, 3:13pm UTC](https://community.dynatrace.com/t/new-baselines-changes/20006/5 "2020-08-10T15:13:25Z")
Hi Wolfgang, One last question, promise! Does the same apply to those baselines that were before, like errors, load and response time? Are those also adjusted once every 24hrs? Thanks again! Emily ---
**Author:** ![wolfgang\_beer](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/wolfgang_beer/32/14717_2.png) [@wolfgang\_beer](https://community.dynatrace.com/u/wolfgang_beer)\ **Post date:** [August 11, 2020, 5:23am UTC](https://community.dynatrace.com/t/new-baselines-changes/20006/6 "2020-08-11T05:23:17Z")
No problem at all, happy to answer all your questions. Yes same applies to all built in service and application baselines that already were in place. ---
**Author:** ![DanteP](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dantep/32/41603_2.png) [@DanteP](https://community.dynatrace.com/u/DanteP)\ **Post date:** [September 5, 2020, 6:31pm UTC](https://community.dynatrace.com/t/new-baselines-changes/20006/7 "2020-09-05T18:31:45Z")
Hi [@Wolfgang B.](https://answers.dynatrace.com/users/12838/view.html) Just a quick question. Does this new baseline work OOTB for infrastructure metrics? Or a Custom Alert is required? Does, for example, CPU “Automatic” Anomaly is still [hardcoded](https://www.dynatrace.com/support/help/shortlink/event-types-resource#cpu-saturation) at 95% ? or will now work with a baseline? Is the same with all others Resource events? Thanks! ---
**Author:** ![wolfgang\_beer](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/wolfgang_beer/32/14717_2.png) [@wolfgang\_beer](https://community.dynatrace.com/u/wolfgang_beer)\ **Post date:** [September 7, 2020, 5:38am UTC](https://community.dynatrace.com/t/new-baselines-changes/20006/8 "2020-09-07T05:38:53Z")
Existing settings are unchanged. By the way, CPU as well as Memory are saturation events, I would not set those to baselining, as it would not deliver the same semantics. For a CPU it might be a bit harsh to alert if a learned baseline of 30% is breached with e.g.: 35%. Here i would really leave the threshold based alerting in place.