-
Notifications
You must be signed in to change notification settings - Fork 45
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
_detector.GoogleCloudResourceDetector misbehaving on Buildkite #363
Labels
Comments
This fails, I see every print so is it really
|
Is there any chance you have minimal repro? I'm not familiar with BuildKite but I haven't seen this issue on GKE in general |
xrmx
added a commit
to xrmx/opentelemetry-operations-python
that referenced
this issue
Dec 19, 2024
We should create a Resource instance and not use Resource.create because if we set OTEL_EXPERIMENTAL_RESOURCE_DETECTORS we will go into an infinite loop trying to load and instantiate all the resources detectors. Fix GoogleCloudPlatform#363
xrmx
added a commit
to xrmx/opentelemetry-operations-python
that referenced
this issue
Dec 24, 2024
We should create a Resource instance and not use Resource.create because if we set OTEL_EXPERIMENTAL_RESOURCE_DETECTORS we will go into an infinite loop trying to load and instantiate all the resources detectors. Fix GoogleCloudPlatform#363
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have
_detector.GoogleCloudResourceDetector
misbehaving when running under Buildkite (CI tool) on GKE.When I load the resource detector the process will get restarted and I'll have an infinite loop with one of this messages from the OTel sdk per run:
I've debugged this a bit and there is something in
_gke_resource
that causes this.As an experiment I've open coded the thing into another resource detector and to my surprise the following code is working fine:
Unrelated questions:
_metadata.is_available
a wrapper for _metadata.get_metadata() that returns false if an exception is raised? This way we have one http call less.The text was updated successfully, but these errors were encountered: