Solr metrics #291
Draft
Solr metrics #291
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is based on https://grafana.com/grafana/dashboards/14114-postgres-overview/ with an extra check for max query duration that seemed interesting, and is mostly intended as a proof of concept for provisioning dashboards. We can further improve the dashboard as needed.
As a start, monitor the amount of rows on sir-indexed tables. Includes a dashboard with gauges for every table; I don't see a reason why it would be useful to have these be line charts since there's no reason we should expect huge jumps, it's just good to have a clear idea of which tables are bigger with the numbers.
There seems to be no good reason why we would keep hitting the DB every 30 seconds to get the counts. 5 minutes seems more than enough. My understanding is that if I set min_interval here to 300s (5m) it will just keep the value for that long and keep responding with it, however often prometheus asks.
* origin/provision-psql-dashboard: Only run table counts every 5 minutes Set up sql-exporter to monitor db content Provision a basic PSQL dashboard for grafana
|
There's a temporary commit here that requires you to build a local docker build -t metabrainz/mb-solr:solr-9.7.0 -f Dockerfile . |
|
This works nicely locally - to be honest I have zero clues what is useful data for solr for us, but in https://docs.google.com/document/d/1vQBiHdxO_qkmxUAfS10QWhoULSYcPazxZWSxsxJMS9o/edit?pli=1&tab=t.0 we wanted "Number of collection documents & Data size" - is that in there? There's so much stuff, we should document exactly where to look if so! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is based on #290 and I'm launching it in the same way (
admin/configure add monitoring+docker compose up -d).I followed https://solr.apache.org/guide/solr/latest/deployment-guide/monitoring-with-prometheus-and-grafana.html and copied the default dashboard under contrib/, only fixing the Prometheus data source name.