<?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: .Net Application issue in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Net-Application-issue/m-p/730649#M7216</link>
    <description>&lt;P&gt;Hi Indrajitkumar,&lt;/P&gt;

&lt;P&gt;It seems like you created the health rule on Agent node availability metric and due to this reason when the nodes are down then the health rule is triggered. Can you please check if there is continuosu traffic on the nodes which are showing down? If not then please generate continuous traffic on them and check if the App Agent status showing up.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Venu.&lt;/P&gt;</description>
    <pubDate>Wed, 14 Feb 2018 09:40:31 GMT</pubDate>
    <dc:creator>Venu_Babu_Thang</dc:creator>
    <dc:date>2018-02-14T09:40:31Z</dc:date>
    <item>
      <title>.Net Application issue</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Net-Application-issue/m-p/730648#M7215</link>
      <description>&lt;P&gt;I am stuck with my hosted .net application it was working fine, from other day i am unable to receive emails as configure and i even tried to restart the AppDynamics.Agent.Coordinator and even done IIS reset but still dont know what what had happened the Node Health is red and when i checked Tiers and Nodes for the same app heath is critical[red] and App Agent Status is down arrow, App Agent Version is 4.2.14.0.&lt;/P&gt;

&lt;P&gt;I even checked the Agent Log&lt;/P&gt;

&lt;P&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info ConfigurationChannel Account edition from controller = ENTERPRISE&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info ConfigurationChannel New account profile [AccountProfile [dataRetentionInMinutes=0, agentTypesSupported=null, automationEnabled=False, azureAutoScalingEnabled=False, systemsPanelEnabled=False, memoryMonitoringEnabled=False, startDateOfTrial=1/1/0001 12:00:00 AM, endDateOfTrial=1/1/0001 12:00:00 AM, businessTransactionLimit=50, nodeLimit=0, transactionCorrelationEnabled=False, snapshotsEnabled=False, snapshotsWithFullCallGraphsEnabled=False, automaticSnapshotsForSlowAndErrorRequestsEnabled=False, sqlDiagnosticsEnabled=False, hardwareMonitoringEnabled=False, jvmMonitoringEnabled=False, clrMonitoringEnabled=False, endUserExperienceMonitoringEnabled=False, backendDetectionEnabled=False, errorMonitoringEnabled=False, customDashboardsEnabled=False, reportingEnabled=False, baselinesEnabled=False, advancedAnalysisEnabled=False, policiesEnabled=False, alertingEnabled=False, informationPointsEnabled=True, topCallsEnabled=False, problemsEnabled=False, informationalEventsEnabled=False, metricBrowserEnabled=False, timestamp=1509485010310, dataCollectorsEnabled=True, customExitPointsEnabled=True, restAPIEnabled=False, maxApplications=0, maxPolicies=0, edition=ENTERPRISE, controllerBusinessTransactionLimitPerApplication=0]]&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info ConfigurationChannel Business transaction limit set to 50&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info ConfigurationChannel Controller version [4.3.8]&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info AgentConfigWatchdog Received properties from controller, going to refresh.&lt;/P&gt;
&lt;P&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info AgentConfigWatchdog ************ Started applying service properties from controller ***************&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info ApplicationStartupPolicy Setting 'enable-startup-snapshot-policy' with value 'false'&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info CallGraphConfigHandler Call Graph Config Changed callgraph-granularity-in-ms Value -0&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info CallGraphConfigHandler Call Graph Config Changed show-packages Value -&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info CallGraphFilteringConfig Setting Callgraph package LOCAL always show []&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info CallGraphConfigHandler Call Graph Config Changed dont-show-packages Value -&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info CallGraphFilteringConfig Setting Callgraph package LOCAL excludes []&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionSnapshotService Reset min-duration-for-jdbc-call-in-ms with new value 10&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionSnapshotService Reset max-jdbc-calls-per-callgraph with new value 100&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionSnapshotService Reset max-jdbc-calls-per-snapshot with new value 500&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionSnapshotService Reset adaptive-callgraph-granularity with new value false&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionMonitor Applying 'enable-transaction-correlation', 'true'&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionMonitor Applying 'enable-soap-header-correlation', 'false'&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info JDBCConfiguration Applying property capture-raw-sql, val false&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info ExitCallMonitoringConfiguration Received property update for [disable-exit-call-metrics-for], value[]&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info ExitCallMonitoringConfiguration Received property update for [disable-exit-call-correlation-for], value[]&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info ExitPointRuleApplier ExitPointRuleApplier property disable-custom-exit-points-for value []&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionMonitor Applying 'max-business-transactions', '50'&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info BusinessTransactionRegistry Max transactions set to 50&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionMonitor Agent will identify a maximum of [50] business transactions.&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionMonitor Applying 'min-load-per-minute-diagnostic-session-trigger', '10'&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionMonitor Minimum load per min on a BT to trigger diagnostic session on agent [10] requests.&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info TransactionMonitor Applying 'slow-request-threshold', '500'&lt;BR /&gt;2018-02-08 05:15:29.5660 11116 w3wp 4 4 Info SlowAndStallRequestMonitor Slow Request checker setup to check for requests slower than 500 ms, at interval 500 ms.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Feb 2018 11:27:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Net-Application-issue/m-p/730648#M7215</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2018-02-08T11:27:12Z</dc:date>
    </item>
    <item>
      <title>Re: .Net Application issue</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Net-Application-issue/m-p/730649#M7216</link>
      <description>&lt;P&gt;Hi Indrajitkumar,&lt;/P&gt;

&lt;P&gt;It seems like you created the health rule on Agent node availability metric and due to this reason when the nodes are down then the health rule is triggered. Can you please check if there is continuosu traffic on the nodes which are showing down? If not then please generate continuous traffic on them and check if the App Agent status showing up.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Venu.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2018 09:40:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Net-Application-issue/m-p/730649#M7216</guid>
      <dc:creator>Venu_Babu_Thang</dc:creator>
      <dc:date>2018-02-14T09:40:31Z</dc:date>
    </item>
    <item>
      <title>Re: .Net Application issue</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Net-Application-issue/m-p/730650#M7217</link>
      <description>&lt;P&gt;Venu,&lt;/P&gt;

&lt;P&gt;You are correct I have created some Health rules and Policies too, and based on that&amp;nbsp;I used to receive emails, but somehow I can't figure out how now not receiving emails for any of the health rules, and yes nodes have traffic, and I even checked Events in Application Dashboard there what i can see is emails are getting triggered but its failed with the error that says " Policy notification emails to [email address] failed to be sent through smtp.office365.com:port"&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Indrajit&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2018 10:07:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Net-Application-issue/m-p/730650#M7217</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2018-02-14T10:07:26Z</dc:date>
    </item>
    <item>
      <title>Re: .Net Application issue</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Net-Application-issue/m-p/730651#M7218</link>
      <description>&lt;P&gt;According to the docs:&lt;/P&gt;

&lt;P&gt;If you do not receive notifications for health rule violations, it could be because the default SMTP server timeout period is too short. To troubleshoot,&amp;nbsp;&lt;SPAN&gt;increase the value of the&lt;/SPAN&gt;&amp;nbsp;mail.smtp.socketiotimeout Controller Setting in the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://docs.appdynamics.com/display/PRO42/Access+the+Administration+Console" target="_blank" rel="nofollow noopener noreferrer"&gt;Administration Console&lt;/A&gt;. The&amp;nbsp;default value is 30 seconds.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Feb 2018 15:12:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Net-Application-issue/m-p/730651#M7218</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2018-02-14T15:12:44Z</dc:date>
    </item>
  </channel>
</rss>

