MongoDB – Fix Ops Manager CPU Time No Data Available

>use mmsdbagentlog
switched to db mmsdbagentlog
> show collections
app.agentLogs
> db.app.agentLogs.stats()
{
    "ns" : "mmsdbagentlog.app.agentLogs",
    "count" : 1711298,
   "size" : 524287948,
    "avgObjSize" : 306,
    "storageSize" : 71323648,
    "capped" : true,
    "max" : -1,
    "maxSize" : 524288000,
    ... }

Looking in OpsManager Database , they use capped size collection to store the agent log , it seems we don't need to worry about the volume. If the collection confuse you is not capped size , you could try to schedule a job with crontab in Linux(just an example) to remove those records :

db.collection.remove({_id : {$lt : ObjectId('55b0d1c40000000000000000')}})

first 8 character is hexadecimal timestamp can be generate in Linux Shell with command :

Today=`date +%F`
T=`date --date="$Today 00:00:00" +%s`
Stamp=`printf "%X" $T`''0000000000000000
echo $Stamp

MongoDB Ops Manager 3.4.0 (released November, 2016) includes monitoring for hardware metrics (cpu, disk usage, and I/O utilization) via the Automation agent. For more information, see: System and Disk Alerts.

Prior versions of Ops Manager did not include hardware monitoring and required the use of an external tool (munin-node) for CPU & disk metrics. If you are still using an older version of Ops Manager and have installed Munin-node for monitoring CPU & I/O stats you could look into using the Munin df plugin to track free disk space. Munin supports sending alerts via email as well as through Nagios and external scripts.