Set up, configure or install RDS Database

[CommunityUser]

Hi everyone,

We have a set of servers in Amazon Web Services that we are trying to monitor using AppDynamics, and we are trying to monitor an RDS instance (it's a MySQL DB). Using the

next URL's steps we are unable to connect from AppDynamics Database service against RDS instance in Amazon side. After adding a new collector for the Databases service in AppDynamics we always get a "The agent is currently not reporting any data" error.

Configuration info when adding collector is OK (we have checked several times).

We have also seen another URL in which you have to install an extension, but as procedure is different as the previous one, and it seems to be a bit confussing about, i.e., where to install the extension, we haven't try it.

My question is really simple, we need to configure the collector against an RDS instance. How exactly should I do?

Thanks in advance!

[Arun_Dasetty]

Hi David,

Going the error message "The agent is currently not reporting any data" error. It looks you have installed DB agent that is part of appdynamics controller https://docs.appdynamics.com/display/PRO42/Database+Monitoring and the supported environments for DB Monitoring is below:

https://docs.appdynamics.com/display/PRO42/Database+Monitoring+Requirements+and+Supported+Environmen...

However, the forum link https://blog.appdynamics.com/database/how-to-set-up-and-monitor-amazon-rds-databases/ you have referred is suggesting to configure collector in AD4DB UI refer https://docs.appdynamics.com/display/ADDB/Install+AppDynamics+for+Databases not contorller UI and for this we do not need to run any separate dbagent.jar process as such

And the other link https://www.appdynamics.com/community/exchange/extension/aws-rds-monitoring-extension/ is need to configured by dropping monitor under monitors folder of machine agent and this will be monitored as extension custom metrics in controller metric browser, this is not AD4DB:

https://docs.appdynamics.com/display/PRO42/Install+the+Standalone+Machine+Agent

Let us know if above information clarifies the process.

Can you attach agent.log under <DBAgent_install_dir>/logs path and also screenshot of collector config in edit view and screenshot showing error in Controller UI, if any disconnect still.

Check if you have configured the collector name and rest of args as per docs and start dbagent.jar as per docs:

https://docs.appdynamics.com/display/PRO42/Database+Agent+Configuration+Properties

Regards,

Arun

[CommunityUser]

Hi Arun,

First of all, thank you so much for your time and explanation.

Maybe we're doing wrong the process. The truth is that I (we) never did this before. We want to configure AppDynamics in an Amazon RDS MySQL instance. Amazon does not let you install anything on DB, so no DB agent is installed. This means that no DB_agent can be started and no DB_agent logs are available, so we won't be able to attach any agent.log.

What we have done, so far, is to configure the MySQL RDS instance in Amazon side. It is done to use a DB in a cloud environment in Amazon AWS, to ease management and throughput issues in AWS (but I'm sure you also know this). It doesn't matter if you will be using AppDynamics later or not...

After that, in AppDynamics Controller, we acceeded Databases menu and added a new Collector. We have to add that we didn't see such UI that is shown in "Step 1" from section "Monitor Your Database With AppD4DB" in https://blog.appdynamics.com/database/how-to-set-up-and-monitor-amazon-rds-databases/ (We understand that this AppD4DB design is only a matter of UI). We have to add, also, that we have never seen any AppD4DB reference anywhere inside the Controller.

Anyway, to avoid confusing ourselves, what about if we start again from the beginning? We have the RDS MySQL instance configured, no possibility to install any DB_agent... next step?

Once more, thank you.

BR,

David.