[
https://issues.apache.org/jira/browse/SOLR-18310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18099750#comment-18099750
]
ASF subversion and git services commented on SOLR-18310:
--------------------------------------------------------
Commit 1ec24a1c968c743f7c78bdd7166e50639fdefa71 in solr's branch
refs/heads/branch_10x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=1ec24a1c968 ]
SOLR-18310: opentelemetry: switch default from gRPC to http/protobuf(#4646)
opentelemetry: the default OTLP sender is now http/protobuf port 4318 and with
fewer/no JARs to do so.
JARs for others like gRPC have been removed but users can add as they need.
This reduces Netty JARs, for example.
Affects metrics & tracing.
Co-authored-by: copilot-swe-agent[bot]
<[email protected]>
(cherry picked from commit 1e8116145faca028b08ac129fdf83e2d82091822)
> opentelemetry module should not ship Netty JARs
> -----------------------------------------------
>
> Key: SOLR-18310
> URL: https://issues.apache.org/jira/browse/SOLR-18310
> Project: Solr
> Issue Type: Improvement
> Components: tracing
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> We ship more JARs than we need to in our opentelemetry module. Netty is a
> CVE machine so let's pair down what we ship. See OTEL docs on the exporters
> [https://opentelemetry.io/docs/languages/java/sdk/#otlp-exporters] which
> shows we can use a JDK HttpClient based transport. We'd loose GRPC but so
> what – someone can add such JARs if they want.
> Also in the bigger picture, an OTEL Java Agent can be used, rendering the
> need for the module altogether moot. FWIW I prefer the agent.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
