[
https://issues.apache.org/jira/browse/SOLR-18536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18148879#comment-18148879
]
ASF subversion and git services commented on SOLR-18536:
--------------------------------------------------------
Commit 81c4470da5fec97d71b956097a9aa76e8f4991bb in solr's branch
refs/heads/main from Jan Høydahl
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=81c4470da5f ]
SOLR-18536: OTel Collector config (#5244)
> Support metrics through OTEL collector (push)
> ---------------------------------------------
>
> Key: SOLR-18536
> URL: https://issues.apache.org/jira/browse/SOLR-18536
> Project: Solr
> Issue Type: Sub-task
> Components: metrics
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> So far we have been focusing on Prometheus scraping Solr. In 9.x it would
> scrape the SolrPrometheusExporter. Now in 10.1+ we can point it directly at
> each solr node's prometheus compatible metrics endpoint.
> But many environments prefer OTEL / OTLP push of metrics rather than direct
> scrape. Problem is that OTEL metrics names have a different format than
> prometheus, so they are not compatible.
> We can solve this by a conversion stage. This Jira will deliver
> * The dev/ docker-compose stack will spin up an OTEL collector
> * A sample OTEL collector config with a metrics key converter thar serves
> the same prometheus keys as when scraping solr direclty (so dashboards will
> work), and that sets up an OTEL exporter instance that Prometheus can scrape
> * Configure prometheus to scrape the OTEL collector
> * Some ref guide documentation around the subject
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]