<?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: Health rule based on application changes in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Health-rule-based-on-application-changes/m-p/721367#M2563</link>
    <description>&lt;P&gt;Hi Gurmit,&lt;/P&gt;

&lt;P&gt;The intent of the rule is to easily detect if an application is recycling&amp;nbsp;frequently, as this may indicate that a private memory limit for instance, is exceeded easily. I suppose checking the availabilty of a tier could also cover this in some way. I will try this&amp;nbsp;first. Thanks for the quick reply!&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;

&lt;P&gt;Simon&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jul 2017 09:18:39 GMT</pubDate>
    <dc:creator>CommunityUser</dc:creator>
    <dc:date>2017-07-21T09:18:39Z</dc:date>
    <item>
      <title>Health rule based on application changes</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Health-rule-based-on-application-changes/m-p/721365#M2561</link>
      <description>&lt;P&gt;I would like to create a health rule that is based on application changes. For instance, a rule that is violated when&amp;nbsp;the app server of a specific node has been restarted more than x times within a specified time&amp;nbsp;range. It seems that this value is not considered as a metric and therefore cannot be referenced in the health rule violation wizard. Am i missing something here or is this simply not supported?&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jul 2017 13:03:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Health-rule-based-on-application-changes/m-p/721365#M2561</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2017-07-20T13:03:57Z</dc:date>
    </item>
    <item>
      <title>Re: Health rule based on application changes</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Health-rule-based-on-application-changes/m-p/721366#M2562</link>
      <description>&lt;P&gt;I am not sure what is the intent of the health rule, if it is to check at what times the app went down then you can use the following.&lt;/P&gt;
&lt;P&gt;Overall Application Performance &amp;gt; Agent &amp;gt; App &amp;gt; Availability,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;At the tier level, the value of the above metric is equal to total number of nodes reporting to the tier, at the node level, the value of the above metric will always be one.&lt;/P&gt;
&lt;P&gt;Perhaps you can use the sum of the metircs over a period of time and check against your threshold?&lt;/P&gt;

&lt;P&gt;To your original question, i dont think number of restarts is saved any where.&lt;/P&gt;
&lt;P&gt;May be you can write a shell script to find that out on your server and then use extensions to report that value as a custom metric?&lt;/P&gt;

&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Gurmit.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2017 03:02:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Health-rule-based-on-application-changes/m-p/721366#M2562</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2017-07-21T03:02:32Z</dc:date>
    </item>
    <item>
      <title>Re: Health rule based on application changes</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Health-rule-based-on-application-changes/m-p/721367#M2563</link>
      <description>&lt;P&gt;Hi Gurmit,&lt;/P&gt;

&lt;P&gt;The intent of the rule is to easily detect if an application is recycling&amp;nbsp;frequently, as this may indicate that a private memory limit for instance, is exceeded easily. I suppose checking the availabilty of a tier could also cover this in some way. I will try this&amp;nbsp;first. Thanks for the quick reply!&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;

&lt;P&gt;Simon&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2017 09:18:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Health-rule-based-on-application-changes/m-p/721367#M2563</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2017-07-21T09:18:39Z</dc:date>
    </item>
  </channel>
</rss>

