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
Currently, we use the raw field in multiple events to allow logging of the raw data.
It would be interesting to allow logging for only the first x bytes, which can help in debugging.
Some options:
New raw_partial field, containing the partial hex-encoded data
New raw_length field, indicating the length of the raw field. If it doesn't match the length parameter (or equivalent), we know raw is truncated
No new fields: we can derive raw's length from the size of the string. Then use similar logic as 2) to detect truncation
No new fields, end raw field with ... at the end of the string. Perfectly human readable, bit of a hassle when decoding the bytes to e.g., ASCII + less optimal for a potential binary format
Personally, I would prefer 3. We will strongly advise AGAINST logging raw in typical usage scenarios anyway: it's only to be used for core debugging. In these latter cases, the person debugging probably knows the stack a bit more deeply and understands that it's logging just partial raw values.
Currently, we use the
raw
field in multiple events to allow logging of the raw data.It would be interesting to allow logging for only the first x bytes, which can help in debugging.
Some options:
raw_partial
field, containing the partial hex-encoded dataraw_length
field, indicating the length of theraw
field. If it doesn't match thelength
parameter (or equivalent), we knowraw
is truncatedraw
's length from the size of the string. Then use similar logic as 2) to detect truncationraw
field with...
at the end of the string. Perfectly human readable, bit of a hassle when decoding the bytes to e.g., ASCII + less optimal for a potential binary formatPersonally, I would prefer 3. We will strongly advise AGAINST logging
raw
in typical usage scenarios anyway: it's only to be used for core debugging. In these latter cases, the person debugging probably knows the stack a bit more deeply and understands that it's logging just partial raw values.cc @huitema
The text was updated successfully, but these errors were encountered: