Switching to a local MongoDB

Edit online

If your Cloud APM server is connected to a MongoDB on a remote server, you can switch to use the local MongoDB at any time.

Procedure

Complete the following steps as the root user on the system where you installed the Cloud APM server:

  1. Go to the install_dir/mongodb/bin directory.
    For example: 
    cd install_dir/mongodb/bin
  2. Delete the /mongodb/mongodb-remote file.
  3. Run the activate-mongodb.sh command to apply the change.
  4. Configure communications between the local MongoDB and the Cloud APM server:
    1. If you are not already logged in to the Cloud APM console, log in now.
      (See Starting the Cloud APM console.)
    2. Click System Configuration > Advanced Configuration and click Mongo Configuration.
    3. In the Host Name field, enter localhost.
    4. Click Save to save the configuration.
    After you click Save, the transaction tracking components begin communicating with the local MongoDB.
  5. If the remote MongoDB was using a custom password rather than the default mongoUsrpasswd@08 password, run the install_dir/ccm/mongopasswd.sh script to configure the local MongoDB and Cloud APM server to use your password.

Results

The Cloud APM server is connected to the local MongoDB.

After you switch to the local version of MongoDB, new threshold events and new transaction tracking data are transferred between the Cloud APM server and the local MongoDB.

Existing open events and existing transaction tracking data are not migrated to MongoDB on the local system. Use the Linux touch command to modify the date and time of all of the private_situation.xml files in the subdirectories under the install_dir/wlp/usr/servers/min/dropins/CentralConfigurationServer.war/data_source directory to view existing open events in the Cloud APM console.