<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Advice Needed: Best Practices for Service Detection Rules in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Advice-Needed-Best-Practices-for-Service-Detection-Rules/m-p/254122#M4775</link>
    <description>&lt;P&gt;Update: I enabled a full web service rule to detect a service as a web request service by setting a condition on &lt;EM&gt;&amp;lt;NameService.svc&amp;gt;&lt;/EM&gt;. It seems to be tracking correctly, so I’m considering making this the default rule without conditions, as it applies to multiple scenarios. Has anyone experienced a service being split into two entities: a web request service and a web service?&lt;/P&gt;&lt;P&gt;######&lt;/P&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm seeking guidance on best practices for creating a service detection rule. We have a service in our environment that is being detected as two separate entities, which is causing discrepancies in our alerting. Currently, it's recognized as &lt;EM&gt;&amp;lt;NameEntryPoint.API&amp;gt;&lt;/EM&gt; and &lt;EM&gt;&amp;lt;NameService.svc&amp;gt;&lt;/EM&gt;, but it should be detected as &lt;EM&gt;&amp;lt;NameEntryPoint.API&amp;gt;\&amp;lt;NameService.svc&amp;gt;&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;I've reviewed the documentation (&lt;A href="https://docs.dynatrace.com/docs/platform-modules/applications-and-microservices/services/service-detection-and-naming/customize-service-detection#create" target="_blank" rel="noopener"&gt;Service detection rules - Dynatrace Docs&lt;/A&gt;), but I'm looking for specific best practices or recommendations on how to address this issue effectively. Any insights or advice would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Sincerely,&lt;/P&gt;&lt;P&gt;Lance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 30 Aug 2024 17:59:45 GMT</pubDate>
    <dc:creator>lwaldrop</dc:creator>
    <dc:date>2024-08-30T17:59:45Z</dc:date>
    <item>
      <title>Advice Needed: Best Practices for Service Detection Rules</title>
      <link>https://community.dynatrace.com/t5/Alerting/Advice-Needed-Best-Practices-for-Service-Detection-Rules/m-p/254122#M4775</link>
      <description>&lt;P&gt;Update: I enabled a full web service rule to detect a service as a web request service by setting a condition on &lt;EM&gt;&amp;lt;NameService.svc&amp;gt;&lt;/EM&gt;. It seems to be tracking correctly, so I’m considering making this the default rule without conditions, as it applies to multiple scenarios. Has anyone experienced a service being split into two entities: a web request service and a web service?&lt;/P&gt;&lt;P&gt;######&lt;/P&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm seeking guidance on best practices for creating a service detection rule. We have a service in our environment that is being detected as two separate entities, which is causing discrepancies in our alerting. Currently, it's recognized as &lt;EM&gt;&amp;lt;NameEntryPoint.API&amp;gt;&lt;/EM&gt; and &lt;EM&gt;&amp;lt;NameService.svc&amp;gt;&lt;/EM&gt;, but it should be detected as &lt;EM&gt;&amp;lt;NameEntryPoint.API&amp;gt;\&amp;lt;NameService.svc&amp;gt;&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;I've reviewed the documentation (&lt;A href="https://docs.dynatrace.com/docs/platform-modules/applications-and-microservices/services/service-detection-and-naming/customize-service-detection#create" target="_blank" rel="noopener"&gt;Service detection rules - Dynatrace Docs&lt;/A&gt;), but I'm looking for specific best practices or recommendations on how to address this issue effectively. Any insights or advice would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Sincerely,&lt;/P&gt;&lt;P&gt;Lance&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 30 Aug 2024 17:59:45 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Advice-Needed-Best-Practices-for-Service-Detection-Rules/m-p/254122#M4775</guid>
      <dc:creator>lwaldrop</dc:creator>
      <dc:date>2024-08-30T17:59:45Z</dc:date>
    </item>
    <item>
      <title>Re: Advice Needed: Best Practices for Service Detection Rules</title>
      <link>https://community.dynatrace.com/t5/Alerting/Advice-Needed-Best-Practices-for-Service-Detection-Rules/m-p/265451#M5256</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/60570"&gt;@lwaldrop&lt;/a&gt;! How did it go, did you apply it as the default rule? It would be great if you share your case with the Community &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Dec 2024 09:12:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Advice-Needed-Best-Practices-for-Service-Detection-Rules/m-p/265451#M5256</guid>
      <dc:creator>GosiaMurawska</dc:creator>
      <dc:date>2024-12-17T09:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: Advice Needed: Best Practices for Service Detection Rules</title>
      <link>https://community.dynatrace.com/t5/Alerting/Advice-Needed-Best-Practices-for-Service-Detection-Rules/m-p/266104#M5295</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/77704"&gt;@GosiaMurawska&lt;/a&gt;. No I haven't tried this yet as other things come up. I was also hoping someone else may have tried it first. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Dec 2024 18:16:56 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Advice-Needed-Best-Practices-for-Service-Detection-Rules/m-p/266104#M5295</guid>
      <dc:creator>lwaldrop</dc:creator>
      <dc:date>2024-12-23T18:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: Advice Needed: Best Practices for Service Detection Rules</title>
      <link>https://community.dynatrace.com/t5/Alerting/Advice-Needed-Best-Practices-for-Service-Detection-Rules/m-p/266288#M5301</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/60570"&gt;@lwaldrop&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Simply it depends on the actual detected request and service. the documentation is giving a proper guidance for:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Internally through the monitored servers&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Web request.&lt;/LI&gt;&lt;LI&gt;Web Service.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Externally&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Web request.&lt;/LI&gt;&lt;LI&gt;Web Service.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;For example&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Regarding the external APIs or External endpoints you can configure the public domain name.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;For internally monitored services, it depends on mainly how many segments the service is composed of.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Tip&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;To facilitate the composition of service detection rules, have a deeper look into the services properties &amp;amp;&amp;amp; Tags section as it contains the most unique attributes based on which you can draft the service detection rules that fits the current setup.&lt;/LI&gt;&lt;LI&gt;You can try multiple attempts on testing environments and you will notice how it works practically and then take notes of the actual findings for further enhancements.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Hoping it adds value.&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Dec 2024 05:18:45 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Advice-Needed-Best-Practices-for-Service-Detection-Rules/m-p/266288#M5301</guid>
      <dc:creator>Peter_Youssef</dc:creator>
      <dc:date>2024-12-30T05:18:45Z</dc:date>
    </item>
  </channel>
</rss>

