Thanks to visit codestin.com
Credit goes to github.com

Skip to content

otlp-proto-grpc default exporter appears to break auto-instrumentation #1189

Closed as not planned
@jeremydvoss

Description

@jeremydvoss

Describe your environment
Windows 11 - Python 3.10.4 - Local OT 1.12.0rc1-0.31b0
Ubuntu 20/04 - Python 3.8.10 - Local OT 1.12.0rc1-0.31b0

Steps to reproduce
Checkout e27f2b8 in core repo. This is the final rc1 commit.
Checkout 51ba801 in contrib repo. This is the commit that added grpc for auto-instrumentation.
Follow these instructions to trigger auto-instrumentation.
This should produce multiple errors on Linux and Windows saying:
RuntimeError: Requested component 'otlp_proto_grpc' not found in entry points for 'opentelemetry_metrics_exporter'

What is the expected behavior?
The above case should produce no errors. To see what that should look like, here is a control case.
Remain at e27f2b8 in core repo. This is the final rc1 commit.
Rewind one commit to ad15f7b in contrib repo. This is the commit before adding grpc for auto-instrumentation.
Follow these instructions to trigger auto-instrumentation.
This should produce no errors. Instead, you should only see output along the lines of:

 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on http://127.0.0.1:8082 (Press CTRL+C to quit)

What is the actual behavior?
RuntimeError: Requested component 'otlp_proto_grpc' not found in entry points for 'opentelemetry_metrics_exporter'

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions