Srikanth Chekuri
Srikanth Chekuri
@mahipatsinghtellius Are you still facing the issue? What is the propagator you are using and can you clarify where you are facing the issue?
That's correct. The individual service-wise numbers are shown in the landing page table. The service graph shows the RED metrics on edges, giving service interaction such as which downstream service...
Yes, that's the current behavior.
Can this be merged so that It will be part of the next release? I would like to use this feature.
@larryluogit shouldn't `system.data_skipping_indices` be including this {_dict,_post} size information somehow or am I misinterpreting something? I have a table where `_post` is as big as ~280x of the original column....
We have been using OTLP/gRPC as a default exporter in the auto instrumentation package https://github.com/open-telemetry/opentelemetry-python-contrib/blob/51ba801bfda31c3d57902d9f9df938cee1236eb8/opentelemetry-distro/src/opentelemetry/distro/__init__.py#L37-L38. This was the choice of default partly because we didn't have HTTP exporters for OTLP....
Don't we do that already today? when the `OTEL_TRACE_EXPORTER` is set to [gRPC](https://github.com/open-telemetry/opentelemetry-python/blob/main/exporter/opentelemetry-exporter-otlp-proto-grpc/src/opentelemetry/exporter/otlp/proto/grpc/exporter.py#L215) it uses the default `http://localhost:4317` for the endpoint and `http://localhost:4318` for HTTP. And the priority order `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT`...
Hello 👋 , I am one of the co-maintainers of OpenTelemetry. The instrumentations are maintained in our repo for various reasons. We could provide some value fast without putting in...
Fwiw, the falcon also showed interest in adding support directly https://github.com/falconry/falcon/issues/1828. If package authors adopt OTEL gradually, we can start deprecating the instrumentation package that monkey patch the original packages,...