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
The UI special case the http.status_code tag in the transaction payload (not spans) to show the status sublabel with the HTTP status code (see flask image).
This looks suboptimal due to, let's say we have a transaction that finishes with the status OK, this transaction has 2 spans which are HTTP requests, one of them is a 200 and the other one is a 500, both are running in parallel and since the tag is in the transaction tags and not span tags, the span that finishes the later always wins setting the tag, overwriting the previous tag.
The same transaction may have a 200 or 500 randomly and can be confusing.
is it an issue? should we address that? also, http.status_code isn't part of the spec so most SDKs are not setting it.
The UI special case the
http.status_codetag in the transaction payload (not spans) to show the status sublabel with the HTTP status code (see flask image).This looks suboptimal due to, let's say we have a transaction that finishes with the status OK, this transaction has 2 spans which are HTTP requests, one of them is a 200 and the other one is a 500, both are running in parallel and since the tag is in the transaction tags and not span tags, the span that finishes the later always wins setting the tag, overwriting the previous tag.
The same transaction may have a 200 or 500 randomly and can be confusing.
is it an issue? should we address that? also,
http.status_codeisn't part of the spec so most SDKs are not setting it.