pmm VS mongodb_exporter

For ongoing monitoring of query performance, I use Percona Monitoring & Management - it's query log provides an easy way to spot frequent queries that may need optimizing.

I cannot recommend PMM highly enough - it's free. You'll get a ton of insight into your DB's bottlenecks, and can use it to validate changes made.

I use the free, open-source tool Percona Monitoring and Management (PMM) for monitoring and graphing.

i don't know if this is an idiom or not but at my workplace each go repo has a separate tools/ directory, which only has 3 files `tools.go` , `go.mod` and `go.sum` https://github.com/percona/pmm/tree/main/tools

Curious what monitoring solution you've used that's both plug-and-play and in IaC. And in any case, nothing stops you (I like this approach, actually) from running your monitoring solution in K8s. For DBs in particular, I'm a huge fan of PMM, which is a set of extremely thorough Grafana dashboards atop VictoriaMetrics, with some discovery tooling.

Percona Monitoring and Management - Open Source tool has backups included

https://www.percona.com/software/database-tools/percona-moni...

(Percona Founder so kind of biased)

Our next project is Percona Monitoring and Management (PMM). This project is supported by Artem Gavrilov, Backend Software Engineer, and Nurlan Moldomurov, Full-Stack Engineer. PMM is a great project to contribute to during Hacktoberfest. There are minor and easy-to-do issues in Github; it is not necessary to register them in Jira. These contributions are welcome if you have any good ideas, want to improve something or simplify some process. Send your PR; the maintainers will review it as soon as possible. We also have advanced issues if you want to go for more advanced tasks.

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