Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[exporter/otlp] Allow DNS scheme to be used in endpoint #10010

Conversation

jpkrohling
Copy link
Member

Fixes #4274

Signed-off-by: Juraci Paixão Kröhling juraci@kroehling.de

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
@jpkrohling jpkrohling requested review from a team and songy23 April 22, 2024 13:31
Copy link

codecov bot commented Apr 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.62%. Comparing base (6611edf) to head (537b2da).

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #10010   +/-   ##
=======================================
  Coverage   91.62%   91.62%           
=======================================
  Files         360      360           
  Lines       16679    16681    +2     
=======================================
+ Hits        15282    15284    +2     
  Misses       1060     1060           
  Partials      337      337           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@codeboten codeboten merged commit bb48107 into open-telemetry:main Apr 22, 2024
49 checks passed
@github-actions github-actions bot added this to the next release milestone Apr 22, 2024
andrzej-stencel pushed a commit to andrzej-stencel/opentelemetry-collector that referenced this pull request May 27, 2024
…ry#10010)

Fixes open-telemetry#4274

Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

gRPC client might not be properly balancing requests
3 participants