Before opening a feature request against this repo, consider whether the feature should/could be implemented in the other OpenTelemetry client libraries. If so, please open an issue on opentelemetry-specification first.

Is your feature request related to a problem?
No

Describe the solution you'd like
Many embedded devices run C++ as their primary programming language. This includes both hobbyist devices such as Arduino's and industrial IoT devices based on chips from various vendors.

Whilst each chip has it's own "special requirements", being able to add Logs, Traces, and Metrics to embedded devices (especially those that have a robust data connection to the outside world!) would provide huge insight into how microcontroller-based embedded devices interact with the systems they talk to.

Describe alternatives you've considered

• Creating a w3c Trace Context TraceID manually as part of the application code and using existing logging libraries to send that data to OTEL collector for processing

Additional context

• Common transports from embedded IoT devices include HTTP and MQTT
• LoRaWAN and other 5G technologies are also options, however payload restrictions will limit what can be sent over some of these options, so I'd recommend only using WiFi, Cellular, or Ethernet as "outbound" options.