[
https://issues.apache.org/jira/browse/SOLR-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847998#comment-17847998
]
David Smiley commented on SOLR-10654:
-------------------------------------
Overall I wonder what others think about maintaining two parallel yet
consistent metrics mappings -- one in the "Prometheus Exporter" configured
using lots of "jq" and that which is very flexible (intended for users to
configure/hack as needed), the second what this PR does, basically as
hard-coded as can be. For example if we add a new metric, we then probably
need to update the exporter's config, and also edit source code being added
here. This could be helped by having the Prometheus Exporter fetch certain
metrics pass-through on-demand. But based on the design of the Prometheus
Exporter, I think that could be tricky/awkward.
> 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]
