Which two symptoms occur if an AppDynamics Controller is NOT scaled correctly? (Choose two.)
According to the Cisco AppDynamics Professional Implementer (CAPI) documents, the two symptoms that occur if an AppDynamics Controller is not scaled correctly are:
The incorrect options are:
The average response times of tiers are higher than normal. This is not a valid symptom because the AppDynamics Controller does not affect the average response times of tiers. The average response time of a tier is the average time that the tier takes to process the incoming requests from the business transactions that are monitored by the AppDynamics platform. The average response time of a tier is influenced by the performance and behavior of the application code, the infrastructure, the dependencies, and the workload of the tier, not by the Controller itself. The average response time of a tier is not affected by the Controller scaling, unless the Controller fails to collect or process the metrics data .
1: Controller System Requirements - AppDynamics
2: Controller Sizing Guidelines - AppDynamics
3: Transaction Snapshots - AppDynamics
Instead of using the Enterprise Console Ul, how can an administrator import an existing keypair to manage the Controller SSL certificate?
A company set up an on-premises AppDynamics Controller and an on-premises Events Service cluster. What describes setting up this Events Service cluster?
Instead of using the Enterprise Console Ul, how can an administrator import an existing keypair to manage the Controller SSL certificate?
What are three valid reasons to use the AppDynamics REST API to retrieve metrics? (Choose three.)
To archive 1-minute granularity data. The AppDynamics Controller stores metric data at different levels of granularity depending on the retention period. For example, it stores 1-minute granularity data for 8 days, 10-minute granularity data for 32 days, and 1-hour granularity data for 365 days. If you want to archive the 1-minute granularity data for longer than 8 days, you can use the API to retrieve and store the data in an external database or file system.
To calculate a new metric based on two existing metrics. The AppDynamics Controller provides some built-in metrics such as average response time, calls per minute, errors per minute, etc. However, you may want to calculate a new metric that is not available in the Controller, such as the ratio of errors to calls, or the percentage of slow transactions. You can use the API to retrieve the values of the existing metrics and perform the calculation using your own logic or formula.
Currently there are no comments in this discussion, be the first to comment!