MMS Automation Agents need create role on Mongodb ?

When I start the automation-agent , 

alway show Error .. " result={"code":13,"errmsg":"not authorized on admin to execute command "

should I need Create a role for Agent On MongoDB?

I don't know how to solve this issue , 

Take a look here:

https://docs.mms.mongodb.com/reference/required-access-monitoring-agent/

The answers are different depending on which version of MongoDB you are running, but that page covers all of them.

I have created user  , user name "mms-monitoring-agent" , user password "somePassword", 

role is "clusterMonitor"。

Is this right?

my mongodb version is 2.6。

because I don't know what is  monitor agent's user name .

please help me about this, thank you very much

It uses the username and password you created for it.

You need to fill it in the config file for the agent.

See the details here:

https://docs.mms.mongodb.com/reference/monitoring-agent/#mongodb-authentication-settings

should I fill it in which config?

monitoring-agent.config or automation-agent.config ?

because I can't find monitoring-agent.config in my system.

only automation-agent.config exist.

so, I need to add globalAuthUsername and  globalAuthPassword  in automation-agent.config ?

Is this right?

Automation Agent will download Monitoring-agent automatically right ?

but in my system , I can't find Monitoring-agent .

so, can I know which port that use for download monitoring-agent by automation-agent?

maybe my firewall block it.

thank you very much 

You configure the automation agent only.

It will take care of installing and running the other agents if necessary.

It sounds like you may be trying to run the Automation Agent on an existing MongoDB deployment. We do not support that at this time. If this is not the case, please let me know how you deployed your Automation Agent so we can try and address the issue.

I have a MongoDB now is running for my App . 

I can't run Automation Agent on my existing MongoDB  event if my MongoDB's version over 2.4?

Can you tell me what is [We do not support run the Automation Agent on an existing Mongodb deployment ]??

I need install Automation  Agent before install MongoDB ?

Or Can you tell me how can I use MMS on my existing MongoDB?

sorry about this , but I really can't understand .

The Automation Agent is for deploying new installations of MongoDB. At this time, it does not support "attaching" to existing MongoDB installations, although we are working on that to be released sometime next year. The MongoDB version is not relevant. This has been the case since early October when we released the new MMS. The only way to monitor existing MongoDB installations at this time is to have an older MMS Classic account, which does not feature Automation. You can tell you have an MMS Classic account as it will say "MMS Classic" on the top bar next to your group's name. There are no new MMS Classic accounts available. You can deploy a new MongoDB installation using the new MMS and then port your data over using mongodump and mongorestore.

I hope this clears some stuff up, but feel free to ask any questions you may have about this.

Thank you very much for your reply.

When I ask question about this to MongoDB's Agent in China , they told me MMS can manage existing MongoDB that version after 2.4.

ok,now I know where the problem is.