elasticsearch_exporter
mongodb_exporter
Our great sponsors
elasticsearch_exporter | mongodb_exporter | |
---|---|---|
2 | 3 | |
1,851 | 1,089 | |
1.3% | 1.7% | |
8.2 | 8.4 | |
4 days ago | 6 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
elasticsearch_exporter
-
Incorrect document count displayed
After the dependent application is finally optimized for Elasticsearch version 7, the cluster was updated from version 6.8.8 to 7.10.1. The cluster is running inside K8S and is managed by the latest version (2.1.0) of the Elastic operator, and monitored by prometheus-community/elasticsearch_exporter also on the latest 1.3.0 version.
-
Monitoring Shard Allocation In OpenSearch
I've done similar things with the elasticsearch_exporter. It's helped debug scaling problems for us.
mongodb_exporter
- Self hosted MongoDB Monitoring
-
Recap Monthly Percona Developer Meetup Hacktoberfest
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.
-
mongotop — json equivalent metrics in prometheus using mongodb-exporter
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
What are some alternatives?
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
windows_exporter - Prometheus exporter for Windows machines
node_exporter - Exporter for machine metrics
process-exporter - Prometheus exporter that mines /proc to report on selected processes
ebpf_exporter - Prometheus exporter for custom eBPF metrics
percona-docker - Collection of Dockerfiles for Percona software. See individual directories for more details.
pg_stat_monitor - Query Performance Monitoring Tool for PostgreSQL
pmm - Percona Monitoring and Management: an open source database monitoring, observability and management tool
percona-server-mongodb-operator - Percona Operator for MongoDB
kube-state-metrics - Add-on agent to generate and expose cluster-level metrics.
script_exporter - Prometheus exporter to execute scripts and collect metrics from the output or the exit status.
Hacktoberfest2023 - About Make your Pull Request on Hacktoberfest 2023. Don't forget to spread love and if you like give us a ⭐️