https://community.dynatrace.com/t5/Open-Q-A/Reason-for-modifying-settings/m-p/202066#M23942 <P><span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:">😊</span> thx!</P> Tue, 10 Jan 2023 15:30:36 GMT wolfgang_beer 2023-01-10T15:30:36Z https://community.dynatrace.com/t5/Open-Q-A/Reason-for-modifying-settings/m-p/201929#M23924 <P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="henk_stobbe_0-1673331833072.png" style="width: 400px;"><img src="https://community.dynatrace.com/t5/image/serverpage/image-id/9316iC2F9E36D38FF97D4/image-size/medium?v=v2&amp;px=400" role="button" title="henk_stobbe_0-1673331833072.png" alt="henk_stobbe_0-1673331833072.png" /></span></P> <P>Hello,</P> <P>In the release notes of version 1.256 you can find above change, a good reminder to always read these before you implement a new version&nbsp;<span class="lia-unicode-emoji" title=":grinning_face:">😀</span></P> <P>The question from my side is, why this default behavior changed by Dynatrace? Or more general what are reasons to changing existing default setiings?</P> <P>&nbsp;</P> <P>KR Henk</P> Tue, 10 Jan 2023 10:21:45 GMT https://community.dynatrace.com/t5/Open-Q-A/Reason-for-modifying-settings/m-p/201929#M23924 henk_stobbe 2023-01-10T10:21:45Z https://community.dynatrace.com/t5/Open-Q-A/Reason-for-modifying-settings/m-p/201975#M23931 <P>Dear Henk,</P> <P>Good catch <span class="lia-unicode-emoji" title=":slightly_smiling_face:">🙂</span> Yes we decided to disable baseline alerts for this specific singelton service by default because we found it always generates a load of alert spam. Reason for this is that the baseline most likely never fits as this singleton service acts as a catch-all for all the non-mapped service endpoints. Those endpoints do not have anything in common between each other and also the baseline therefore is not really valuable.</P> <P>Another issue is that multiple events on this single service always leads to the detection and muting of a so called Frequent issue, which means we detect a load of events which we automatically mute afterwards again. Reason for that is that all those unrelated endpoints share this artificial service.</P> <P>In case that your service does not catch too many endpoints you can easily override the default again as this is a singleton service and you just need to switch the toggle again.</P> <P>I would recommend to split out important endpoints into separate services which then get a valid baseline and where the frequent issue detection does not interfer.</P> <P>I hope that answer helps to understand our reasoning behind changing the defaults here.</P> <P>We will further enhance the release note entry to give more context about the decision.</P> <P>Best greetings,</P> <P>Wolfgang</P> Tue, 10 Jan 2023 12:20:24 GMT https://community.dynatrace.com/t5/Open-Q-A/Reason-for-modifying-settings/m-p/201975#M23931 wolfgang_beer 2023-01-10T12:20:24Z https://community.dynatrace.com/t5/Open-Q-A/Reason-for-modifying-settings/m-p/201985#M23934 <P>Hi Wolfgang,</P><P>A perfect answer,!</P><P>KR Henk</P> Tue, 10 Jan 2023 12:42:07 GMT https://community.dynatrace.com/t5/Open-Q-A/Reason-for-modifying-settings/m-p/201985#M23934 henk_stobbe 2023-01-10T12:42:07Z https://community.dynatrace.com/t5/Open-Q-A/Reason-for-modifying-settings/m-p/202066#M23942 <P><span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:">😊</span> thx!</P> Tue, 10 Jan 2023 15:30:36 GMT https://community.dynatrace.com/t5/Open-Q-A/Reason-for-modifying-settings/m-p/202066#M23942 wolfgang_beer 2023-01-10T15:30:36Z