[
https://issues.apache.org/jira/browse/SOLR-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848325#comment-17848325
]
David Smiley commented on SOLR-10654:
-------------------------------------
A possible way to have it both ways would be to +embed+ the Prometheus Exporter
_partially_, without the caching aspect -- it'd be a request handler that
fetches metrics locally (would talk to MetricsHandler in a direct way) and
post-processes via JQ. I don't love JQ but... hey, some do. XSLT/XQuery is
more my thing. No new dependencies to add directly to Solr; people would just
add the Exporter's as if it's a module. Regardless of some details, there
would still be *some* overhead in this post processing due to JQ. I'm not sure
that's the pain point we're solving for here? I haven't measured lately. It
could be interesting to compare the performance of the Prometheus Exporter and
this patch.
> Expose Metrics in Prometheus format DIRECTLY from Solr
> ------------------------------------------------------
>
> Key: SOLR-10654
> URL: https://issues.apache.org/jira/browse/SOLR-10654
> Project: Solr
> Issue Type: Improvement
> Components: metrics
> Reporter: Keith Laban
> Priority: Major
> Attachments: prometheus_metrics.txt
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Expose metrics via a `wt=prometheus` response type.
> Example scape_config in prometheus.yml:
> {code}
> scrape_configs:
> - job_name: 'solr'
> metrics_path: '/solr/admin/metrics'
> params:
> wt: ["prometheus"]
> static_configs:
> - targets: ['localhost:8983']
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
