Are you using MongoDB? If so, you can use IDERA Uptime Cloud Monitor (UCM) to monitor your MongoDB for availability and performance.
Uptime Cloud Monitor from IDERA offers a SAAS based out-of-the-box solution for monitoring a MongoDB instance for availability and performance. If you are not familiar with the concept of custom metrics as used in Uptime Cloud Monitor, please go through Custom Metrics information once before continuing with this document.
There are three steps that you need to do to start monitoring a MongoDB service:
Figure 1: In your Uptime Cloud Monitor Account, navigate to Custom>Getting Started
Login to your Uptime Cloud Monitor account and navigate to Custom tab -> Getting Started. Click on MongoDB icon.
Figure 2: The MongoDB agent installation script
Click on icon to copy the installer script to your clipboard. Paste the command into the terminal window on the server where you want to install the agent. Script can be run on the server running MongoDB, or it can be a different server, but this server will need to be continually running in order to monitor MongoDB.
As soon as the script is run on a terminal with root access, it starts downloading the required MongoDB monitoring agent on your server. You will need to configure the following items in the agent installation process. Item specified in square brackets ( [ ] ) are the default.
Figure 3: Executing the MongoDB agent installation script with user as copperegg, Group as copperegg and monitoring frequency as 60 seconds
Figure 4: Executing the MongoDB agent installation script with group name as “MongoDB_admin” and “MongoDB”, group label as “MongoDB-Admin Metrics” and “MongoDB metrics”, Dashboard as “MongoDB-Admin” and “MongoDB”
3. Group label, group name and dashboard name for custom metrics [MongoDB_admin][MongoDB-Admin Metrics][MongoDB-Admin][MongoDB][MongoDB Metrics][MongoDB]
Figure 5: Executing the MongoDB agent installation script with unique id , server URL and port. Only one MongoDB server is added for monitoring.
4. Unique name for this db server. [<user>-MongoDB] 5. Server details : URL and Port for service. [localhost] 6. Database name: [test] 7. Username and Password are optional 8. After configuring one node, you’ll get an option to add more MongoDB databases and servers.
Figure 6: Executing the MongoDB agent installation script with an upstart init file and the default value for log file name. The installation completes successfully!
9. Configure log file name and upstart job name (defaults present) [/usr/local/copperegg/log/MongoDB_metrics.log][/etc/init/revealmetrics_MongoDB.conf]
Navigate to Dashboard and you will see a new MongoDB-Admin and MongoDB Dashboards have been added automatically by the installer.
Figure 7: A new Dashboard for MongoDB and MongoDB-Admin has been added
As the installed script executes, you will notice data samples appearing on the widgets for this Dashboard.
Figure 8: Widget inside MongoDB-Admin Dashboard displaying uptime. The uptime value gradually increases over time as the MongoDB service continues to remain operational.
Figure 9: Widget inside MongoDB-Admin Dashboard displaying count of current connections.
Figure 10: Widget inside MongoDB-Admin Dashboard displaying count of Page Faults.
Uptime Cloud Monitor currently monitors 52 metrics which cover most of the important metrics for MongoDB-Admin from a performance and stability perspective. You can see these 52 metrics by navigating to the Custom Tab > Custom Objects and selecting Details on the Custom Metrics Group Label [MongoDB-Admin Metrics] that was given as installation input.
The metrics are:
Uptime Cloud Monitor also monitors 5 metrics which cover most of the important metrics for MongoDB databases from a performance and stability perspective. You can see these 5 metrics by navigating to the Custom Tab > Custom Objects and selecting Details on the Custom Metrics Group Label [MongoDB Metrics] that was given as installation input.
For some of these metrics, alerts have been automatically created (see section 3 below). To create new alerts see section: Configuring your own Alerts for MongoDB.
As soon as your MongoDB Monitoring Dashboard comes up, you will notice that some alert configurations have been automatically created by our Installation Script (under Alerts > Configure Alerts). These pre-configured alerts for MongoDB include:
Number of connections to the database server from clients
Alert will be triggered when connections reach 800000.
Amount of memory currently used by the database process
Number of page faults per second that require disk operations
Alert will be triggered for every page fault.
Number of warnings raised per second
Warning Alert for each assert warning.
If the alerting condition is met for these pre-configured alerts, some alert notifications may also be triggered.
Figure 11: A new alert being added that will be triggered when MongoDB data size metric exceeds a threshold of 2000 within a time period of 1 min
Alerts can also be configured against any of these 57 monitored metrics for MongoDB.
You can configure new alerts that will be triggered when performance issues with MongoDB arise. You can also configure the notification mechanisms for a triggered alert.
Notification mechanisms include:
Webhooks are also exposed for clients to configure custom notification mechanisms. More about setting up website probe alerts can be found here.
Sign up for a 14 day FREE TRIAL of Uptime Cloud Monitor (no Credit Card required).
You can find more information about Uptime Cloud Monitor pricing options here.
We charge only $0.08 per month per metric!
Sign up today!