|
I ran through the simple test install, and came across these suggested improvements to make it easier to use.
We should include the command for opening the file & editing it within step 9:
Edit /opt/mongodb/mms/conf/conf-mms.properties with root privileges and set the following options. For detailed information on each option, see Ops Manager Configuration Files.
Similarly, regarding step 9, we should provide the command to edit /opt/mongodb/mms-backup-daemon/conf/conf-daemon.properties with root privileges within this instruction:
OPTIONAL: If you installed the Backup Daemon, edit /opt/mongodb/mms-backup-daemon/conf/conf-daemon.properties with root privileges and set the mongo.mongoUrivalue to the port hosting the Ops Manager Application database:
Regarding step 9 with respect to conf-mms.properties, it’ll say mongo.mongoUri=mongodb://127.0.0.1:27017/ by default after installing, so we can remove the following:
Set the mongo.mongoUri option to the port hosting the Ops Manager Application database:
mongo.mongoUri=mongodb://localhost:27017
Separately but related (could be a separate ticket), when installing a monitoring or backup agent, the reference docs for “Install Monitoring Agent” and “Install Backup Agent” are lacking the new easy Automation-aided method: There should be a new first class citizen install option for "Add [Monitoring|Backup] Agent with Automation" which would simply link to https://docs.opsmanager.mongodb.com/current/tutorial/move-agent-to-new-server/.
|