Fix OTEL issues when dealing with unsupported objects #698
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR prevents the OTEL
instrument_tracing
method to crash when dealing with complex types.It has the following changes:
First, it detects a typical IIB API response, which consists of a tuple with a Flask.Response object and the HTTP code.
Example:
Then, it also changes the execution from the
else
condition oninstrument_tracing
so any object which is not properly mapped gets converted intoString
before being sent as a dictionary value to the OTELspan_result
.With this we no longer see the following messages in IIB-API logs:
Refers to CLOUDDST-23028