pg_stat_monitor VS mongodb_exporter

Our next project is percona/pg_stat_monitor, a Query Performance Monitoring tool for PostgreSQL. The maintainer is Ibrar Ahmed, Sr. Software Engineer (PostgreSQL). The primary area to contribute is the releases. If there are contributions with ideas on improving the information provided for pg_stat_monitor, they are welcome. The issues are defined in Jira.

For our third project, we have percona/mongodb_exporter. Carlos Salguero is the maintainer for this project. He says it is a project easy to get started, and there is not much-complicated logic behind this. It is about running some MongoDB internal commands to get statistics like diagnostic data or replica status, passing JSON to produce metrics from these commands. You use a complete Makefile to start sandbox instances to test almost everything; you don’t have a virtual machine or different MongoDB instances. The issues are in GitHub and Jira. The primary programming language is Go.

I am running MongoDB-exporter and pushing data to Prometheus by default mongotop metric is disabled in MongoDB-exporter which I have enabled using --collect.topmetrics flag but enabling this flag is giving fewer metrics and I don't need those metrics when I run mongotop -- json on mongo node I am getting a couple of metrics that are pretty useful to me (read, write, total time and stuff per dB, collection, etc ..) is there any flag in mongo-exporter that lets me get the get mongotop -- json equivalent metrics in Prometheus (https://github.com/percona/mongodb_exporter) this the exporter