We keep all essential user documentation (and some dev docs) in the Ref Guide.
The source for the Ref Guide is checked-in under solr/solr-ref-guide, it uses a
simple ASCII markup so adding some content should be easy. You should follow
the same workflow as with the code (create a JIRA, and then
Many thanks both for your responses, they've been helpful.
@Andrzej - Sorry I wasn't clear on the "A latency of 1mil" as I wasn't
aware the image wouldn't come through. But following your bullet points
helped me present a better unit for measurement in the axis.
In regards to contributing, would
Hi,
Starting with Solr 7.0 all JMX metrics are actually internally driven by the
metrics API - JMX (or Prometheus) is just a way of exposing them.
I agree that we need more documentation on metrics - contributions are welcome
:)
Regarding your specific examples (btw. our mailing lists aggressi
Hi Richard,
We do not use API to collect metrics but JMX, but I believe that those are the
same (did not verify it in code). You can see how we handled those metrics into
reports/charts or even use our agent to send data to Prometheus:
https://github.com/sematext/sematext-agent-integrations/tree
Hi there,
I'm currently working on using the prometheus exporter to provide some
detailed insights for our Solr Cloud clusters.
Using the provided template killed our prometheus server, as well as the
exporter due to the size of our clusters *(each cluster is around 96 nodes,
~300 collections wit
