<?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 Alerting on /actuator/health on AKS in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Alerting-on-actuator-health-on-AKS/m-p/299948#M6342</link>
    <description>&lt;P&gt;Good morning,&lt;/P&gt;&lt;P&gt;I'm looking to get some advice on alerting for (or without)&amp;nbsp;/actuator/health requests on AKS.&lt;/P&gt;&lt;P&gt;Our naming rules for services are using namespace_workload_className, resulting often in having the actuator bundled together with other requests.&lt;/P&gt;&lt;P&gt;I've considered to mute them or modify naming rules to create a separate service, but honestly I'm not sure. I have been dragging and thinking about this topic for a while so I've decided to ask for some help.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;From my understanding, the main purpose of actuator is to do a low level technical health check and trigger a auto restart on failure, so you might as well alert on restarts and ignore these requests?&lt;/LI&gt;&lt;LI&gt;How are you handling actuator on your environment?&lt;/LI&gt;&lt;LI&gt;Are there benefits for alerting on other endpoints if you stop considering the actuator requests, Dynatrace today (with grails) already gives you alerts by endpoint even if you don't mark as key requests, right?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Appreciate your time.&lt;BR /&gt;Best regards,&lt;BR /&gt;Rafael&lt;/P&gt;</description>
    <pubDate>Tue, 26 May 2026 11:46:39 GMT</pubDate>
    <dc:creator>RafaelF</dc:creator>
    <dc:date>2026-05-26T11:46:39Z</dc:date>
    <item>
      <title>Alerting on /actuator/health on AKS</title>
      <link>https://community.dynatrace.com/t5/Alerting/Alerting-on-actuator-health-on-AKS/m-p/299948#M6342</link>
      <description>&lt;P&gt;Good morning,&lt;/P&gt;&lt;P&gt;I'm looking to get some advice on alerting for (or without)&amp;nbsp;/actuator/health requests on AKS.&lt;/P&gt;&lt;P&gt;Our naming rules for services are using namespace_workload_className, resulting often in having the actuator bundled together with other requests.&lt;/P&gt;&lt;P&gt;I've considered to mute them or modify naming rules to create a separate service, but honestly I'm not sure. I have been dragging and thinking about this topic for a while so I've decided to ask for some help.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;From my understanding, the main purpose of actuator is to do a low level technical health check and trigger a auto restart on failure, so you might as well alert on restarts and ignore these requests?&lt;/LI&gt;&lt;LI&gt;How are you handling actuator on your environment?&lt;/LI&gt;&lt;LI&gt;Are there benefits for alerting on other endpoints if you stop considering the actuator requests, Dynatrace today (with grails) already gives you alerts by endpoint even if you don't mark as key requests, right?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Appreciate your time.&lt;BR /&gt;Best regards,&lt;BR /&gt;Rafael&lt;/P&gt;</description>
      <pubDate>Tue, 26 May 2026 11:46:39 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Alerting-on-actuator-health-on-AKS/m-p/299948#M6342</guid>
      <dc:creator>RafaelF</dc:creator>
      <dc:date>2026-05-26T11:46:39Z</dc:date>
    </item>
  </channel>
</rss>

