-
Notifications
You must be signed in to change notification settings - Fork 250
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
opencensus-ext-azure trace_exported request.success value is always False on Python2 #764
Comments
This is a known issue, which is being fixed by #755. |
@victoraugustolls FYI. |
I realize this issue is for Python2, but I think in Python3 the same issue manifests as an exception, |
@RocketPuppy you're right. |
@RocketPuppy yes, but the main issue is that |
While that PR is in progress, is there a workaround available? |
@RocketPuppy #755 got merged today. We will do a hotfix release. Closing the issue now. pip install "git+https://github.com/census-instrumentation/opencensus-python.git@master#subdirectory=context/opencensus-context"
pip install "git+https://github.com/census-instrumentation/opencensus-python.git@master"
# add your packages (e.g. opencensus-ext-azure) based on what's needed
... @lzchen need your help to do a hotfix release. Thanks. |
@reyang I'd like to plan when I can go live with my application monitoring in production. Do you know when that release is going to be done? I don't see anything updated on pypi or the github releases yet. |
@RocketPuppy I will be doing a release today! |
@RocketPuppy Packages are up! |
Looks like on Python2 exported request success status is wrong, because of objects comparison on
this line
Steps to reproduce.
data.success = (status_code >= 200 and status_code <= 399)
if
status_code
type is string, than:>>> ("200" >= 200 and "200" <= 399)
>>> False
since in python2
int
is always less thanstr
Otherwise:
>>> (200 >= 200 and 200 <= 399)
>>> True
This mainly affects all requests
success
status displayed in Azure Monitor Log which is set toFalse
The text was updated successfully, but these errors were encountered: