About Ranjith_Kumarka

Ranjith_Kumarka · ‎04-04-2024

Hi Amit, I'm not sure about the issue, but I suggest trying to reinstall with the latest agent version. Also, check the connectivity and SSL certification if required. Make sure that the hostname is correctly set in the server section to ensure all metrics are present.

Ranjith_Kumarka · ‎04-04-2024

Hi Rohit, Could you please perform the following checks: 1) Verify the connection between the database agent and the controller, as well as between the database agent and the database server. 2) Ensure that the user has the correct permissions as specified in the AppDynamics document. https://docs.appdynamics.com/appd/onprem/23.x/23.2/ja/database-visibility/add-database-collectors/configure-mysql-collectors 3) Check if you have created a user for the db collector setting. Try logging in with the same user on the MySQL server to confirm that the user ID and password are correct. Thank you.

Ranjith_Kumarka · ‎06-02-2023

We are now monitoring MS SQL database instances that have numerous schema, however our requirement is to simply monitor the performance of a single schema. I submitted a request at the help site for that, and I got the below response. Problem statement: Wanted to monitor only dB instead of complete MSSQL dB server Next steps: By default, agent will monitor all dBs in the MySQL server instance. The option available to restrict not to monitor certain databases are available. For this you need to exclude unwanted databases using "Exclude Databases" option in collector configuration. Refer: https://docs.appdynamics.com/appd/23.x/latest/en/database-visibility/add-database-collectors/configure-microsoft-sql-server-collectors and look for "Exclude Databases" option. However, omitting the database is not a solution because doing so will make it harder to monitor the remaining databases. Please give us your suggestions so we can solve this problem more quickly.

Ranjith_Kumarka · ‎12-06-2022

Hi All, Our Windows servers have the Windows Machine Agent installed. Version -22.9 of the machine agent Microsoft Windows servers, 2016 After installation, we noted the following points. 1) The WmiPrvSE process consumes more than 50% of the CPU. 2) The agent is automatically rebooting. 3) The MA is steadily using more memory. Please provide input to help resolve the existing problems.

Ranjith_Kumarka · ‎10-19-2022

Hi @Rao.Srinivasa , If you have previously dB agent installed in your environment, then no need to install new dB agent. Because one dB agent can monitor up to 200 database instance. So you just add the new database details in AppDynamics collector .

Ranjith_Kumarka · ‎10-14-2022

Hi @aman.nagle I am writing below step's for you but don't known it will works for you or not. You just install a machine agent on your servers as a Linux service . And create a health rule and policies for MA availability, Once the server stop/start it will send you a notification. Thanks Ranjit kumar

Ranjith_Kumarka · ‎10-14-2022

@aditya.mittal To monitor windows services status first install machine agent on that server. after installation use windows service extension to monitor your services PFB link for more deatils https://community.appdynamics.com/t5/Controller-SaaS-On-Premises/Windows-Service-Monitoring-Extension-Metrics-fluctuating-for-few/td-p/46717 Thanks Ranjit kumar

Ranjith_Kumarka · ‎10-14-2022

@Avinash.Isukaleti Can you attach here the log file to check the issue . Thanks Ranjit kumar

Ranjith_Kumarka · ‎10-14-2022

Hi @Rao.Srinivasa Can you confirm for me the below point? 1) Do You want to install a new DB agent on that windows server ?? Or 2) We want to add a collector through that DB agent.

Ranjith_Kumarka · ‎10-04-2022

Hi Srinivas, If you want to replace the new node with existing node then you may lose the previous data on the same node. So better to create a new node under the same Tier . If you don't care about your data, Then do the below steps to replace the existing with new node. 1) Open your server and navigate to the Appdynamics Agent folder-> version->Conf 2)Open the controller-info.xml file and edit the below parameter with new details and restart the application to apply the changes. <controller-info> <controller-host>192.168.1.20</controller-host> <controller-port>8090</controller-port> <application-name>ACMEOnline</application-name> <tier-name>InventoryTier</tier-name> <node-name>Inventory1</node-name> </controller-info> Thanks Ranjit Kumar

Posts	12
Solutions	1
Karma Given	0
Karma Received	5
Member Since	‎04-04-2022

Online Status	Offline
Date Last Visited	4 weeks ago

Need to monitor single schema of a dB instance

Windows machine is not working properly

Re: Help with Machine Agent error

Re: Appdynamics DB collector Issues

Need to monitor single schema of a dB instance

Windows machine is not working properly

Re: Appdynamics components installation on new dat...

Re: How to set up an alert for a server reboot?

Re: Monitoring and alerting Windows service status

Re: URL Monitoring Extension Crashing intermittent...

Re: Appdynamics components installation on new dat...

Re: Replacing existing nodes with new nodes