Using MongoDB Support Feature
Learn how to redirect the collection of metrics and audit data from the designated Policy Manager Database to the MongoDB Database.
Supported Platforms: 8.0 and later
Supported Envision Versions: 1.0 and later
Table of Contents
- Step 1: Download and Install MongoDB
- Step 2: Create MongoDB Data Folder
- Step 3: Start MongoDB
- Step 4: Configure MongoDB Support Plug-in
This plug-in redirects the collection of metrics and audit data from the designated Policy Manager Database (RDBMS) to the MongoDB Database.
Use of this plug-in requires installation of MongoDB.
Redirecting the capture of metrics and auditing data can help to optimize performance by reducing the toll on your designated RDBMS. This is because metrics and roll-up data processes will now occur in MongoDB which will increase performance in the container by reducing query times and CPU/memory overhead.
- This plug-in can be used exclusively with the Policy Manager product or in combination with Community Manager and/or Akana Envision.
- Data stored includes Policy Manager Alerts, and all metrics and auditing log data that has a write operation.
- Metrics and audit data collected from Network Director will be stored directly in MongoDB and will not be stored in the designated Policy Manager database (RDBMS). This would be data relating to how a particular API is performing; for example, response times and error rates.
- Alert and audit trail data would be related to when a particular service changed, who changed it, what is the affect of the change, etc.
- Audit data can be used both in Community Manager, Policy Manager, and Envision for various charts by configuring a Business Metrics Policy that allows you to configure what focus of data to extract from the payload.
- In Policy Manager, logging data for historical charts and logs that can be viewed via the Monitoring tab in Services, Containers, and Contracts will now be fetched from MongoDB.
- The logging data stored in MongoDB can also be used in your own third-party reporting tools.
Step 1: Download and Install MongoDB
Use of this plug-in requires installation of MongoDB. If you have already installed and started MongoDB skip to Step 4.
- Go to http://www.mongodb.org/downloads and download the MongoDB Version 3.0.0 file for your platform. Windows 64-bit (MSI), Linux 64-bit (TGZ), and Solaris 64-bit (TGZ) are supported. If you are on a Mac you can install Mongo with homebrew using "brew install mongo."
- Install MongoDB on your platform.
Note that these instructions provide a basic MongoDB installation approach. For information on installation instructions and shutdown procedures for your specific deployment, refer to the MongoDB documentation: https://docs.mongodb.org/v3.0/tutorial/manage-mongodb-processes/
Step 2: Create MongoDB Data Folder
- Create a MongoDB data folder. The default is /data/db. If you prefer to use a different location use --dbpath.
Step 3: Start MongoDB
- Navigate to the MongoDB installation directory: /MongoDB/Server/3.0/bin
- Enter mongod.
- If MongoDB successfully starts, your command window will display the message waiting for connections, followed by the port number.
Step 4: Configure MongoDB Support Plug-in
- Log into the Akana Administration Console of the target installation container instance using your default credentials.
- On the Available Features screen, select Plug-ins from the Filter menu.
- Select the MongoDB Support plug-in and click Install Feature.
- After the installation is complete, click Configure and continue.
- On the Configure MongoDB Database screen, specify the host name and port where the MongoDB database is installed in the MongoClientURI field. The default MongoDB port is 27017.
- Click Finish, and then click OK to restart the container. The URI is assigned and the system automatically configures seed data and adds schemas.
After the installation is complete, you can manage (install / uninstall) data sets via the Configuration tab by selecting Configure MongoDB Database.