You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2021/01/08 16:35:00 UTC
[jira] [Commented] (SOLR-11795) Add Solr metrics exporter for
Prometheus
[ https://issues.apache.org/jira/browse/SOLR-11795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261423#comment-17261423 ]
David Smiley commented on SOLR-11795:
-------------------------------------
In the sixth comment on this issue, [~koji] contrasts this approach to SOLR-10654 (using a response writer; CC [~k317h] ). There are definitely positive things to be said about the Prometheus Exporter – most of all is its flexibility. While I don't disagree with the specific points Koji raised, let's not pretend that the Exporter is 100% better than a response writer. I think it's important to consider how the Exporter suffers relative to the Response Writer _as well:_
The Exporter is more heavyweight both literally in the actual processing required and architecturally -- witness the intermediate "JQ" processing. In my experience, I've found maintaining its long configuration file to be a PITA with its heavy repetition and some new quirky language to understand ("JQ"). There is additional delay in the metrics reflecting reality since the Exporter caches it. I feel I can confidently claim that maintaining the Exporter has higher costs for us than the response writer would have been. It's also more maintenance for our users (and I wear that figurative hat as well). It was said "Implementing an exporter looks mainstream in Prometheus field" – but so what? I argue Solr's flexible frameworks (e.g. response writers) unlocked options to us not easily available to other projects. Yet we didn't leverage it.
There may be a case for both to co-exist, such as the response writer purely being used for node-level metrics, and the exporter being used for cluster level? I think I will explore this with my colleagues. If we try it, we'll report our experience back to the project. If we explore but rule it out, I'll share why.
> Add Solr metrics exporter for Prometheus
> ----------------------------------------
>
> Key: SOLR-11795
> URL: https://issues.apache.org/jira/browse/SOLR-11795
> Project: Solr
> Issue Type: Improvement
> Components: contrib - prometheus-exporter, metrics
> Affects Versions: 7.2
> Reporter: Minoru Osuka
> Assignee: Koji Sekiguchi
> Priority: Minor
> Fix For: 7.3, 8.0
>
> Attachments: SOLR-11795-10.patch, SOLR-11795-11.patch, SOLR-11795-2.patch, SOLR-11795-3.patch, SOLR-11795-4.patch, SOLR-11795-5.patch, SOLR-11795-6.patch, SOLR-11795-7.patch, SOLR-11795-8.patch, SOLR-11795-9.patch, SOLR-11795-dev-tools.patch, SOLR-11795-doc.patch, SOLR-11795-ref-guide.patch, SOLR-11795.patch, solr-dashboard.png, solr-exporter-diagram.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I 'd like to monitor Solr using Prometheus and Grafana.
> I've already created Solr metrics exporter for Prometheus. I'd like to contribute to contrib directory if you don't mind.
> !solr-exporter-diagram.png|thumbnail!
> !solr-dashboard.png|thumbnail!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org