@Gregory.Burkhead I was trying to find this answer as well, and came across your post. I found this article on docs, that may help.  https://docs.appdynamics.com/appd/23.x/latest/en/analytics/configure-analytics/collect-transaction-analytics-data What concerns me is that you mentioned turning off "Enable Analytics for New Applications." That sliding button should turn that off for new apps and all BTs except All Other Traffic. If that is the situation, there appears to be a bug, which would require support.  ... View more

@Dawid.Wrobel  Correct...AppDynamics, by default, will create a snapshot every 10 minutes, and they capture a 10-second window unless they are in what is called a diagnostic session.  The UI can be used as you mentioned to change the frequency, but I must have misunderstood your question. I assumed you wanted to change the time period for what is captured...rather than the frequency.  If you feel there is a need to take more frequent snapshots, I would ask what that reason is, and from my experiences, that change happens when there are systemic issues happening and the default rules don't do a good enough job capturing what is needed for troubleshooting, therefore, I suggest creating a manual diagnostic session rather than changing those types of global settings.  If no paper icon is available, meaning, there is no partial or full call graph, it just means a snapshot was created without there being a slow, very slow, or error that will put the transaction into a diagnostic session. It can almost be considered normal operations or behavior. Call graphs, whether they are partial or full, generate due to a diagnostic session. AppD can create the diagnostic session or you can manually. If you look at the differences, you will see a partial call graph does get to the line causing a violation, but will not encompass the entire flow like when having a full call graph...which is very useful if you want to know what is effected or being caused by downstream or upstream transactions. If a transaction happens that deviates from a normal activity during the snapshot being captured, AppD will start a diagnostic session which will capture the method calls seen in a call graph. Depending on when that diagnostic session started, you may/may not get the whole transaction flow. If nothing deviates from what AppD thinks is normal, then there would be no reason a diagnostic session gets created, meaning a call graph wont be generated and that is when we wont see a paper icon. You can initiate a diagnostic session manually or via rules which will give you the control to capture when, for how long and how many snapshots per minute you want...which will surely get you the details you need.   I am happy to try and help some more if you have further questions.  ... View more

Here is the diagnostic session documentation link: https://docs.appdynamics.com/appd/23.x/latest/en/application-monitoring/business-transactions/troubleshoot-business-transaction-performance-with-transaction-snapshots/diagnostic-sessions ... View more

@Dawid.Wrobel I am not sure of how you can change the snapshotting...that is generally handled by support, or perhaps it is something you would have access to, but I cannot advise of that. The frequency that is default should be sufficient. I do get asked this question, especially around the fact that not all snapshots contain the call graphs which really make them valuable. The way I see it, there are enough snapshots that happen to account for providing the information you would need, without having to adjust those settings.  The fact that if there is a systemic issue, it will be captured as you need. If you need to, you can also initiate what we call a diagnostic session which will be providing much more at a more controlled fashion. Those sessions should only be used when there is an issue that is not being resolved by the systems snapshots, or, perhaps because the problem is not seen as sufficiently abnormal to our AI engine.  In summay...I would advise not changing the default settings, acknowledging your point about performance, and instead, leverage a diagnostic session just for a specific time frame.  I hope this helps... ... View more

I am sorry @Simon.Parish you hare having a hard time with this. Neither @Ryan.Paredez nor myself are experts when it comes to this topic, but we are here to try and help as best as we can. Have you see this doc which details how to create a client for API? We support OAuth standards... As for the details, I assumed you were using Infra based, as the agent does not provide the same level of details you seem to be after. There is no way around what is available, other than to create an idea which we can advocate with the product team on your behalf for a future enhancement. With infra, you can Retrieve Usage by Application ID and Retrieve by Application Name. ... View more

@Simon.Parish  What API reference document are you leveraging? From what I can see, licensing is not broken down by instances/nodes. Assuming you are talking about infrastructure based licensing, you can get the number and types of agents, and applications, but nothing deeper.  What is it that you are trying to achieve by getting going down to the node? ... View more

@Simon.Parish Are you familiar with setting up rules to understand account usage and only needing support for the second question around API?  For account usage, you can setup a rule with a set number of allowed units, to see who is consuming what. You can refer to our license doc on the subject for more info. As for the API part...I assume you can, though I have not personally tried, use something like Postman to leverage auth and variables as you would generally do. Can't see why you should have to clear text passwords but perhaps the docs were to make it easy for users who do not know how to leverage API tools. ... View more

@Ashley.Lewis  Good news then...Are you suggesting that all new applications automatically use that Health Rule? If so that would make a nice Idea request. If you submit that, please post it here and so I can follow up with the product team so they are aware of it.  ... View more

Thanks for the clarity @Ashley.Lewis .  I do not believe this would be possible at this time, but I am looking into this by connecting with a product manager who manages the Health Rules within our SaaS product. I will let you know more when I hear back from this person...I believe I will need to submit an enhancement request on your behalf, but will confirm this to be the case...if so, I will need to get a few more details from you I believe. I'll get back with you sometime next week regardless...thanks! Aaron CC: @Ryan.Paredez  ... View more

@Ashley.Lewis @Ryan.Paredez and I have been talking about this... Have you tried just modifying one of the built-in HRs that would then be applied to your settings? That could be the alternative to an otherwise enhancement request. I see the value of what I believe you are after...the ability to create the templates that all new applications would then be able to use, without having to create them after the fact.  ... View more

I also want to add some details here that I put together for a presentation some time ago... AppDynamics provides a method to account for variations in the normal operation of the overall application, various user experience areas such as browser or mobile applications as well as API monitoring…additionally, databases, servers, and analytics make up the scope of Health Rules. Baselines derived from AppDynamics Cognition Engine, feed into health rules… The types of health rules that can be configured are around: •Transaction performance metrics related to the load, i.e. response time, slow calls, stalls, errors, etc., •Node health such as the hardware, JVM, JMX, disk I/O… •User experience areas such as how they relate to pages, i.e. the DOM build time, digest cycles, load and execution time, AJAX requests, mobile app status changes, HTTP errors, and many other relevant performance metrics. •Additionally, types relating to hardware resources for servers, databases, service endpoints, and just a slew of others… ... View more

@Joel.Francois I would say that Health Rules are a way to customize your anomaly detection engine. We have a number of built-in HRs that you can use as-is or customize, depending on the type of entity you are looking to configure, on top of creating your own.  If a value for say, the response time between services, or hardware resource such as CPU goes beyond a threshold you configure, you can configure warnings and/or critical notifications and automated responses.  While baselines are automatically detected with the AppDynamics cognition engine, Health Rules are configured by the end user. Baselines will alert on deviations the system sees as anomalies, where as HRs will rely on the values being defined by you, or AppD if we are talking out-of-the-box health rules.  So the main points here are that you have control over which values are determined to mean an issue, or potential one, and having the ability to automate responses to those alerts...email, Jira ticket, PagerDuty notification, etc... ... View more

@Rahul.Gunasekaran This is a great document...hopefully it will help you identify the types of rules that apply to your needs. https://docs.appdynamics.com/appd/22.x/22.9/en/appdynamics-essentials/alert-and-respond/health-rules ... View more

@Hemanth.Kari  There is a need to install the Visual Studio C++ redistributable, in reference of the C++ Supported Platforms documentation, and you will also need to modify the source code, leveraging this reference document. There is no auto-instrumentation with the C++ SDK. You can also work with your sales representative about seeing if professional services is a viable option or leveraging an example we have internally. Thanks for the question, I hope it helps!  Aaron CC: @Claudia.Landivar for awareness... ... View more