Add optional Exception parameter to Emit LogRecord

Author: trask

CHANGELOG.md

@@ -20,6 +20,8 @@ release.
 
 - Add optional Ergonomic API.
   ([#4741](https://github.com/open-telemetry/opentelemetry-specification/pull/4741))
+- Add optional `Exception` parameter to Emit LogRecord.
+  ([#4824](https://github.com/open-telemetry/opentelemetry-specification/pull/4824))
 
 ### Baggage
 

specification/logs/api.md

@@ -126,6 +126,10 @@ The API MUST accept the following parameters:
 - [Attributes](./data-model.md#field-attributes) (optional)
 - [Event Name](./data-model.md#field-eventname) (optional)
 
+**Status**: [Development](../document-status.md) - Languages that support exceptions SHOULD accept the following parameter:
+
+- Exception (optional): An exception associated with the log record.
+
 ### Enabled
 
 To help users avoid performing computationally expensive operations when

specification/logs/sdk.md

@@ -224,6 +224,11 @@ However, the changes MUST be eventually visible.
 If [Observed Timestamp](./data-model.md#field-observedtimestamp) is unspecified,
 the implementation SHOULD set it equal to the current time.
 
+**Status**: [Development](../document-status.md) - If an
+[Exception](api.md#emit-a-logrecord) is provided, the SDK MUST set attributes
+from the exception on the `LogRecord` with the conventions outlined in the
+[exception semantic conventions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/exceptions/exceptions-logs.md).
+
 **Status**: [Development](../document-status.md) Before processing a log record,
 the implementation MUST apply the filtering rules defined by the
 [LoggerConfig](#loggerconfig) (in case `Enabled` was not called prior to