<?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: License limitation in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/License-limitation/m-p/724063#M4034</link>
    <description>&lt;P&gt;Hi Gary.Sun,&lt;/P&gt;

&lt;P&gt;looking at&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.appdynamics.com/display/PRO45/Historical+and+Disconnected+Nodes#HistoricalandDisconnectedNodes-NodeActivityandAgentLicensing)%C2%A0" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/display/PRO45/Historical+and+Disconnected+Nodes#HistoricalandDisconnectedNodes-NodeActivityandAgentLicensing)%C2%A0&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;the behaviour should be the following:&lt;/P&gt;

&lt;P&gt;"&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;For licensing purposes, the Controller releases the license for the agent if the Controller has not received data from the agent in the previous 5 minutes. This license availability behavior is not affected by the historical node status or node deletion timeout settings.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;"&lt;/P&gt;

&lt;P&gt;So I guess you could just block the connection from the agents you don't want to have monitored anymore for at least 5 minutes or as you said restart the application without the agent.&lt;/P&gt;

&lt;P&gt;Philipp&lt;/P&gt;</description>
    <pubDate>Fri, 17 Aug 2018 09:10:37 GMT</pubDate>
    <dc:creator>CommunityUser</dc:creator>
    <dc:date>2018-08-17T09:10:37Z</dc:date>
    <item>
      <title>License limitation</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/License-limitation/m-p/724062#M4033</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I'm new to here and have a question about license.&lt;/P&gt;
&lt;P&gt;My customer is planning to purchase 40 licenses for their Java application servers.&lt;/P&gt;
&lt;P&gt;Actually, they have over 40 servers in their production environment. It's around 60.&lt;/P&gt;

&lt;P&gt;As far as I know, I can install Java agent to all of the servers but Appdynamics controller will accept connection&amp;nbsp;for 40 servers only.&lt;/P&gt;

&lt;P&gt;If I need to see performance metric data which reside in the rest of 20 servers, do I have to remove the agent setting and restart 20 servers which already registered to&amp;nbsp;&lt;SPAN&gt;Appdynamics&amp;nbsp;&lt;/SPAN&gt;controller for accepting new server's registration?&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 16 Aug 2018 06:12:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/License-limitation/m-p/724062#M4033</guid>
      <dc:creator>Gary_Sun</dc:creator>
      <dc:date>2018-08-16T06:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: License limitation</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/License-limitation/m-p/724063#M4034</link>
      <description>&lt;P&gt;Hi Gary.Sun,&lt;/P&gt;

&lt;P&gt;looking at&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.appdynamics.com/display/PRO45/Historical+and+Disconnected+Nodes#HistoricalandDisconnectedNodes-NodeActivityandAgentLicensing)%C2%A0" target="_blank" rel="nofollow noopener noreferrer"&gt;https://docs.appdynamics.com/display/PRO45/Historical+and+Disconnected+Nodes#HistoricalandDisconnectedNodes-NodeActivityandAgentLicensing)%C2%A0&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;the behaviour should be the following:&lt;/P&gt;

&lt;P&gt;"&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;For licensing purposes, the Controller releases the license for the agent if the Controller has not received data from the agent in the previous 5 minutes. This license availability behavior is not affected by the historical node status or node deletion timeout settings.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;"&lt;/P&gt;

&lt;P&gt;So I guess you could just block the connection from the agents you don't want to have monitored anymore for at least 5 minutes or as you said restart the application without the agent.&lt;/P&gt;

&lt;P&gt;Philipp&lt;/P&gt;</description>
      <pubDate>Fri, 17 Aug 2018 09:10:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/License-limitation/m-p/724063#M4034</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2018-08-17T09:10:37Z</dc:date>
    </item>
    <item>
      <title>Re: License limitation</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/License-limitation/m-p/724064#M4035</link>
      <description>Hi Philipp,&lt;BR /&gt;Thanks for your helpful information. I have another question extend from your reply.&lt;BR /&gt;&lt;BR /&gt;To block the connection from specified agent, Is there a UI interface to do it or I have to do it from network layer by command?&lt;BR /&gt;&lt;BR /&gt;Regards,</description>
      <pubDate>Mon, 20 Aug 2018 05:06:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/License-limitation/m-p/724064#M4035</guid>
      <dc:creator>Gary_Sun</dc:creator>
      <dc:date>2018-08-20T05:06:50Z</dc:date>
    </item>
    <item>
      <title>Re: License limitation</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/License-limitation/m-p/724065#M4036</link>
      <description>Hi, you would have to do this from your network layer.&lt;BR /&gt;Philipp</description>
      <pubDate>Mon, 20 Aug 2018 07:12:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/License-limitation/m-p/724065#M4036</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2018-08-20T07:12:06Z</dc:date>
    </item>
  </channel>
</rss>

