better vector docs

Author: AbhiPrasad

docs/product/drains/integration/vector.mdx

@@ -6,17 +6,11 @@ description: Learn how to set up Vector to forward logs to Sentry via OpenTeleme
 
 You can configure [Vector](https://vector.dev/) to forward logs to Sentry using its [OpenTelemetry sink](https://vector.dev/docs/reference/configuration/sinks/opentelemetry/).
 
-<Alert level="warning">
-
-Vector's OpenTelemetry sink requires events to conform to the [OTEL proto format](https://opentelemetry.io/docs/specs/otlp/). You must use the [remap transform](https://vector.dev/docs/reference/configuration/transforms/remap/) with VRL (Vector Remap Language) to convert your log data into the proper OpenTelemetry structure before sending to Sentry.
-
-</Alert>
-
 ## Prerequisites
 
 Before you begin, ensure you have:
 
-- Vector installed and running
+- Vector installed and running (version 0.51.0 or higher for `otlp` codec support)
 - A Sentry project you want to send data to
 
 ## Step 1: Get Your Sentry OTLP Credentials
@@ -37,15 +31,53 @@ x-sentry-auth: sentry sentry_key=___PUBLIC_KEY___
 
 ## Step 2: Configure Vector
 
-Vector configuration requires three components:
+Choose your configuration based on your data source:
 
-1. **Source**: Where your logs come from (files, syslog, etc.)
-2. **Transform**: A remap transform to convert logs to OTEL format
-3. **Sink**: The OpenTelemetry sink to send data to Sentry
+- **Option A**: Forwarding existing OTLP data (simplest)
+- **Option B**: Transforming non-OTLP data (files, syslog, etc.)
+
+## Option A: Forwarding OTLP Data
+
+If you're receiving data that's already in OTLP format (from an OpenTelemetry SDK or collector), you can forward it directly to Sentry using the `otlp` codec without any transformation.
+
+```yaml {filename:vector.yaml}
+sources:
+  otel_source:
+    type: opentelemetry
+    grpc:
+      address: 0.0.0.0:4317
+    http:
+      address: 0.0.0.0:4318
+    use_otlp_decoding: true
+
+sinks:
+  sentry_logs:
+    inputs:
+      - otel_source.logs
+    type: opentelemetry
+    protocol:
+      type: http
+      uri: ___OTLP_LOGS_URL___
+      method: post
+      headers:
+        x-sentry-auth: "sentry sentry_key=___PUBLIC_KEY___"
+      encoding:
+        codec: otlp
+```
+
+<Alert level="info">
+
+The `otlp` codec requires Vector version [0.51.0](https://vector.dev/releases/0.51.0/) or higher. The `use_otlp_decoding` option was introduced in Vector [0.50.0](https://vector.dev/releases/0.50.0/).
+
+</Alert>
+
+## Option B: Transforming Non-OTLP Data
+
+If your logs come from non-OTLP sources (files, syslog, etc.), you need to use a [remap transform](https://vector.dev/docs/reference/configuration/transforms/remap/) with VRL (Vector Remap Language) to convert your data into the OTEL format before sending to Sentry.
 
 ### Understanding the OTEL Log Format
 
-The OpenTelemetry log format requires a specific structure with `resourceLogs`, `scopeLogs`, and `logRecords`. Here's the structure you need to create:
+The OpenTelemetry log format requires a specific structure with `resourceLogs`, `scopeLogs`, and `logRecords`:
 
 ```json
 {
@@ -74,7 +106,7 @@ The OpenTelemetry log format requires a specific structure with `resourceLogs`,
 }
 ```
 
-## Example: Forwarding File Logs
+### Example: Forwarding File Logs
 
 Here's a complete example that reads logs from a file and forwards them to Sentry:
 
@@ -134,14 +166,11 @@ sinks:
       method: post
       headers:
         x-sentry-auth: "sentry sentry_key=___PUBLIC_KEY___"
-        content-type: "application/json"
       encoding:
-        codec: json
-      framing:
-        method: newline_delimited
+        codec: otlp
 ```
 
-## Example: Forwarding Syslog
+### Example: Forwarding Syslog
 
 For syslog data, you can map severity levels to OTEL severity:
 
@@ -218,11 +247,8 @@ sinks:
       method: post
       headers:
         x-sentry-auth: "sentry sentry_key=___PUBLIC_KEY___"
-        content-type: "application/json"
       encoding:
-        codec: json
-      framing:
-        method: newline_delimited
+        codec: otlp
 ```
 
 ## VRL Remap Reference
@@ -247,7 +273,7 @@ Here are the key VRL functions you'll use when building OTEL log records:
 | `protocol.type`           | Transport protocol (`http`)                  | Yes      |
 | `protocol.uri`            | Your Sentry OTLP logs endpoint               | Yes      |
 | `protocol.headers`        | HTTP headers including authentication        | Yes      |
-| `protocol.encoding.codec` | Encoding format (`json`)                     | Yes      |
+| `protocol.encoding.codec` | Must be `otlp` for OpenTelemetry encoding    | Yes      |
 
 ### OTEL Log Record Fields
 
@@ -262,16 +288,18 @@ Here are the key VRL functions you'll use when building OTEL log records:
 
 ### Logs Not Appearing in Sentry
 
-1. **Check the OTEL structure**: Ensure your remap transform creates the correct `resourceLogs` structure with all required nested fields.
+1. **Check Vector version**: The `otlp` codec requires Vector 0.51.0+. Run `vector --version` to verify.
+
+2. **Check the OTEL structure**: If using remap, ensure your transform creates the correct `resourceLogs` structure with all required nested fields.
 
-2. **Verify timestamps**: The `timeUnixNano` field must be a valid Unix timestamp in nanoseconds.
+3. **Verify timestamps**: The `timeUnixNano` field must be a valid Unix timestamp in nanoseconds.
 
-3. **Enable Vector debug logging**: Run Vector with debug logging to see the transformed events:
+4. **Enable Vector debug logging**: Run Vector with debug logging to see the transformed events:
 
    ```bash
    VECTOR_LOG=debug vector --config /path/to/vector.yaml
    ```
 
-4. **Validate your VRL**: Use [Vector's VRL playground](https://playground.vrl.dev/) to test your remap logic.
+5. **Validate your VRL**: Use [Vector's VRL playground](https://playground.vrl.dev/) to test your remap logic.
 
 For more information on Vector configuration options, see the [Vector documentation](https://vector.dev/docs/reference/configuration/).