docs: add Datadog integration guide with importable operations dashboard (#6225)

Adds a consolidated `datadog.mdx` under `docs/edge/{en,pt-BR,ko,ar}/enterprise/guides/`
covering both the Datadog Agent path (stdout JSON logs via `CREWAI_LOG_FORMAT=json`)
and the Datadog OTLP intake, with a JSON log schema reference and a ready-to-import
operations dashboard (`datadog_dashboard.json`). Reframes `capture_telemetry_logs.mdx`
to lead with OpenTelemetry as the vendor-neutral path and point readers to the new
Datadog page for that ecosystem's setup.

Author: lucasgomide

docs/docs.json

@@ -515,6 +515,7 @@
                       "edge/en/enterprise/guides/update-crew",
                       "edge/en/enterprise/guides/enable-crew-studio",
                       "edge/en/enterprise/guides/capture_telemetry_logs",
+                      "edge/en/enterprise/guides/datadog",
                       "edge/en/enterprise/guides/azure-openai-setup",
                       "edge/en/enterprise/guides/vertex-ai-workload-identity-setup",
                       "edge/en/enterprise/guides/tool-repository",
@@ -8647,6 +8648,7 @@
                       "edge/pt-BR/enterprise/guides/update-crew",
                       "edge/pt-BR/enterprise/guides/enable-crew-studio",
                       "edge/pt-BR/enterprise/guides/capture_telemetry_logs",
+                      "edge/pt-BR/enterprise/guides/datadog",
                       "edge/pt-BR/enterprise/guides/azure-openai-setup",
                       "edge/pt-BR/enterprise/guides/tool-repository",
                       "edge/pt-BR/enterprise/guides/custom-mcp-server",
@@ -16510,6 +16512,7 @@
                       "edge/ko/enterprise/guides/update-crew",
                       "edge/ko/enterprise/guides/enable-crew-studio",
                       "edge/ko/enterprise/guides/capture_telemetry_logs",
+                      "edge/ko/enterprise/guides/datadog",
                       "edge/ko/enterprise/guides/azure-openai-setup",
                       "edge/ko/enterprise/guides/tool-repository",
                       "edge/ko/enterprise/guides/custom-mcp-server",
@@ -24565,6 +24568,7 @@
                       "edge/ar/enterprise/guides/update-crew",
                       "edge/ar/enterprise/guides/enable-crew-studio",
                       "edge/ar/enterprise/guides/capture_telemetry_logs",
+                      "edge/ar/enterprise/guides/datadog",
                       "edge/ar/enterprise/guides/azure-openai-setup",
                       "edge/ar/enterprise/guides/tool-repository",
                       "edge/ar/enterprise/guides/custom-mcp-server",

docs/edge/ar/enterprise/guides/capture_telemetry_logs.mdx

@@ -9,6 +9,10 @@ mode: "wide"
 
 تتبع بيانات القياس [اتفاقيات OpenTelemetry GenAI الدلالية](https://opentelemetry.io/docs/specs/semconv/gen-ai/) بالإضافة إلى سمات خاصة بـ CrewAI.
 
+<Tip>
+تُعدّ OpenTelemetry **مسار المراقبة الموصى به** — محايدة تجاه الموردين، وتعمل مع أي خلفية متوافقة مع OTLP (Grafana, Honeycomb, NewRelic، أو مجمّعك الخاص). إذا كنت تستخدم Datadog تحديدًا، فراجع دليل [تكامل Datadog](./datadog) المخصص، الذي يغطي كلًا من مسار وكيل Datadog واستيعاب OTLP من Datadog.
+</Tip>
+
 ## المتطلبات المسبقة
 
 <CardGroup cols={2}>
@@ -41,17 +45,7 @@ mode: "wide"
     <Frame>![تهيئة مجمّع OpenTelemetry](/images/crewai-otel-collector-opentelemetry.png)</Frame>
   </Tab>
   <Tab title="Datadog">
-    - **Datadog Site Domain** — مضيف OTLP لموقع Datadog الخاص بك فقط، دون بروتوكول أو مسار. يقوم CrewAI ببناء نقطة نهاية HTTPS OTLP الكاملة نيابةً عنك. استخدم المضيف المطابق لـ [موقع Datadog](https://docs.datadoghq.com/getting_started/site/) الخاص بك:
-      - `otlp.datadoghq.com` (US1)
-      - `otlp.us3.datadoghq.com` (US3)
-      - `otlp.us5.datadoghq.com` (US5)
-      - `otlp.datadoghq.eu` (EU1)
-      - `otlp.ap1.datadoghq.com` (AP1)
-    - **API Key** — مفتاح واجهة برمجة تطبيقات Datadog الخاص بك. راجع [كيفية إنشاء واحد](https://docs.datadoghq.com/account_management/api-app-keys/#api-keys).
-
-    يصدّر تكامل Datadog **التتبعات**.
-
-    <Frame>![تهيئة مجمّع Datadog](/images/crewai-otel-collector-datadog.png)</Frame>
+    لإعداد Datadog، راجع دليل [تكامل Datadog](./datadog) المخصص — فهو يغطي كلًا من مسار وكيل Datadog (الموصى به، أرخص لحجم السجلات الكبير) واستيعاب OTLP من Datadog، مع خطوات تهيئة كاملة للمجمّع.
   </Tab>
 </Tabs>
 

docs/edge/ar/enterprise/guides/datadog.mdx

@@ -9,6 +9,10 @@ CrewAI AMP can export OpenTelemetry **traces** and **logs** from your deployment
 
 Telemetry data follows the [OpenTelemetry GenAI semantic conventions](https://opentelemetry.io/docs/specs/semconv/gen-ai/) plus additional CrewAI-specific attributes.
 
+<Tip>
+OpenTelemetry is the **recommended observability path** — vendor-neutral, works with any OTLP-compatible backend (Grafana, Honeycomb, NewRelic, your own collector). If you specifically use Datadog, see the dedicated [Datadog Integration](./datadog) guide which covers both the Datadog Agent path and Datadog's OTLP intake.
+</Tip>
+
 ## Prerequisites
 
 <CardGroup cols={2}>
@@ -41,17 +45,7 @@ Telemetry data follows the [OpenTelemetry GenAI semantic conventions](https://op
     <Frame>![OpenTelemetry collector configuration](/images/crewai-otel-collector-opentelemetry.png)</Frame>
   </Tab>
   <Tab title="Datadog">
-    - **Datadog Site Domain** — Your Datadog site's OTLP host only, with no protocol or path. CrewAI builds the full HTTPS OTLP endpoint for you. Use the host that matches your [Datadog site](https://docs.datadoghq.com/getting_started/site/):
-      - `otlp.datadoghq.com` (US1)
-      - `otlp.us3.datadoghq.com` (US3)
-      - `otlp.us5.datadoghq.com` (US5)
-      - `otlp.datadoghq.eu` (EU1)
-      - `otlp.ap1.datadoghq.com` (AP1)
-    - **API Key** — Your Datadog API key. See [how to create one](https://docs.datadoghq.com/account_management/api-app-keys/#api-keys).
-
-    The Datadog integration exports **traces**.
-
-    <Frame>![Datadog collector configuration](/images/crewai-otel-collector-datadog.png)</Frame>
+    For Datadog setup, see the dedicated [Datadog Integration](./datadog) guide — it covers both the Datadog Agent path (recommended, cheaper for log volume) and Datadog's OTLP intake with full collector configuration steps.
   </Tab>
 </Tabs>