[
https://issues.apache.org/jira/browse/SOLR-18638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-18638:
-------------------------------
Description:
🤖 {{OtelMetrics.register()}} builds {{new SolrMetricManager(new
OtlpExporterFactory().getExporter())}} without calling
{{OpenTelemetryConfigurator.initializeOpenTelemetrySdk}}, so its meter
providers fall back to {{Resource.getDefault()}}.
Pushed metrics therefore carry {{service.name="unknown_service:java"}} and no
{{service.instance.id}}, so a collector cannot tell one cross-DC manager from
another. This is the same defect SOLR-18594 fixed for Solr nodes.
It is not a Solr node, so the {{host:port}} node defaults do not apply. It
wants its own resource, for example {{service.name=solr\-crossdc}} plus
{{host.name}}, honouring {{OTEL_SERVICE_NAME}} and {{OTEL_RESOURCE_ATTRIBUTES}}
like everything else.
was:
{{OtelMetrics.register()}} builds {{new SolrMetricManager(new
OtlpExporterFactory().getExporter())}} without calling
{{OpenTelemetryConfigurator.initializeOpenTelemetrySdk}}, so its meter
providers fall back to {{Resource.getDefault()}}.
Pushed metrics therefore carry {{service.name="unknown_service:java"}} and no
{{service.instance.id}}, so a collector cannot tell one cross-DC manager from
another. This is the same defect SOLR-18594 fixed for Solr nodes.
It is not a Solr node, so the {{host:port}} node defaults do not apply. It
wants its own resource, for example {{service.name=solr\-crossdc}} plus
{{host.name}}, honouring {{OTEL_SERVICE_NAME}} and {{OTEL_RESOURCE_ATTRIBUTES}}
like everything else.
> cross-dc-manager pushes OTLP metrics as unknown_service:java
> ------------------------------------------------------------
>
> Key: SOLR-18638
> URL: https://issues.apache.org/jira/browse/SOLR-18638
> Project: Solr
> Issue Type: Bug
> Components: metrics, module - crossDC
> Reporter: Jan Høydahl
> Priority: Major
> Labels: otel
>
> 🤖 {{OtelMetrics.register()}} builds {{new SolrMetricManager(new
> OtlpExporterFactory().getExporter())}} without calling
> {{OpenTelemetryConfigurator.initializeOpenTelemetrySdk}}, so its meter
> providers fall back to {{Resource.getDefault()}}.
> Pushed metrics therefore carry {{service.name="unknown_service:java"}} and no
> {{service.instance.id}}, so a collector cannot tell one cross-DC manager from
> another. This is the same defect SOLR-18594 fixed for Solr nodes.
> It is not a Solr node, so the {{host:port}} node defaults do not apply. It
> wants its own resource, for example {{service.name=solr\-crossdc}} plus
> {{host.name}}, honouring {{OTEL_SERVICE_NAME}} and
> {{OTEL_RESOURCE_ATTRIBUTES}} like everything else.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
