You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BatchExportProcessor, PeriodicReader has been rewritten to use own thread. In the new implementation, they do not enforce timeouts and instead relies on Exporters to enforce timeouts.
Tonic currently enforce timeout - default 10, and respects both OTEL_EXPORTER_OTLP_TIMEOUT and the signal specific override of this.
Reqwest-Blocking does not enforce timeout, so the default timeout from Reqwest-Blocking client, which is 30 seconds, is the only one.
Need to fix this to also enforce timeout like the tonic crate.
We also need to document that OTEL_BLRP_EXPORT_TIMEOUT,OTEL_BSP_EXPORT_TIMEOUT, OTEL_METRIC_EXPORT_TIMEOUT are not honored by default in the SDK.
The text was updated successfully, but these errors were encountered:
Its better to do it in the opentelemetry-otlp exporter rather than in the http crate, as it needs to get the time out vases from otlp specific env variables.
BatchExportProcessor, PeriodicReader has been rewritten to use own thread. In the new implementation, they do not enforce timeouts and instead relies on Exporters to enforce timeouts.
Tonic currently enforce timeout - default 10, and respects both OTEL_EXPORTER_OTLP_TIMEOUT and the signal specific override of this.
Reqwest-Blocking does not enforce timeout, so the default timeout from Reqwest-Blocking client, which is 30 seconds, is the only one.
Need to fix this to also enforce timeout like the tonic crate.
We also need to document that OTEL_BLRP_EXPORT_TIMEOUT,OTEL_BSP_EXPORT_TIMEOUT, OTEL_METRIC_EXPORT_TIMEOUT are not honored by default in the SDK.
The text was updated successfully, but these errors were encountered: