✅ Deploy Preview for opentelemetry-cpp-api-docs canceled.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.96%. Comparing base (7059f73) to head (55a31a3).
Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main    #3495      +/-   ##
==========================================
+ Coverage   89.95%   89.96%   +0.02%     
==========================================
  Files         219      219              
  Lines        7051     7051              
==========================================
+ Hits         6342     6343       +1     
+ Misses        709      708       -1     

Unfortunately, as a side effect, this change also enables support for populating byte/uint8 types as span attribute values, which is inconsistent with the specs:

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/common/README.md#attribute

Per the spec, an attribute value MUST be one of the following:

• string
• boolean
• double (IEEE 754)
• signed 64-bit integer
• Or an array of the above types (array must be homogeneous)

Supporting raw bytes or uint8 is not permitted for span attributes.

It’s better to enable populating uint8_t as OTLP attributes or body only for logs, not for spans.
Alternatively, instead of this PR, document that byte data should be encoded as base64 and set as a string attribute. The custom exporter or backend can handle base64 decoding if needed.

Unfortunately, as a side effect, this change also enables support for populating byte/uint8 types as span attribute values, which is inconsistent with the specs:

https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/common/README.md#attribute

Per the spec, an attribute value MUST be one of the following:

• string
• boolean
• double (IEEE 754)
• signed 64-bit integer
• Or an array of the above types (array must be homogeneous)

Supporting raw bytes or uint8 is not permitted for span attributes.

It’s better to enable populating uint8_t as OTLP attributes or body only for logs, not for spans. Alternatively, instead of this PR, document that byte data should be encoded as base64 and set as a string attribute. The custom exporter or backend can handle base64 decoding if needed.

Thanks, only log record use bytes now.