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
Originally posted by georgkrause August 13, 2022
Whenever the sentry sdk tries to send performance data, I get the following:
demo-api-1 | [sentry] ERROR: Unexpected status code: 400 (body: b'{"spans":{"6":{"tags":{"redis.is_cluster":["Not a valid string."]}},"15":{"tags":{"redis.is_cluster":["Not a valid string."]}},"16":{"tags":{"redis.is_cluster":["Not a valid string."]}},"17":{"tags":{"redis.is_cluster":["Not a valid string."]}}}}')
Where can I start to find the cause for this? Any help is appreciated! :)
The text was updated successfully, but these errors were encountered:
A user reported this bug to GlitchTip which I believe is what's responsible for the 400 error attached. However it may be a bug in sentry-python. A Span interface tag field is documented as "A map or list of tags for this event. Each tag must be less than 200 characters." It's not exactly clear if this is intended to explicitly be a string. One could interpret "characters" as implying it needs to be a string, in which case sentry-python should probably convert it to a string. If it is intended to be a non-string or you feel the server should be responsible for coercing it as a string, then this issue should be closed.
hmm ok I wasn't able to reproduce this. I tried the sample here and all kinds of tags - strings/ints/booleans go through so I'm not sure how to see your error. Please help with me reproduction steps so I can investigate further.
@bufke I just saw what GlitchTip is, our backends are supposed to be flexible in ingesting, so I believe you just need to fix the deserialization on your backend, closing.
Discussed in #1563
Originally posted by georgkrause August 13, 2022
Whenever the sentry sdk tries to send performance data, I get the following:
Where can I start to find the cause for this? Any help is appreciated! :)
The text was updated successfully, but these errors were encountered: