Currently there is no such a thing.
However, MongoDB writes its log into /var/log/mongodb/mongodb.log
Just make sure you turn on the profiling: db.setProfilingLevel(1,50)
Then all you need is to create an Splunk inputs.conf and you are good to go.
For example,
[monitor:///var/log/mongodb/mongodb]
sourcetype = mongodb_profile
index = mongodb_metrics
[script://./bin/mongodb_cpu.sh]
interval = 30
sourcetype = cpu
source = cpu
index = mongodb_os
disabled = 0
** If you download Splunk *Nix App you can find many of these scripts to monitor these Linux resources
Currently there is no such a thing.
However, MongoDB writes its log into /var/log/mongodb/mongodb.log
Just make sure you turn on the profiling: db.setProfilingLevel(1,50)
Then all you need is to create an Splunk inputs.conf and you are good to go.
For example,
[monitor:///var/log/mongodb/mongodb]
sourcetype = mongodb_profile
index = mongodb_metrics
[script://./bin/mongodb_cpu.sh]
interval = 30
sourcetype = cpu
source = cpu
index = mongodb_os
disabled = 0
** If you download Splunk *Nix App you can find many of these scripts to monitor these Linux resources
Thank you for this information. The one issue still to resolve is the formatting of the log; it is BSON (Binary-encoded JSON).