<?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 Re: Specific time based Health Rules in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Specific-time-based-Health-Rules/m-p/729512#M6709</link>
    <description>&lt;DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;Hi &lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/153232"&gt;@Srimukundan.T&lt;/A&gt;&amp;nbsp;,&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;SPAN&gt;Thank you for posting to the community.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;As written in the last comment at the related post, you can use "Wait time after violation" to throttle the continuing health rule violations.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;A href="https://docs.appdynamics.com/21.6/en/appdynamics-essentials/alert-and-respond/health-rules/health-rule-schedules#HealthRuleSchedules-HealthRuleWaitTimeAfterViolation" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/21.6/en/appdynamics-essentials/alert-and-respond/health-rules/health-rule-schedules#HealthRuleSchedules-HealthRuleWaitTimeAfterViolation&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;SPAN&gt;For example, if you set 240 minutes(4 hours) of "Wait time after violation" on a health rule and health rule violation continues for 4 hours, then you will get an alert at the beginning and after 4 hours.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;* If the violation doesn't continue for 4 hours, you will get an alert after violation is triggered again even within 4 hours. By setting "Use data from last" with a large value, the violation may continue for a long time.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;SPAN&gt;Hiroki&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Tue, 29 Jun 2021 02:16:55 GMT</pubDate>
    <dc:creator>Hiroki_Ito</dc:creator>
    <dc:date>2021-06-29T02:16:55Z</dc:date>
    <item>
      <title>Specific time based Health Rules</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Specific-time-based-Health-Rules/m-p/729511#M6708</link>
      <description>&lt;P&gt;Hi, I also have the same issue&amp;nbsp;&lt;/P&gt;

&lt;P&gt;I want to trigger the alert like below.&lt;/P&gt;
&lt;P&gt;Once the alert starts, there should an alert.&lt;/P&gt;
&lt;P&gt;After a certain amount of time, say 4 hours, I should get another alert. I should not get the alert in between.&lt;/P&gt;

&lt;P&gt;Did anyone reply to this or is there any solution like setting up the throttle?&lt;/P&gt;

&lt;P&gt;This post is related to this existing Community post:&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/Dashboards/Time-based-health-rules-not-possible/m-p/29930#M337" target="_blank"&gt;https://community.appdynamics.com/t5/Dashboards/Time-based-health-rules-not-possible/m-p/29930#M337&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jun 2021 04:29:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Specific-time-based-Health-Rules/m-p/729511#M6708</guid>
      <dc:creator>srimukundant</dc:creator>
      <dc:date>2021-06-28T04:29:07Z</dc:date>
    </item>
    <item>
      <title>Re: Specific time based Health Rules</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Specific-time-based-Health-Rules/m-p/729512#M6709</link>
      <description>&lt;DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;Hi &lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/153232"&gt;@Srimukundan.T&lt;/A&gt;&amp;nbsp;,&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;SPAN&gt;Thank you for posting to the community.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;As written in the last comment at the related post, you can use "Wait time after violation" to throttle the continuing health rule violations.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;&lt;A href="https://docs.appdynamics.com/21.6/en/appdynamics-essentials/alert-and-respond/health-rules/health-rule-schedules#HealthRuleSchedules-HealthRuleWaitTimeAfterViolation" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/21.6/en/appdynamics-essentials/alert-and-respond/health-rules/health-rule-schedules#HealthRuleSchedules-HealthRuleWaitTimeAfterViolation&lt;/A&gt;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;SPAN&gt;For example, if you set 240 minutes(4 hours) of "Wait time after violation" on a health rule and health rule violation continues for 4 hours, then you will get an alert at the beginning and after 4 hours.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;* If the violation doesn't continue for 4 hours, you will get an alert after violation is triggered again even within 4 hours. By setting "Use data from last" with a large value, the violation may continue for a long time.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;SPAN&gt;Best Regards,&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;BR /&gt;
&lt;DIV&gt;&lt;SPAN&gt;Hiroki&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 29 Jun 2021 02:16:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Specific-time-based-Health-Rules/m-p/729512#M6709</guid>
      <dc:creator>Hiroki_Ito</dc:creator>
      <dc:date>2021-06-29T02:16:55Z</dc:date>
    </item>
  </channel>
</rss>

