open-telemetry / open-telemetry/opentelemetry-python
Generate default endpoint for metric, trace in grpc
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 1k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 19
Description
How about pushing value of endpoint in OTLPSpanExporter, OTLPMetricExporter which generated by OTEL_EXPORTER_OTLP_ENDPOINT like http?
e.g. Trace
self._endpoint = endpoint or environ.get(
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT,
_append_trace_path(
environ.get(OTEL_EXPORTER_OTLP_ENDPOINT, DEFAULT_ENDPOINT)
),
)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the gRPC trace exporter at exporter/opentelemetry-exporter-otlp-proto-grpc/src/opentelemetry/exporter/otlp/proto/grpc/trace_exporter/init.py#L78 and compare it with the HTTP trace exporter at the linked line. Check the corresponding metric exporter as well; done means the gRPC metric and trace exporters derive their default endpoints from OTEL_EXPORTER_OTLP_ENDPOINT in the same manner as the HTTP exporters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, python
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100