feat(otlp): Add docs for OTLP logs endpoint

Author: AbhiPrasad

docs/concepts/otlp/index.mdx

@@ -5,14 +5,17 @@ description: "Learn how to send OpenTelemetry trace data directly to Sentry from
 keywords: ["otlp", "otel", "opentelemetry"]
 ---
 
+Sentry can ingest [OpenTelemetry](https://opentelemetry.io) traces and logs directly via the [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/). Sentry does not support ingesting OTLP metrics.
+
+## OpenTelemetry Traces
+
 <Include name="feature-available-alpha-otlp.mdx" />
 
-Sentry can ingest [OpenTelemetry](https://opentelemetry.io) traces directly via the  [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/). If you have an existing OpenTelemetry trace instrumentation, you can configure your OpenTelemetry exporter to send traces to Sentry directly. Sentry's OTLP ingestion endpoint is currently in development, and has a few known limitations:
+If you have an existing OpenTelemetry trace instrumentation, you can configure your OpenTelemetry exporter to send traces to Sentry directly. Sentry's OTLP ingestion traces endpoint is currently in development, and has a few known limitations:
 
 - Span events are not supported. All span events are dropped during ingestion.
 - Span links are partially supported. We ingest and display span links, but they cannot be searched, filtered, or aggregated. Links are are shown in the [Trace View](/concepts/key-terms/tracing/trace-view/).
 - Array attributes are partially supported. We ingest and display array attributes, but they cannot be searched, filtered, or aggregated. Array attributes are shown in the [Trace View](/concepts/key-terms/tracing/trace-view/).
-- Sentry does not support ingesting OTLP metrics or OTLP logs.
 
 The easiest way to configure an OpenTelemetry exporter is with environment variables. You'll need to configure the trace endpoint URL, as well as the authentication headers. Set these variables on the server where your application is running.
 
@@ -39,7 +42,50 @@ const sdk = new NodeSDK({
 sdk.start();
 ```
 
-You can find the values of Sentry's OTLP endpoint and public key in your Sentry project settings.
+You can find the values of Sentry's OTLP traces endpoint and public key in your Sentry project settings.
+
+1. Go to the [Settings > Projects](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/) page in Sentry.
+2. Select a project from the list.
+3. Go to the "Client Keys (DSN)" sub-page for this project under the "SDK Setup" heading.
+
+## OpenTelemetry Logs
+
+<Include name="feature-stage-beta.mdx" />
+
+If you have an existing OpenTelemetry log instrumentation, you can configure your OpenTelemetry exporter to send logs to Sentry directly. Sentry's OTLP ingestion logs endpoint has the following known limitations:
+
+- Array attributes are partially supported. We ingest and display array attributes, but they cannot be searched, filtered, or aggregated.
+
+The easiest way to configure an OpenTelemetry exporter is with environment variables. You'll need to configure the trace endpoint URL, as well as the authentication headers. Set these variables on the server where your application is running.
+
+```bash {filename: .env}
+export OTEL_EXPORTER_OTLP_LOGS_ENDPOINT="___OTLP_LOGS_URL___"
+export OTEL_EXPORTER_OTLP_LOGS_HEADERS="x-sentry-auth=sentry sentry_key=___PUBLIC_KEY___"
+```
+
+Alternatively, you can configure the OpenTelemetry Exporter directly in your application code. Here is an example with the OpenTelemetry Node SDK:
+
+```typescript {filename: app.ts}
+import {
+  LoggerProvider,
+  BatchLogRecordProcessor,
+} from "@opentelemetry/sdk-logs";
+import { OTLPLogExporter } from "@opentelemetry/exporter-logs-otlp-http";
+
+const logExporter = new OTLPLogExporter({
+  url: "___OTLP_LOGS_URL___",
+  headers: {
+    "x-sentry-auth": "sentry sentry_key=___PUBLIC_KEY___",
+  },
+});
+const loggerProvider = new LoggerProvider({
+  processors: [new BatchRecordProcessor(logExporter)],
+});
+
+const logger = loggerProvider.getLogger("default", "1.0.0");
+```
+
+You can find the values of Sentry's OTLP logs endpoint and public key in your Sentry project settings.
 
 1. Go to the [Settings > Projects](https://sentry.io/orgredirect/organizations/:orgslug/settings/projects/) page in Sentry.
 2. Select a project from the list.

src/components/codeContext.tsx

@@ -14,6 +14,7 @@ type ProjectCodeKeywords = {
   ORG_ID: number;
   ORG_INGEST_DOMAIN: string;
   ORG_SLUG: string;
+  OTLP_LOGS_URL: string;
   OTLP_TRACES_URL: string;
   PROJECT_ID: number;
   PROJECT_SLUG: string;
@@ -88,6 +89,7 @@ export const DEFAULTS: CodeKeywords = {
         'https://o0.ingest.sentry.io/api/0/minidump/?sentry_key=examplePublicKey',
       UNREAL_URL: 'https://o0.ingest.sentry.io/api/0/unreal/examplePublicKey/',
       OTLP_TRACES_URL: 'https://o0.ingest.sentry.io/api/0/otlp/v1/traces/',
+      OTLP_LOGS_URL: 'https://o0.ingest.sentry.io/api/0/otlp/v1/logs/',
       title: `example-org / example-project`,
     },
   ],
@@ -143,6 +145,10 @@ const formatOtlpTracesUrl = ({scheme, host, pathname}: Dsn) => {
   return `${scheme}${host}/api${pathname}/otlp/v1/traces/`;
 };
 
+const formatOtlpLogsUrl = ({scheme, host, pathname}: Dsn) => {
+  return `${scheme}${host}/api${pathname}/otlp/v1/logs/`;
+};
+
 const formatApiUrl = ({scheme, host}: Dsn) => {
   const apiHost = host.indexOf('.ingest.') >= 0 ? host.split('.ingest.')[1] : host;
 
@@ -236,6 +242,7 @@ export async function fetchCodeKeywords(): Promise<CodeKeywords> {
         MINIDUMP_URL: formatMinidumpURL(parsedDsn),
         UNREAL_URL: formatUnrealEngineURL(parsedDsn),
         OTLP_TRACES_URL: formatOtlpTracesUrl(parsedDsn),
+        OTLP_LOGS_URL: formatOtlpLogsUrl(parsedDsn),
         title: `${project.organizationSlug} / ${project.projectSlug}`,
       };
     }),