processes.disabled | Boolean | Optional. Set to true to shut down the process. |
processes.manualMode | Boolean | Optional. Set to true to operate this process in manual mode. The Automation Agent will take no actions on the process. |
Hi Alex,
As you noted, the MongoDB API can pass the processes.disabled
and processes.manualMode
parameters. I tested this functionality using MongoDB Ops Manager v2.0 API and MongoDB 3.2.8 without any problems.
This can be done with the curl
command similar to the following:
curl -u "<us...@example.net>:<api_key>" -H "Content-Type: application/json" "http://<app-example.net>/api/public/v1.0/groups" --digest -i -X POST --data @<path_to_data_file>
Where the data file has a JSON format with the processes.disabled
set to true as shown in the following example:
...
...
...
"processes" : [ {
"args2_6" : {
"net" : {
"port" : <your_port#_here>
},
"storage" : {
"dbPath" : "<your_db_path_here>"
},
"systemLog" : {
"destination" : "file",
"path" : "<your_log_path_here>"
}
},
"authSchemaVersion" : 5,
"hostname" : "<your_hostname_here>",
"logRotate" : {
"sizeThresholdMB" : 1000.0,
"timeThresholdHrs" : 24
},
"name" : "<your_deployment_name_here>",
"numCores" : 1,
"processType" : "mongod",
"version" : "<your_version_here>",
"disabled": true
} ],
"replicaSets" : [ ],
"roles" : [ ],
"sharding" : [ ],
"uiBaseUrl" : null,
"version" : 7
}
Please see Ops Manager v2.0 API for more information regarding the API.
It is worth noting that the OpsManager Application is part of the MongoDB Enterprise Advanced subscription, which is a commercially supported product. If your company/organisation already has a commercial subscription and you have further questions about running OpsManager, I would suggest that you consider opening a Commercial Support case.
Alternatively, if you are evaluating MongoDB Enterprise and are interested, feel free to send me a private message of your contact details and I can request a MongoDB Account Executive to reach out to you.
Thanks,
Chris