merge master

Author: maycmlee

config/_default/menus/main.en.yaml

@@ -2196,6 +2196,11 @@ menu:
       parent: idp_eng_reports
       identifier: eng_reports_dora_metrics
       weight: 403
+    - name: Custom Reports
+      url: internal_developer_portal/eng_reports/custom_reports
+      parent: idp_eng_reports
+      identifier: eng_reports_custom
+      weight: 404
     - name: Developer Homepage
       url: internal_developer_portal/developer_homepage
       parent: internal_developer_portal
@@ -3661,26 +3666,21 @@ menu:
       parent: nm_parent
       identifier: cnm
       weight: 1
-    - name: CNM Terms and Concepts
-      url: network_monitoring/cloud_network_monitoring/glossary
-      parent: cnm
-      identifier: cnm_glossary
-      weight: 101
     - name: Setup
       url: network_monitoring/cloud_network_monitoring/setup/
       parent: cnm
       identifier: cnm_setup
-      weight: 102
+      weight: 101
     - name: Network Health
       url: network_monitoring/cloud_network_monitoring/network_health/
       parent: cnm
       identifier: cnm_network_health
-      weight: 103 
+      weight: 102 
     - name: Network Analytics
       url: network_monitoring/cloud_network_monitoring/network_analytics/
       parent: cnm
       identifier: cnm_analytics
-      weight: 104
+      weight: 103
     - name: Tags Reference
       url: network_monitoring/cloud_network_monitoring/tags_reference/
       parent: cnm_analytics
@@ -3690,17 +3690,22 @@ menu:
       url: network_monitoring/cloud_network_monitoring/network_map/
       parent: cnm
       identifier: cnm_map
-      weight: 105
+      weight: 104
     - name: Guides
       url: network_monitoring/cloud_network_monitoring/guide/
       identifier: cnm_guides
       parent: cnm
-      weight: 106
+      weight: 105
     - name: Supported Cloud Services
       url: network_monitoring/cloud_network_monitoring/supported_cloud_services/
       identifier: cnm_supported_cloud_services
       parent: cnm
-      weight: 10601 
+      weight: 106
+    - name: Terms and Concepts
+      url: network_monitoring/cloud_network_monitoring/glossary
+      parent: cnm
+      identifier: cnm_glossary
+      weight: 107
     - name: DNS Monitoring
       url: network_monitoring/dns/
       parent: nm_parent
@@ -3711,81 +3716,81 @@ menu:
       parent: nm_parent
       identifier: ndm
       weight: 3      
-    - name: NDM Terms and Concepts
-      url: network_monitoring/devices/glossary
-      parent: ndm
-      identifier: ndm_glossary
-      weight: 301
     - name: Setup
       url: network_monitoring/devices/setup
       parent: ndm
       identifier: ndm_setup
-      weight: 302
+      weight: 301
     - name: Supported Devices
       url: network_monitoring/devices/supported_devices
       parent: ndm_setup
       identifier: ndm_supported_devices
-      weight: 30301
+      weight: 30101 
     - name: SNMP Metrics
       url: network_monitoring/devices/snmp_metrics
       parent: ndm_setup
       identifier: ndm_snmp_metrics
-      weight: 30302
+      weight: 30102
     - name: SNMP Traps
       url: network_monitoring/devices/snmp_traps
       parent: ndm_setup
       identifier: ndm_snmptraps
-      weight: 30303
+      weight: 30103
     - name: Ping
       url: network_monitoring/devices/ping
       parent: ndm_setup
       identifier: ndm_snmp_ping
-      weight: 30304
+      weight: 30104
     - name: Syslog
       url: network_monitoring/devices/syslog
       parent: ndm_setup
       identifier: ndm_syslog
-      weight: 30305
+      weight: 30105
     - name: VPN Monitoring
       url: network_monitoring/devices/vpn_monitoring
       parent: ndm_setup
       identifier: ndm_vpn_monitoring
-      weight: 30306
+      weight: 30106
     - name: Integrations
       url: network_monitoring/devices/integrations
       parent: ndm
       identifier: ndm_integrations
-      weight: 304
+      weight: 302
     - name: Profiles
       url: network_monitoring/devices/profiles
       parent: ndm
       identifier: ndm_profiles
-      weight: 305
+      weight: 303
     - name: Configuration Management
       url: network_monitoring/devices/config_management
       parent: ndm
       identifier: ndm_config_management
-      weight: 306   
+      weight: 304   
     - name: Maps
       url: network_monitoring/devices/topology
       parent: ndm
       identifier: ndm_network_maps
-      weight: 307
+      weight: 305
     - name: SNMP Metrics Reference
       url: network_monitoring/devices/data
       parent: ndm
       identifier: ndm_data
-      weight: 308
+      weight: 306
     - name: Troubleshooting
       url: network_monitoring/devices/troubleshooting
       parent: ndm
       identifier: ndm_trouble
-      weight: 309
+      weight: 307
     - name: Guides
       url: network_monitoring/devices/guide/
       parent: ndm
       identifier: ndm_guide
-      weight: 310
+      weight: 308
+    - name: Terms and Concepts
+      url: network_monitoring/devices/glossary
+      parent: ndm
+      identifier: ndm_glossary
+      weight: 309
     - name: NetFlow Monitoring
       url: /network_monitoring/netflow/
       parent: nm_parent
@@ -3801,11 +3806,6 @@ menu:
       parent: nm_parent
       identifier: network_path
       weight: 5
-    - name: Terms and Concepts
-      url: network_monitoring/network_path/glossary
-      parent: network_path
-      identifier: network_path_glossary
-      weight: 501 
     - name: Setup
       url: network_monitoring/network_path/setup/
       parent: network_path
@@ -3826,6 +3826,11 @@ menu:
       parent: network_path
       identifier: network_path_guides
       weight: 505
+    - name: Terms and Concepts
+      url: network_monitoring/network_path/glossary
+      parent: network_path
+      identifier: network_path_glossary
+      weight: 506 
     - name: Storage Management
       url: /infrastructure/storage_management/
       pre: file-wui
@@ -6752,7 +6757,7 @@ menu:
       parent: cloud_siem_ingest_and_enrich
       identifier: cloud_siem_content_packs
       weight: 101
-    - name: Threat Intelligence
+    - name: Bring Your Own Threat Intelligence
       url: security/cloud_siem/ingest_and_enrich/threat_intelligence
       parent: cloud_siem_ingest_and_enrich
       identifier: cloud_siem_threat_intelligence
@@ -6847,11 +6852,16 @@ menu:
       parent: cloud_siem_triage_and_investigate
       identifier: cloud_siem_entities_and_risk_scoring
       weight: 302
+    - name: IOC Explorer
+      url: security/cloud_siem/triage_and_investigate/ioc_explorer
+      parent: cloud_siem_triage_and_investigate
+      identifier: cloud_siem_ioc_explorer
+      weight: 303
     - name: Investigator
       url: security/cloud_siem/triage_and_investigate/investigator
       parent: cloud_siem_triage_and_investigate
       identifier: cloud_siem_investigator
-      weight: 303
+      weight: 304
     - name: Respond and Report
       url: security/cloud_siem/respond_and_report
       parent: cloud_siem

content/en/account_management/audit_trail/_index.md

@@ -174,7 +174,7 @@ Log management users can audit API key usage with Audit Trail. For API key audit
 
 ## Create a monitor
 
-To create a monitor on a type of audit trail event or by specificTrail attributes, see the [Audit Trail Monitor documentation][7]. For example, set a monitor that triggers when a specific user logs in, or set a monitor for anytime a dashboard is deleted.
+To create a monitor on a type of audit trail event or by specific Audit Trail attributes, see the [Audit Trail Monitor documentation][7]. For example, set a monitor that triggers when a specific user logs in, or set a monitor for anytime a dashboard is deleted.
 
 ## Create a dashboard or a graph
 

content/en/account_management/teams/_index.md

@@ -1,6 +1,12 @@
 ---
 title: Teams
 description: Organize team assets, filter Datadog experiences, and manage team membership with team handles, notifications, and resource associations.
+
+further_reading:
+  - link: https://www.datadoghq.com/blog/datadog-teams-github-integration
+    tag: Blog
+    text: Keep service ownership up to date with Datadog Teams' GitHub integration
+
 ---
 
 ## Overview

content/en/account_management/teams/github.md

@@ -5,6 +5,9 @@ further_reading:
     - link: '/integrations/github/'
       tag: 'Documentation'
       text: 'GitHub integration'
+    - link: https://www.datadoghq.com/blog/datadog-teams-github-integration
+      tag: Blog
+      text: Keep service ownership up to date with Datadog Teams' GitHub integration
 ---
 
 ## Overview

content/en/api/v1/usage-metering/examples.json

@@ -31,6 +31,9 @@ further_reading:
     - link: 'https://www.datadoghq.com/blog/watermark-pod-autoscaler/'
       tag: 'Blog'
       text: 'A guide on scaling out your Kubernetes pods with the Watermark Pod Autoscaler'
+    - link: https://www.datadoghq.com/blog/kubernetes-operator-performance
+      tag: Blog
+      text: Monitor your Kubernetes operators to keep applications running smoothly
 ---
 
 

content/en/api/v2/observability-pipelines/examples.json

@@ -8,6 +8,9 @@ aliases:
     - /agent/prometheus
     - /agent/kubernetes/prometheus
 further_reading:
+- link: https://www.datadoghq.com/blog/kubernetes-operator-performance
+  tag: Blog
+  text: Monitor your Kubernetes operators to keep applications running smoothly
 - link: "/agent/kubernetes/log/"
   tag: "Documentation"
   text: "Collect your application logs"

content/en/containers/kubernetes/_index.md

@@ -37,19 +37,8 @@ You can start your investigation from any timeseries graph that uses metric data
 
 This opens a full-screen investigation view. Watchdog analyzes the anomaly and surfaces any tag groups that significantly contributed to the shape or scale of the anomaly. Click on a tag to see how removing or isolating that dimension affects the graph. Use this to identify root causes like specific customers, services, or environments.
 
-## Example: Surge in traffic from a single tenant
-
-A spike in traffic is detected in the `shopist-returns` service. Watchdog surfaces a sharp increase in request volume, highlighted on the graph. Upon investigation, it attributes the anomaly to a single tag group: `org_id:17728`
-
-A spike in **Shopist Checkout Latency** is quickly explained by Watchdog: the `/apply-coupon` route in `eu-west-1` is the driver. This suggests that customers in that region experienced delays or were blocked when applying discount codes, directly impacting their ability to complete purchases.
-
-{{< img src="/dashboards/graph_insights/watchdog_explains/isolation_root_cause.png" alt="Example of Watchdog Explains highlighting a root cause in a timeseries graph" style="width:100%;" >}}
-
-At the same time, **Shopist Payment Error Rate** climbs. Watchdog Explains attributes the spike to `payment_provider:adyen` and a recent code change (`version:2025.08.14`). The release introduced errors that prevented some customers from completing payments, resulting in failed checkouts and revenue loss.
-
 {{< img src="/dashboards/graph_insights/watchdog_explains/isolation_tag_breakdown.png" alt="Tag breakdown in Watchdog Explains investigation" style="width:100%;" >}}
 
-By automatically surfacing these contributors, Watchdog Explains narrowed the root cause from "checkout is slow" to "coupon submissions in eu-west-1 failed due to a recent code change on Adyen." This clarity enabled a quick rollback and helped restore reliability.
 
 ## Disabling anomaly detection
 

content/en/containers/kubernetes/prometheus.md

@@ -11,18 +11,19 @@ further_reading:
       tag: 'Blog'
       text: 'Autodiscover Confluent Cloud connectors and easily monitor performance in Data Streams Monitoring'
 aliases:
-  - /data_streams/python
+    - /data_streams/python
 ---
 
 ### Prerequisites
 
-* [Datadog Agent v7.34.0 or later][10]
+-   [Datadog Agent v7.34.0 or later][10]
 
 ### Supported libraries
 
-| Technology     | Library                                                      | Minimal tracer version                                                        | Recommended tracer version                                                        | Minimal Lambda Library Version |
-|----------------|--------------------------------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|--------------------------------|
+| Technology     | Library                                                      | Minimal tracer version                                                        | Recommended tracer version                                                        | Minimal Lambda Library Version                                                |
+| -------------- | ------------------------------------------------------------ | ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
 | Kafka          | [confluent-kafka](https://pypi.org/project/confluent-kafka/) | {{< dsm-tracer-version lang="python" lib="confluent-kafka" type="minimal" >}} | {{< dsm-tracer-version lang="python" lib="confluent-kafka" type="recommended" >}} | [112](https://github.com/DataDog/datadog-lambda-python/releases/tag/v7.112.0) |
+| Kafka          | [aiokafka](https://pypi.org/project/aiokafka/)               | {{< dsm-tracer-version lang="python" lib="aiokafka" type="minimal" >}}        | {{< dsm-tracer-version lang="python" lib="aiokafka" type="recommended" >}}        | Not supported                                                                 |
 | RabbitMQ       | [Kombu](https://pypi.org/project/kombu/)                     | {{< dsm-tracer-version lang="python" lib="kombu" type="minimal" >}}           | {{< dsm-tracer-version lang="python" lib="kombu" type="recommended" >}}           | [112](https://github.com/DataDog/datadog-lambda-python/releases/tag/v7.112.0) |
 | Amazon SQS     | [Botocore](https://pypi.org/project/botocore/)               | {{< dsm-tracer-version lang="python" lib="botocore" type="minimal" >}}        | {{< dsm-tracer-version lang="python" lib="botocore" type="recommended" >}}        | [112](https://github.com/DataDog/datadog-lambda-python/releases/tag/v7.112.0) |
 | Amazon Kinesis | [Botocore](https://pypi.org/project/botocore/)               | {{< dsm-tracer-version lang="python" lib="botocore" type="minimal" >}}        | {{< dsm-tracer-version lang="python" lib="botocore" type="recommended" >}}        | [112](https://github.com/DataDog/datadog-lambda-python/releases/tag/v7.112.0) |
@@ -33,10 +34,11 @@ aliases:
 Python uses auto-instrumentation to inject and extract additional metadata required by Data Streams Monitoring for measuring end-to-end latencies and the relationship between queues and services. To enable Data Streams Monitoring, set the `DD_DATA_STREAMS_ENABLED` environment variable to `true` on services sending messages to (or consuming messages from) Kafka.
 
 For example:
+
 ```yaml
 environment:
-  - DD_DATA_STREAMS_ENABLED: "true"
-  - DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED: "true"
+    - DD_DATA_STREAMS_ENABLED: 'true'
+    - DD_TRACE_REMOVE_INTEGRATION_SERVICE_NAMES_ENABLED: 'true'
 ```
 
 {{% data_streams/monitoring-kafka-pipelines %}}
@@ -50,11 +52,13 @@ environment:
 {{% data_streams/monitoring-sns-to-sqs-pipelines %}}
 
 ### Manual instrumentation
+
 Data Streams Monitoring propagates context through message headers. If you are using a message queue technology that is not supported by DSM, a technology without headers (such as Kinesis), use [manual instrumentation to set up DSM][6].
 
 ### Monitoring connectors
 
 #### Confluent Cloud connectors
+
 {{% data_streams/dsm-confluent-connectors %}}
 
 ## Further reading