Hi @Tiong.Koh , I apologize for the delay in my response. I reviewed this limitation and found that an idea request was previously submitted regarding this, but, it was rejected due to concern of system performance. Additionally, the 32,767 character limit was deemed sufficient for SQL analysis at the time. Regarding the character limit, the current maximum is 32,767 characters, including white spaces. If this limitation is critical to your business processes, I recommend reaching out to your account manager or sales reps with business justification so that they can discuss with our product manager.   Regards, Martina ... View more

Hi Tiong.Koh, Thank you for posting to community. Could you clarify how many characters are currently being captured and how many characters you'd need to be shown? This will help in understanding the scope. From what I understand, the maximum character of query text shown is hardcoded to the maximum of 32,767 characters in database agent. We can’t change this setting, because, Increasing this limit might lead to higher memory consumption on the DB agent side and increased storage usage on the Controller side. ‌ Regards, Martina ... View more

Hi @‌Easwar.C, Thank you for posting to the community. Is your jar file being placed under the path :  JRE_HOME>/lib/ext  as indicated in perquisite for Object instance Tracking? Also, When using the JDK runtime environment, we need to set the classpath using the  -classpath option for the application. After these setting. restart the JVM. Moreover, it is worth to check whether the user that currently running the JVM has access to read the jar file. Cause this error could be triggered when permission denied. Hope this helps, Martina ... View more

Hi @Josua.Panjaitan , From the error “Unable to get AppAgentConfigurationResponse from controller“ given, it is worth to double check the controller information in controller-info.xml . Was the the controller info set correct? For example, check whether the  <controller-host> ,  <account-name> ,  <account-access-key>   are correct. There are other possible causes as well for this error it is hard to tell from the error statement only. However, it’s possible to gain closure on what happens in the process by checking the agent log.   Troubleshooting Java Agent Issues Hope this helps! Regards, Martina ... View more

Hi @Shashwat .Pandey , For the issue: Analytic-agent is not reporting, It looks like there are a few key areas to check in your configuration and setup for the Analytics Agent. Next Step: Check Python Agent Version: Ensure that your Python Agent version supports Analytics. It appears you are using Python Agent 21.5, but Transaction Analytics requires Python Agent version 21.10 or later. Versions earlier than 21.10 do not support Transaction Analytics. You can find more details here:   Deploy Analytics With the Analytics Agent Python Agent Configuration: Review the configuration for the Python Agent. For detailed setup instructions, refer to the following resources: check here to see on what to configure:   Configure Transaction Analytics for Node.js, PHP, and Python Applications Also, check here for Python Agent settings in detail:   Python Agent Settings Analysis on provided config file: > Checkpoint 1: In the  [services:analytics]  section of your  appdynamics.cfg , the  host  field should point to the hostname where the Analytics Agent is installed, not the service analytics connection endpoint. For most configurations, install the Analytics Agent on the same machine as the python agent. Example : => host = localhost > CheckPoint2: ・The  enabled  field is not required in this configuration. Configure analytics-agent.properties  : refer to url below and make sure if  analytics-agent.properties  is correctly configured. Key points to verify include: Controller information &  http.event.endpoint  value see: “Enable the Standalone Analytics Agent“   Install Agent-Side Components Lastly, make sure to enable Analytics for specific applications and business transactions you want to monitor. Configure Analytics Hope this helps. Regards, Martina ... View more

Hi Anup.Thatte I gathered some Appdynamics documentation that could help you with the uninstallation. See following documentation for detailed uninstallation steps for each agent 🙂 Uninstalling AppDynamics Machine Agent https://docs.appdynamics.com/appd/24.x/latest/en/infrastructure-visibility/machine-agent/administer-the-machine-agent/uninstall-the-machine-agent Uninstalling AppDynamics Java Agent https://docs.appdynamics.com/appd/22.x/22.12/en/application-monitoring/install-app-server-agents/java-agent/administer-the-java-agent/uninstall-the-java-agent Uninstalling AppDynamics ABAP App Agents and Datavard Transports/Now:SNP Crystal Bridge https://docs.appdynamics.com/sap/en/upgrade-or-uninstall-the-solution (see Uninstall the ABAP Agent and SNP CrystalBridge® Monitoring) Hope this helps. Regards, Martina ... View more

Hi @pavi.p ,  I have answered similar question on this post. Kindly check my answer below. it might help you to resolve your  issue. ：） https://community.appdynamics.com/t5/NET-Agent-Installation/Couldn-t-get-MSMQ-entry-point-for-NET-Consumer-Application/m-p/54299/highlight/true#M1619 Hope this helps. Regards,  Martina ... View more

Hello @Jonathan.Wang 、 To install demo profile controller, 50GB = 51200 MB Disk Space is required. Please make sure to allocate sufficient disk space. Or if you need to skip the disk space requirement, you can update the configuration file. Steps: Locate the Configuration File: For the demo profile controller, the file is likely in the path: platform/platform-admin/archives/controller/<ver>/playbooks/controller-demo.groovy Edit the Disk Space Property: Update the property ”controller_data_min_disk_space_in_mb" to a lower disk space number. For example: controller_data_min_disk_space_in_mb = 2000 * 1024 Note: This manual configuration is intended for test purposes only and may not be suitable for production environments. Additional Information: For more details on Controller system requirements and settings, please refer to the AppDynamics Documentation. Hope this helps. Regards, Martina ... View more

Hi @aina.rahman , Thank you for posting on community. To monitor the SQL Server and SQL Agent services and set up email alerts when they are down, you can follow these steps: Enable the Email Server if not yet set up.  steps to  Enable the Email Server Set up Related Health Rules, Policies, and Actions to Monitor Services for SQL Server Monitoring, utilize AppDynamics Database Agent: Install Database Agent Monitor Databases and Database Servers Steps: Set Health Rule: On Controller > Databases > Alert & Respond, configure a health rule. Use the metric DB|KPI|Database Availability to monitor whether the SQL Server is running.     Set Policies: Policies: On Controller > Alert & Respond > Policies, create a new policy. Set the Trigger, Health Rule Scope, and Actions. Add action and configure email to specify where to send alert emails.     By following these steps, I received email alerts when health rules are violated (SQL server down/SQL server stopped). for SQL Server Agent Monitoring, utilize AppDynamics Machine Agent. AppDynamics Machine Agent can monitor processes on server. Machine Agent Server Process Metrics Steps: Set up health rule, policy, and action similarly to the database agent above. Notes: When setting up the health rules, under Affected Entities, select Custom Health Rule Type to set process metrics such as memory usage or count in the Critical/Warning area. By following these steps, I received email alerts when the SQL Agent service is down. Other Monitoring Alternatives Below are some possible alternatives to monitor your windows services status: .NET Agent Extension .NET Agent extension to monitor windows services. Reference: .NET Agent Extension Documentation Write your own Machine Agent Extension Machine Agent for custom monitoring of services.　Reference: Machine Agent Documentation Hope this help. Regards, Martina ... View more

Hi @Arsenii.Shub , Thank you for posting on community. I saw you raised a support case already for this. Hence, I would like to share what was the solution, result of my experimentation, and additional information. Issue: The URLs shown in BT/Transaction Snapshots are incomplete. Goal: Differentiate slow search requests in the system caused by specific user input. Tests: I tested the URL behavior on a .NET MVC web app. Solutions: URL Display on URL Column: While it’s not possible to show the full URL with  http://host/ , we can display the URL as  /Search/userInput . Reference: https://docs.appdynamics.com/appd/23.x/latest/en/application-monitoring/configure-instrumentation/transaction-detection-rules/custom-match-rules/net-business-transaction-detection/name-mvc-transactions-by-area-controller-and-action#id-.NameMVCTransactionsbyArea,Controller,andActionv23.1-MVCTransactionNaming Complete URL Display on BT name Column: It is possible to display the complete URL  https://host/Search/userInput  in the BT name. Reference: https://docs.appdynamics.com/appd/23.x/latest/en/application-monitoring/configure-instrumentation/transaction-detection-rules/uri-based-entry-points Next Steps: For Partial URL in URL column  /Search/userInput : Add App Server Agent Configuration. Set the following .NET Agent Configuration properties to false: aspdotnet-core-naming-controlleraction aspdotnet-core-naming-controllerarea     Restart the  AppDynamics.Agent.Coordinator_service and IIS in the same sequence. After that, apply loads and check the BT/Snapshot if necessary. For Complete URL in BT name  https://host/Search/userInput : Navigate to Configuration > Instrumentation > Transaction Detection in your Application. Add New Rules: Choose  Include , proper Agent type, and Current Entry Point. Fill in the Name Field (it will be shown on your BT). Set Priority higher than Default Automatic detection for prioritization.     Rule Configuration: Matching condition:  URL is not empty Custom Expression: ${HttpRequest.Scheme}://${HttpRequest.Host}${HttpRequest.Path}${HttpRequest.QueryString} Restart the  AppDynamics.Agent.Coordinator_service  and  IIS in the same sequence. After that, apply loads and check the BT/Snapshot if necessary. Final Result: Additional Information: You can also add the custom expression by modifying the default Auto detection rule instead off Add new one like how I did in the step above. Result from modifying the default auto detection below.     ... View more

Hi @Anonymous , I recreated the issue you described and managed to have both the Sender and Receiver Application processes shown on my AppDynamics dashboard. I didn’t add the Message Queue entry points mentioned Above. But, I did these steps below to resolve the issue of Receiver info not being shown: Setting MSMQ Backends Monitoring for .NET: To enable downstream correlation for MSMQ, you must configure the agent. Documentation: MSMQ Backends for .NET. What to do: Go to “Tiers and Nodes” on Controller UI: Choose your Receiver Application Node. At the top right, select “Action” > “Configure App Server Agent”. Configure the App Server Agent: In the "App Server Agent Configuration" modal window, click on "Apps" from the tree on the right. Select “.NET Agent Configuration” on the right panel, then click on “+”. Define the MSMQ Correlation Field: Name:  msmq-correlation-field Description: Your description here Type: String Value: Label By following these steps, I was able to see the MQ details and transaction snapshots for both the sender and receiver applications in the AppDynamics controller. Hope this helps. Regards, Martina ... View more

Hello @Michael.Mom , Thanks for posting to the AppDynamics Community. Your Question: is it correct to assume that the best approach is to provision an EC2 instance (or AWS workspace) in my AWS environment with the appropriate VPC / RDS security group settings and install an agent? Brief Answer: not necessarily. We can avoid provisioning a new EC2 instance solely for this purpose. Analysis & Observations: The AppDynamics Database Agent can be run from any machine as long as it has network access to your RDS and the Controller. This means you can leverage any existing on-premises server or, for scalability, any pre-existing AWS EC2 instance, including your controller if applicable. But, it’s important to ensure that your chosen machine has the necessary network access. 1. Machine to RDS: Ensure the machine can communicate with the RDS over the necessary ports (default: 1433 for SQL Server). 2. Machine to Controller: If the machine and the controller are on different hosts, ensure the machine can access the controller over the internet. Step by step guide : Ensure Resource Requirements. ensure your machine has sufficient resources. Database Visibility System Requirements Ensure your SQL Server version is supported.   Database Visibility Supported Environments Install the Database Agent. Install the Database Agent Note: You can configure access to the controller using the controller-info.xml file. This can be found in the “Configure the Agent” section of the documentation above. Configure Database Collectors.  After installing the agent, you need to configure database collectors. Refer to the following documentation: Add Database Collectors Configure Microsoft SQL Server Collectors Database User Permissions.  Ensure that the database user has the appropriate permissions. For SQL Server on AWS RDS, refer to: Microsoft SQL Server on AWS RDS Permissions Hope this helps. Best Regards, Martina ... View more