[ 
https://issues.apache.org/jira/browse/SOLR-18060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18107131#comment-18107131
 ] 

David Smiley commented on SOLR-18060:
-------------------------------------

Noticed the crossdc backport commits (e.g. SOLR-18060/61/62/63/64/77) use a 
subject like "... (cherry-pick from #4106) (#4150)" to note provenance. Next 
time, please switch to {{git cherry-pick -x <sha>}} instead.  It embeds the 
standard {{(cherry picked from commit <sha>)}} line in the commit body, which 
backport-tracking tooling (and other contributors) actually parse. The 
hand-written subject note isn't isn't standardized.  If you backport with 
IntelliJ, the message should be there in my experience.

Of course, going forward, IMO nobody should bother with the burden of 
backporting most of the time.  Just update a GH PR "Milestone" accordingly and 
my scripts will take care of it.


> CrossDC Consumer - add Prometheus metrics
> -----------------------------------------
>
>                 Key: SOLR-18060
>                 URL: https://issues.apache.org/jira/browse/SOLR-18060
>             Project: Solr
>          Issue Type: Improvement
>          Components: module - crossDC
>    Affects Versions: 10.0
>            Reporter: Andrzej Bialecki
>            Assignee: Andrzej Bialecki
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: main(11.0), 10.1
>
>          Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> The CrossDC Consumer application (a.k.a. cross-dc-manager) exposes several 
> useful metrics in Dropwizard JSON format. However, the prevalent format 
> currently used for metrics monitoring seems to be Prometheus text / protobuf 
> format.
> This ticket will:
>  * add Prometheus wrapper around existing Dropwizard metrics,
>  * move the existing Dropwizard JSON endpoint to {{/metrics/json}}
>  * add a new API endpoint {{/metrics/prometheus}} .



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to