Merge branch 'master' into datadog-api-spec/generated/4041

Author: warthy

.apigentools-info

@@ -4,13 +4,13 @@
     "spec_versions": {
         "v1": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-07-21 13:22:51.945618",
-            "spec_repo_commit": "b7969cc2"
+            "regenerated": "2025-07-21 13:56:36.540795",
+            "spec_repo_commit": "06ccc326"
         },
         "v2": {
             "apigentools_version": "1.6.6",
-            "regenerated": "2025-07-21 13:23:01.041102",
-            "spec_repo_commit": "b7969cc2"
+            "regenerated": "2025-07-21 13:56:45.594812",
+            "spec_repo_commit": "06ccc326"
         }
     }
 }

assets/scripts/datadog-docs.js

@@ -153,7 +153,7 @@ function getVisibleParentPath(ancestralEl, path){
 function hasParentLi(el) {
     while (el) {
         if (el.classList) {
-            if (el.classList.contains('sidenav-nav-main')) {
+            if (el.classList.contains('sidenav-nav-js-load')) {
                 break;
             }
 
@@ -174,7 +174,7 @@ function hasParentLi(el) {
 
 function getPathElement(event = null) {
     let path = window.location.pathname;
-    const activeMenus = document.querySelectorAll('.side .sidenav-nav-main .active, header .sidenav-nav-main .active');
+    const activeMenus = document.querySelectorAll('.side .sidenav-nav-js-load .active, header .sidenav-nav-js-load .active');
 
     // remove active class from all sidenav links to close all open menus
     for (let i = 0; i < activeMenus.length; i++) {
@@ -237,8 +237,8 @@ function getPathElement(event = null) {
 
 // remove open class from li elements and active class from <a> elements
 function closeNav() {
-    const activeMenus = document.querySelectorAll('.side .sidenav-nav-main .active, header .sidenav-nav-main .active');
-    const openMenus = document.querySelectorAll('.side .sidenav-nav-main .open, header .sidenav-nav-main .open');
+    const activeMenus = document.querySelectorAll('.side .sidenav-nav-js-load .active, header .sidenav-nav-js-load .active');
+    const openMenus = document.querySelectorAll('.side .sidenav-nav-js-load .open, header .sidenav-nav-js-load .open');
 
     for (let i = 0; i < activeMenus.length; i++) {
         activeMenus[i].classList.remove('active');
@@ -293,8 +293,8 @@ function updateSidebar(event) {
     }
 }
 
-const sideNav = document.querySelector('.side .sidenav-nav-main');
-const mobileNav = document.querySelector('header .sidenav-nav-main');
+const sideNav = document.querySelector('.side .sidenav-nav-js-load');
+const mobileNav = document.querySelector('header .sidenav-nav-js-load');
 
 if (sideNav) {
     sideNav.addEventListener('click', navClickEventHandler);

content/en/agent/guide/private-link.md

@@ -144,7 +144,10 @@ After the endpoint status is updated to **Available**, you can use this endpoint
 | Database Monitoring       | {{< region-param key="aws_private_link_dbm_service_name" code="true" >}}               | {{< region-param key="dbm_endpoint_private_link" code="true" >}}        |
 | Remote Configuration      | {{< region-param key="aws_private_link_remote_config_service_name" code="true" >}}     | {{< region-param key="remote_config_endpoint_private_link" code="true" >}}     |
 
+**Note**: Cross-region PrivateLink doesn't emit CloudWatch metrics. See [CloudWatch metrics for AWS PrivateLink][2] for more information.
+
 [1]: /help/
+[2]: https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-cloudwatch-metrics.html
 {{% /tab %}}
 
 {{% tab "VPC Peering" %}}
@@ -278,7 +281,6 @@ The VPCs with Private Hosted Zone (PHZ) attached need to have a couple of settin
 
 3. [Restart the Agent][7].
 
-
 [1]: /help/
 [2]: https://docs.aws.amazon.com/vpc/latest/peering/working-with-vpc-peering.html
 [3]: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-private.html
@@ -302,6 +304,37 @@ The VPCs with Private Hosted Zone (PHZ) attached need to have a couple of settin
 
 {{% /site-region %}}
 
+## Verify that data is being sent using PrivateLink
+
+After setting up PrivateLink, to verify that data is getting sent using PrivateLink, run the `dig` command on a machine that is on that VPC. For example, run this command if you had set up a PrivateLink for the endpoint `http-intake.logs.datadoghq.com`:
+
+```
+dig http-intake.logs.datadoghq.com
+```
+
+If logs are being sent over PrivateLink, the `ANSWER Section` section of the output shows `http-intake.logs.datadoghq.com` like in the following example. **Note**: The IP addresses you get back should be in [private IP space][1].
+
+```
+;; ANSWER SECTION:
+http-intake.logs.datadoghq.com.	60 IN	A	172.31.57.3
+http-intake.logs.datadoghq.com.	60 IN	A	172.31.3.10
+http-intake.logs.datadoghq.com.	60 IN	A	172.31.20.174
+http-intake.logs.datadoghq.com.	60 IN	A	172.31.34.135
+```
+
+If logs are not being sent over PrivateLink, the `ANSWER SECTION` of the output shows the load balancer (`4-logs-http-s1-e721f9c2a0e65948.elb.us-east-1.amazonaws.com`) to which the logs are getting sent.
+
+```
+;; ANSWER SECTION:
+http-intake.logs.datadoghq.com.	177 IN	CNAME	http-intake-l4.logs.datadoghq.com.
+http-intake-l4.logs.datadoghq.com. 173 IN CNAME	l4-logs-http-s1-e721f9c2a0e65948.elb.us-east-1.amazonaws.com.
+l4-logs-http-s1-e721f9c2a0e65948.elb.us-east-1.amazonaws.com. 42 IN A 3.233.158.48
+l4-logs-http-s1-e721f9c2a0e65948.elb.us-east-1.amazonaws.com. 42 IN A 3.233.158.49
+l4-logs-http-s1-e721f9c2a0e65948.elb.us-east-1.amazonaws.com. 42 IN A 3.233.158.50
+```
+
 ## Further reading
 
 {{< partial name="whats-next/whats-next.html" >}}
+
+[1]: https://en.wikipedia.org/wiki/Private_network#Private_IPv4_addresses