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

Stackdriver exporter doesn't expose timeout flag #738

Closed
olagacek opened this issue Aug 17, 2020 · 0 comments · Fixed by #835
Closed

Stackdriver exporter doesn't expose timeout flag #738

olagacek opened this issue Aug 17, 2020 · 0 comments · Fixed by #835
Assignees
Labels
enhancement New feature or request

Comments

@olagacek
Copy link
Contributor

Is your feature request related to a problem? Please describe.

Currently StackDriver exporter has a 5s timeout for calls to StackDriver Monitoring API (default value in an underlying OpenCensus implementation). From time to time my agent, which uses Open Telemetry StackDriver exporter receives deadline exceeded errors from StackDriver Monitoring API. With timeout bigger than 5s number of those errors could be reduced.

Describe the solution you'd like
Flag, which will allow to set timeout for StackDriver exporter.

Additional context

Link to Opencensus timeout config: https://github.com/census-ecosystem/opencensus-go-exporter-stackdriver/blob/master/stackdriver.go#L256

@nilebox nilebox self-assigned this Aug 27, 2020
@andrewhsu andrewhsu added the enhancement New feature or request label Jan 6, 2021
dyladan referenced this issue in dynatrace-oss-contrib/opentelemetry-collector-contrib Jan 29, 2021
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
ljmsc referenced this issue in ljmsc/opentelemetry-collector-contrib Feb 21, 2022
* Remove the push controller named Meter map

* Checkpoint

* Remove Provider impls

* Add a test

* Expose Provider() getter instead of implementing the interface
codeboten pushed a commit that referenced this issue Nov 23, 2022
Now that SDK does not depend on opentelemetry-instrumentation
anymore and opentelemetry-instrumentation has actual build time
dependencies on the contrib repo, it makes maintanence a lot
easier if we move opentelemetry-instrumentation to contrib repo.
opentelemetry-distro depends on opentelemetry-instrumentation
and is being moved as well. Neither of the two packages are
really part of "core" Otel python anyway.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants