ref(logs): Change documentation for logs sentry.origin consolidation

develop-docs/sdk/telemetry/logs.mdx

@@ -305,13 +305,20 @@ If there are no `sentry.message.parameter.X` attributes included in the log, the
 
 #### SDK Integration Attributes
 
-If a log is generated by an SDK integration, the SDK should also set the `sentry.origin` attribute, as per the [Trace Origin](/sdk/telemetry/traces/trace-origin/) documentation. It is assumed that logs without a `sentry.origin` attribute are manually created by the user.
+If a log is generated by an SDK integration, the SDK should also set the `sentry.origin` attribute, as per the [Trace Origin](/sdk/telemetry/traces/trace-origin/) documentation.
 
-```json
-{
-  "sentry.origin": "auto.db.graphql"
-}
-```
+Logs can be generated in three ways:
+
+1. User calls Sentry’s Logging API directly: No `sentry.origin`.
+
+2. Captured from a logging library: Use `auto.log.<name>` format. where `<name>` is the relevant integration. For example, the .NET Serilog library emits:
+  ```json
+  { "sentry.origin": "auto.log.serilog" }
+  ```
+3. Auto-emitted logs from other instrumented systems: Use the matching trace origin category (e.g. db, http, etc.).
+  ```json
+  { "sentry.origin": "auto.db.prisma" }
+  ```
 
 #### User Attributes
 

develop-docs/sdk/telemetry/traces/span-operations.mdx

@@ -265,6 +265,7 @@ Messages/Queue spans are expected follow OpenTelemetry's [Messaging](https://git
 | graphql    |             |
 | grpc       |             |
 | http       |             |
+| log        |             |
 | mark       |             |
 | measure    |             |
 | middleware |             |