Add semantic conventions for http content size

open-telemetry · Jun 9, 2020 · 1822cdd · 1822cdd
1 parent 1729bc4
commit 1822cdd
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/specification/trace/semantic_conventions/http.md b/specification/trace/semantic_conventions/http.md
@@ -79,6 +79,11 @@ Note that the items marked with [1] are different from the mapping defined in th
 | `http.status_text` | [HTTP reason phrase][]. E.g. `"OK"` | No |
 | `http.flavor` | Kind of HTTP protocol used: `"1.0"`, `"1.1"`, `"2"`, `"SPDY"` or `"QUIC"`. | No |
 | `http.user_agent` | Value of the HTTP [User-Agent][] header sent by the client. | No |
+| `http.request_content_length` | The size of the request body in bytes. For requests using transport encoding, this should be the compressed size. | No |
+| `http.raw_request_content_length` | The size of the raw request body after transport decoding. Not set if transport encoding not used. | No |
+| `http.response_content_length` | The size of the response body in bytes. For requests using transport encoding, this should be the compressed size. | No |
+| `http.raw_response_content_length` | The size of the raw response body after transport decoding. Not set if transport encoding not used. | No |
+
 
 It is recommended to also use the general [network attributes][], especially `net.peer.ip`. If `net.transport` is not specified, it can be assumed to be `IP.TCP` except if `http.flavor` is `QUIC`, in which case `IP.UDP` is assumed.