Adding Controller

[CommunityUser]

Hey,
I have a customer that has 3 environments in his company.
He installed part of the first environment, and already has 200BT (he haven't installed all the agents yet).
Now he want to add the rest of the agents, but he can't because he passed the BT limitation.
Can he expand his controller? or add another one to the same application?  
And what should he do with the other two environments? Should it be on the same controller? (PROD, TEST, DEV)

Any answer will be appreciated.
Thanks,

Adi

[Arun_Dasetty]

Hi Adi,

We do not recommend increasing BT limit on either agent end (50 by default per agent node) and 200 per application, Listed though for reference for steps to increase below, we request you to check following doc links and see if you can group BTs using custom rules and exlude unnecassary BTs and also disable auto discovery of entry points under Configure -> Instrumentation -> transaction detection screen, that you are not interested in.

https://docs.appdynamics.com/display/PRO39/All+Other+Traffic+Business+Transaction

https://docs.appdynamics.com/display/PRO39/Organizing+Traffic+as+Business+Transactions

https://docs.appdynamics.com/display/PRO39/Configure+Business+Transaction+Detection

To answer your other query. if agent nodes under Prod, Dev, Test environments should be part of same app dashboard flow that you should associate agents under them as different tiers under same app, but it looks you have same jvms(jvm with same webapps) under Prod , Dev, Test if this is the case we request you to configure agents under Prod as separate application and agents under Test as separate app Hope that answers your queries.

Steps to increase BT limit at agent and controller level for reference:

1) Increase the agent node level property max-business-transactions whose default value is 50

Please find the below link to update node property
https://docs.appdynamics.com/display/PRO39/App+Agent+Node+Properties#AppAgentNodeProperties-Toeditar...

2) For controller, this can be increased by adding below JVM option in domain.xml at path <controller-install>/appserver/glassfish/domains/domain1/config/

<config name="server-config">
<java-config..

add below jvm option at the end of the other jvm options already present..
<jvm-options>-Dmaximum.bts.per.application=<MAX-BT></jvm-options>
replace <MAX-BT> with number such as 250 or 300 (default value is 200)

Ex:
<jvm-options>-Dmaximum.bts.per.application=300></jvm-options>

Please stop controller appserver before you update domain.xml and save the changes and restart appserver, better you use the utility https://docs.appdynamics.com/display/PRO39/Modify+GlassFish+JVM+Options to update jvm args :

1) Stop controller app server only
- <controller-install>/bin $./controller.sh stop-appserver
2) APPLY the domain.xml changes as suggested above.
3) Start controller appserver.
- <controller-install>/bin $./controller.sh start-appserver

Let us know if that information helps.

Regards,

Arun

[CommunityUser]

Hey Arun,
First off all - thank you for your answer. It's very detailed and helpful.
I'm new SE at AppDynamics and I heard from my customer that AppDynamics has different size for controllers - Small, Medium and Large. Is it true? and if so - how can I know what size of controller my customer has? what are the differences between those controllers? 

Thank you,
Adi

[Arun_Dasetty]

Hi Adi,

If i am not wrong you are referring to performance profile and you can profile installed for current controller under the following file <Controller_install_dir>/.install4j/response.varfile and search performance.profile string in install.log under <Controller_install_dir> as well.

Please refer doc for more info: https://docs.appdynamics.com/display/PRO39/Controller+System+Requirements

Hope that information helps.

Regards,

Arun