<?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: Events Service Unhealthy in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718440#M996</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/159831"&gt;@Salah.Tarek Khattab&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;I found this existing post where a member shared a similar error message. Can you check it out and let me know if it helps.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.appdynamics.com/t5/Java-Java-Agent-Installation-JVM/Event-Service-health-keeps-turning-critical/m-p/39882" target="_blank"&gt;https://community.appdynamics.com/t5/Java-Java-Agent-Installation-JVM/Event-Service-health-keeps-turning-critical/m-p/39882&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Oct 2022 20:25:00 GMT</pubDate>
    <dc:creator>iamryan</dc:creator>
    <dc:date>2022-10-26T20:25:00Z</dc:date>
    <item>
      <title>Events Service Unhealthy</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718437#M993</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I just started to implement a Cluster of 3 nodes of events service with a load balancer,&lt;BR /&gt;every node is started to be healthy and then unhealthy for two properties, and then go down&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;[Elasticsearch] unhealthy...retrying it the same error in every node and then go down&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;I tried to build this cluster on Windows Environment&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I tried to make a single node on the test environment also on windows,&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;and it's running successfully.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Oct 2022 23:23:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718437#M993</guid>
      <dc:creator>SalahKhattab</dc:creator>
      <dc:date>2022-10-24T23:23:07Z</dc:date>
    </item>
    <item>
      <title>Re: Events Service Unhealthy</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718438#M994</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/159831"&gt;@Salah.Tarek Khattab&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;What is the actual error you are getting? Can you share it as a reply?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 17:00:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718438#M994</guid>
      <dc:creator>iamryan</dc:creator>
      <dc:date>2022-10-25T17:00:15Z</dc:date>
    </item>
    <item>
      <title>Re: Events Service Unhealthy</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718439#M995</link>
      <description>&lt;P&gt;Hi Ryan,&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Error that I have is&amp;nbsp;&lt;/P&gt;&lt;P&gt;"events-service-api-store / Connection to ElasticSearch: clusterName=[appdynamics-events-service-cluster]" : {&lt;BR /&gt;"healthy" : false,&lt;BR /&gt;"message" : "None of the configured nodes are available: [{#transport#-1}{10.13.2.33}{10.13.2.33:9300}, {#transport#-2}{10.13.2.36}{10.13.2.36:9300}, {#transport#-3}{10.13.2.37}{10.13.2.37:9300}]",&lt;BR /&gt;"error" : {&lt;BR /&gt;"message" : "None of the configured nodes are available: [{#transport#-1}{10.13.2.33}{10.13.2.33:9300}, {#transport#-2}{10.13.2.36}{10.13.2.36:9300}, {#transport#-3}{10.13.2.37}{10.13.2.37:9300}]",&lt;BR /&gt;"stack" : [ "org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:290)", "org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:207)", "org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55)", "org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:288)", "org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:359)", "org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:348)", "org.elasticsearch.client.support.AbstractClient$ClusterAdmin.execute(AbstractClient.java:848)", "org.elasticsearch.client.support.AbstractClient$ClusterAdmin.nodesStats(AbstractClient.java:943)", "com.appdynamics.analytics.processor.elasticsearch.node.admin.ElasticSearchAdminFacade.getNodesStatsResponse(ElasticSearchAdminFacade.java:410)", "com.appdynamics.analytics.processor.elasticsearch.node.provider.ElasticSearchClientFacade.getNodesStatsResponse(ElasticSearchClientFacade.java:368)", "com.appdynamics.analytics.processor.elasticsearch.clusters.ClusterHealthStateReporter.isPartOfCluster(ClusterHealthStateReporter.java:120)", "com.appdynamics.analytics.processor.elasticsearch.clusters.ClusterHealthStateReporter.updateHistogram(ClusterHealthStateReporter.java:110)", "com.appdynamics.analytics.processor.elasticsearch.clusters.ClusterHealthStateReporter.updateHealthCheckResult(ClusterHealthStateReporter.java:99)", "com.appdynamics.common.util.health.AsynchronousHealthCheckable.runUpdateHealthCheckResult(AsynchronousHealthCheckable.java:122)", "com.appdynamics.common.util.health.AsynchronousHealthCheckable.access$100(AsynchronousHealthCheckable.java:46)", "com.appdynamics.common.util.health.AsynchronousHealthCheckable$2.run(AsynchronousHealthCheckable.java:146)", "java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)", "java.util.concurrent.FutureTask.runAndReset(Unknown Source)", "java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)", "java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)", "java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)", "java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)", "java.lang.Thread.run(Unknown Source)" ]&lt;BR /&gt;}&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 06:02:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718439#M995</guid>
      <dc:creator>SalahKhattab</dc:creator>
      <dc:date>2022-10-26T06:02:24Z</dc:date>
    </item>
    <item>
      <title>Re: Events Service Unhealthy</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718440#M996</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/159831"&gt;@Salah.Tarek Khattab&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;I found this existing post where a member shared a similar error message. Can you check it out and let me know if it helps.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.appdynamics.com/t5/Java-Java-Agent-Installation-JVM/Event-Service-health-keeps-turning-critical/m-p/39882" target="_blank"&gt;https://community.appdynamics.com/t5/Java-Java-Agent-Installation-JVM/Event-Service-health-keeps-turning-critical/m-p/39882&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 20:25:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718440#M996</guid>
      <dc:creator>iamryan</dc:creator>
      <dc:date>2022-10-26T20:25:00Z</dc:date>
    </item>
    <item>
      <title>Re: Events Service Unhealthy</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718441#M997</link>
      <description>&lt;P&gt;there is no solution in this link,&lt;/P&gt;&lt;P&gt;it's only a question&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2022 05:58:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718441#M997</guid>
      <dc:creator>SalahKhattab</dc:creator>
      <dc:date>2022-10-27T05:58:27Z</dc:date>
    </item>
    <item>
      <title>Re: Events Service Unhealthy</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718442#M998</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/159831"&gt;@Salah.Tarek Khattab&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;"we should scale up the events service as long as we run it as a single node especially in the dev &amp;amp; test environment however it's recommended to use a cluster of multi-nodes in a production environment&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.appdynamics.com/display/PRO21/Events+Service+Deployment" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/display/PRO21/Events+Service+Deployment&lt;/A&gt;"&lt;/P&gt;</description>
      <pubDate>Thu, 27 Oct 2022 16:10:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Events-Service-Unhealthy/m-p/718442#M998</guid>
      <dc:creator>iamryan</dc:creator>
      <dc:date>2022-10-27T16:10:39Z</dc:date>
    </item>
  </channel>
</rss>

