document sentry.origin log attribute

Author: AbhiPrasad

develop-docs/sdk/telemetry/logs.mdx

@@ -285,6 +285,14 @@ Example:
 }
 ```
 
+If a log is generated by an SDK integration, the SDK should also set the `sentry.origin` attribute, as per the [Trace Origin](./traces/trace-origin/) documentation. It is assumed that logs without a `sentry.origin` attribute are manually created by the user.
+
+```json
+{
+  "sentry.origin": "auto.db.graphql"
+}
+```
+
 Beyond these attributes, we are exploring if the SDK should also send OS, user, and device information automatically (via reading the appropriate contexts from the scope). Given this behaviour can easily be added as a new feature to the SDK, it does not have to be part of the initial SDK implementation until we make a finalized decision.
 
 ### SDK Integrations

develop-docs/sdk/telemetry/traces/trace-origin.mdx

@@ -2,11 +2,13 @@
 title: Trace Origin
 ---
 
-Trace origin indicates what created a trace or a span. Not all traces and spans contain enough information
+Trace origin indicates what created a trace, span or log. Not all traces, spans or logs contain enough information
 to tell whether the user or what precisely in the SDK created it. Origin solves this problem. Origin can be sent with
-the <Link to="/sdk/data-model/event-payloads/contexts/#trace-context">trace context</Link> or <Link to="/sdk/data-model/event-payloads/span/">spans</Link>.
-The SDKs should set this value automatically. It is not expected to be set manually by users. The value for origin should rarely change so that we can run proper analytics on them.
+the <Link to="/sdk/data-model/event-payloads/contexts/#trace-context">trace context</Link>, <Link to="/sdk/data-model/event-payloads/span/">spans</Link>, or <Link to="/sdk/telemetry/logs/">logs</Link>.
+
+For logs and standalone spans, the origin should be set as the `sentry.origin` attribute key.
 
+The SDKs should set this value automatically. It is not expected to be set manually by users. The value for origin should rarely change so that we can run proper analytics on them.
 
 The origin is of type `string` and consists of four parts: `<type>.<category>.<integration-name>.<integration-part>`.
 Only the first is mandatory. The parts build upon each other, meaning it is forbidden
@@ -28,12 +30,10 @@ to skip one part. For example, you may send parts one and two but aren't allowed
 
 : _Optional_. Is the part of the integration of the SDK that created the trace or span. This is only useful when one integration creates multiple traces or spans, and you'd like to differentiate. Therefore, most of the time, this will be omitted.
 
-
 All parts can only contain:
 
-* Alphanumeric characters: `a-z` , `A-Z` , and `0-9`.
-* Underscores: `_`
-
+- Alphanumeric characters: `a-z` , `A-Z` , and `0-9`.
+- Underscores: `_`
 
 ### Examples
 
@@ -53,7 +53,7 @@ All parts can only contain:
 - `auto.db.core_data`
 - `auto.db.graphql`
 
-Origins of type `manual` can also have categories and integration names. For example, for the <Link to="/sdk/performance/time-to-initial-full-display/">time to display feature</Link>, the user manually calls an API  of the SDK,
+Origins of type `manual` can also have categories and integration names. For example, for the <Link to="/sdk/performance/time-to-initial-full-display/">time to display feature</Link>, the user manually calls an API of the SDK,
 creating a span. In this case, the SDK can tell what created the span, but the user did it manually. On the other hand, the SDK also
 automatically creates a span. In this case we end up with the following origins:
 
@@ -63,5 +63,8 @@ automatically creates a span. In this case we end up with the following origins:
 ## See also:
 
 - <Link to="/sdk/data-model/event-payloads/span/">Span Interface</Link>
-- <Link to="/sdk/data-model/event-payloads/contexts/#trace-context">Trace Context</Link>
+- <Link to="/sdk/data-model/event-payloads/contexts/#trace-context">
+    Trace Context
+  </Link>
+- <Link to="/sdk/telemetry/logs/">Logs Interface</Link>
 - Related [RFC](https://github.com/getsentry/rfcs/pull/73/);