2868 is the total number of transactions that have registered for this Controller Application. Out of 2868, 185 transactions are receiving traffic at the point when the screenshot was taken. If you uncheck the "Transactions with Performance Data" checkbox you will see rest of transactions.  The reason we see so many transactions instead of 200 + All Other Traffic Bts can be attributed to two reasons 1) The BT limit has been increased at the Controller 2) There are literally (2685 - 200 = ) 2485 unique tiers registered under this Controller Application ... View more

Few of the BTs should have names like "All Other Traffic - <Tier Name>. These are the All Other traffic BTs belonging to different tiers which might have pushed the count to 207.  Thanks, Raunak ... View more

Hi José.Alves,   PHP Agent does not monitor PHP applications in Zend Thread Safety (ZTS) mode. If you are using ZTS, AppDynamics suggests that you review your dependencies on ZTS to confirm that you actually need it and if you do not, to switch to non-ZTS mode.  The PHP Agent is not compatible with Zend Monitor Thanks, Raunak ... View more

The error in the logs suggests that you have not provided proxy authentication information or the provided info is not correct. Can you please double check with your Network Team? If you have access to the support system, please create a ticket directly.  Otherwise, let us know so that we can share a SFTP location to get the logs from you. Thanks, Raunak ... View more

Please do not share the config file here as this community platform. As Satyam suggested please modify the config.xml to include <proxy host="myproxy.example.com"port="3128"enabled="true"> <authentication enabled="true"user_name="MyProxyUser"password="password"domain="mydomain.com"/> </proxy> Thanks, Raunak  ... View more

Hi Anant,   This means that Agent is not able to connect with Controller. Try running Agent Configuration Tool and verify if you are able to successfully establish a connection. Try accessing the Controller URL on the same server. Thanks, Raunak ... View more

Please try restarting the server. Sounds like a registry cache issue which should get sorted out after the restart. Thanks, Raunak ... View more

The following guide explains how AppDynamics detects Business Transactions and what you can do if AppDynamics doesn't recognize your application's Business Transactions out of the box. How does AppDynamics detect new Business Transactions? AppDynamics detects new Business Transactions by recognizing a particular set of "entry" methods in the callstack of the executing application. When one of these methods is hit, a new Business Transaction starts and all methods executing downstream of this method are instrumented. No Business Transactions were detected in my application, now what? In cases where no recognized Business Transaction entry methods are hit, we can enable the agent node property named find-entry-points to find some. With find-entry-points enabled, AppDynamics will log a call stack to  BusinessTransaction.log each time a recognized outgoing call is made. For example, any HTTP/ASMX/WCF/Remoting service, DB, or MQ call. You can find the BusinessTransactions.log in the agent logs folder. We can then review these callstacks to determine which method will make a suitable "entry" point to begin a Business Transaction. Callstack example shows what code is running in the application The following callstack is an example of what we might find in the BusinessTransactions.log after enabling find-entry-points. It should be read from the bottom up. That is, methods furthest down executed first. Look for callstacks following  Thread Empty_Name >>  which means they are not part of any existing BT. ... BusinessTransactions Logging request stack for Thread Empty_Name >>AppDynamics.Agent.ManagedAPI.ps.kk AppDynamics.Agent.Interceptors.ww.jv AppDynamics.Agent.MethodExecutionEnv.MethodBegin System.Data.SqlClient.ExecuteReader() <---AppDynamics recognized this as an exit and logged the callstack. MyCompany.MyClass.DataAccess.FindCustomerData() MyCompany.MyClass.BusinessLogic.TransformCustomerData() MyCompany.MyClass.UI.btnFindCustomerData_OnClick() System.Windows.Forms.Button.OnClick() System.Windows.Form.ButtonBase.WindProc(...) System.Windows.Forms.NativeWindow.Callback(...) We can see that this is a Windows Forms application where a particular button was clicked to find customer data. Once that button was clicked, an outgoing database call was made which AppDynamics recognized. From this point, AppDynaimcs code was executed to log the callstack to the BusinessTransaction.log file. Which application method would make a good Business Transaction entry point? Remember, methods executed first are at the bottom of the callstack. Looking at methods that executed before the database call, we can see that MyCompany.MyClass.UI.btnFindCustomerData_OnClick() is a custom developed code that would make a suitable starting point for this unique Business Transaction to begin. All methods which execute after this method are also tracked as part of this Business Transaction. If we use a method that executed before this one, for instance System.Windows.Forms.Button.OnClick(), every application button click would be tracked as part of the same business transaction, which is not ideal for troubleshooting. We want to make sure separate code paths are tracked as separate Business Transactions. OK I've found a suitable Business Transaction entry point method, now what? Once we've found a suitable BT entry point, we can configure a .NET Class/Method Custom Match Rule to let AppDynamics know that this method marks the start of a new Business Transaction. Once you've created the Custom Match Rule, you'll need to wait a minute or two for the rule to be brought down to the agent, then restart the application for the change to go into effect. Once in effect, you should see your Business Transaction show up in the controller. Just let us know if you have any further questions regarding this. Thanks, Raunak ... View more

That is correct. Thanks, Raunak ... View more

Hi Mohak, As you can see in your license file, you have only licenses available to use PHP and Python language agents, .net Agent are not able to connect and throwing errors property_no-of-python-app-agent-license-units=5 property_no-of-php-agent-license-units=5 startDate=1537182654624 property_mobile-license-allows-overages=false property_edition=ENTERPRISE_TRIAL property_transaction-analytics-volume-no-of-license-units=0 property_transaction-analytics-retention-period-no-of-license-units=90 property_no-of-machine-sim-license-units=0 property_eum-license-allows-overages=false property_eum-license-type=EUM_LITE What you need to do is connect with your Sales Rep/Account Manager so that .Net Agent trial licenses can be included as well. Or you can create a new query at the following area and someone from Licensing team will get in touch with you. https://community.appdynamics.com/t5/Licensing/bd-p/Licensing Thanks, Raunak ... View more

Hi Mohak, Can you send me the content of license file as a private message so that I can review it ? Thanks, Raunak ... View more

Hi, What is the value of Agent type you see in those alerts ? Do you have enough .Net Agent licenses ? Now regarding instrumenting standalone applications you will need to follow https://docs.appdynamics.com/display/PRO45/Configure+the+.NET+Agent+for+Windows+Services+and+Standalone+Applications Also you may not not see any BTS getting identified. For which you will need to create Custom Match Rules of type .Net Class/Method https://docs.appdynamics.com/display/PRO45/POCO+Entry+Points You can use Live Preview to identify appropriate Class/Method to create POCO on https://docs.appdynamics.com/display/PRO45/Custom+Match+Rule+Live+Preview Thanks, Raunak ... View more

Hi Lautaro, As of now we support instrumenting Linux based .Net Core applications via an SDK as explained here https://docs.appdynamics.com/display/PRO45/.NET+Core+for+Linux+SDK Thanks, Raunak ... View more

Hi ,   .Net Agent should capture most of async calls. Which patterns are supported OOTB and which need additional configurations are listed out here https://docs.appdynamics.com/display/PRO45/Thread+Correlation+for+.NET But MS Dynamic CRM is beast in itself you might need help our Professional Services team who can help you get maximum value out of AppDynamics. I will request you to connect with your Account Manager who can connect you to correct team who can help you out. Thanks, Raunak  ... View more

Hi Robert,   The container itself is Windows or Linux ? I am talking about the actual container host on which application is hosted. Thanks, Raunak ... View more

You don't have to manually add reference. I do not that mentioned as part of the documentation. Just make sure to set Copy Always to True for each of the Agent files/dlls and then just publish your application after creating necessary environment variables. BTs will get identified OOTB. On Windows, we support fully functional Agent. On Linux, we offer an SDK for now. Thanks, Raunak ... View more

Hi , .Net Agent can only instrument managed code which is .Net. I do not see an issue with creating Custom Instrumentation Points ( like Info Points, Data Collectors) etc on server side code as that is what .net Agent is instrumenting and collecting all the metrics from. Thanks, Raunak ... View more

Hi, What language is the application built on ? Is it Java app making Soap/MQ calls ? Thanks, Raunak ... View more

Hi Mervin,   Apologies for the delay. I will just try and explain it with sample cade. Assume you have code like this in your solution Namespace  Namespace SPSolution { Class SPClass { ...... ..... Public void AddItem(SPList list, CustomObject item) { ....... ....... } } } You can create Info Point like this Class: SPSolution.SPClass Method : AddItem Custom Metric Definition Collect Data from Method Param @index 0 Getter Chain: this.Items.Count SPList has Count property which we can use to get the current count. Thanks, Raunak ... View more

Hi Prodip, We are reviewing provided info and will get back to you. Thanks, Raunak ... View more

Hi Indarjit, Depends on what qualifies as API down. We have a number of options here. 1. If we have a Health page which gets invoked periodically then that BT can be used for Health Rule (HR) creation. If there are no calls ( BT metrics not reporting) then it can be a case that APIs are down. 2. We can also create HR on App Agent availability metrics. If availability is down then one of the case could be that the Process is down so Agent is not able to report metrics. But if API is up and for some reason Agent is not able to report any metrics it will lead to a false alarm. 3. If this is IIS hosted app then you will be using an AppPool to host this application which in turn will have a IIS Worker Process (w3wp) to serve the request. We can create HR on the following metric available at Metric Browser and see if the number of w3wps is equal to 0 which will mean w3wp is not running hence won't be able to serve requests Application Infrastructure Performance|<Tier Name>|IIS|Application Pools|<AppPool Name>|Number of working processes 4. If this is IIS hosted app then you will be using an AppPool which means you can check the status of AppPool itself. You can import the relevant Perfmon Counter using following doc and then create HR on it  https://docs.appdynamics.com/display/PRO45/Manage+Windows+Performance+Metrics Thanks, Raunak ... View more

Hi Mervin, Apologies for the delay here. I suppose you are using .Net Agent to instrument your SharePoint applications. I think we should be able to extract the value using Method Invocation Data Collectors or Info Point. https://docs.appdynamics.com/display/PRO45/Data+Collectors#DataCollectors-TypesofDataCollectors https://docs.appdynamics.com/display/PRO45/Information+Points We will need to identify the class and method and associated property which can be used to extract the length of items in a SPList. And once we have the current count we can create a Health Rule on the metric which will get fired when a certain threshold is breached. Thanks, Raunak ... View more

Hi Kevin, That is correct. You will install/configure Microservices Agent for each IIS App. Instead of creating System level environment variables you can defined the env variables directly at web.config like below <aspNetCore processPath="dotnet" arguments=".\Web.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout"> <environmentVariables> <environmentVariable name="CORECLR_PROFILER_PATH_64" value="C:\inetpub\wwwroot\NetCoreWeb\AppDynamics.Profiler_x64.dll" /> </environmentVariables> </aspNetCore> Thanks, Raunak ... View more