diff --git a/content/en/monitors/notify/variables.md b/content/en/monitors/notify/variables.md
index 63785f72121..a1f5eb14b26 100644
--- a/content/en/monitors/notify/variables.md
+++ b/content/en/monitors/notify/variables.md
@@ -380,6 +380,38 @@ For Docs and Links you can also access a specific item with the following syntax
 ```
 {{% /collapse-content %}}
 
+
+{{% collapse-content title="Query group by device_ip and device_namespace" level="h5" %}}
+
+If your monitor triggers an alert for each `device_ip` and `device_namespace`, then you can access any attribute of the network device.
+
+Network device metadata variables:
+- Canonical ID: `{{network_device.canonical_id}}`
+- Description: `{{network_device.description}}`
+- Device type: `{{network_device.device_type}}`
+- Device ID: `{{network_device.device_id}}`
+- ID tags: `{{network_device.id_tags}}`
+- Integrations: `{{network_device.integrations}}`
+- IP address: `{{network_device.ip_address}}`
+- location: `{{network_device.location}}`
+- model: `{{network_device.model}}`
+- name: `{{network_device.name}}`
+- namespace: `{{network_device.namespace}}`
+- OS hostname: `{{network_device.os_hostname}}`
+- OS name: `{{network_device.os_name}}`
+- OS version: `{{network_device.os_version}}`
+- Ping status: `{{network_device.ping_status}}`
+- Product name: `{{network_device.product_name}}`
+- Profile: `{{network_device.profile}}`
+- Serial number: `{{network_device.serial_number}}`
+- Status: `{{network_device.status}}`
+- Subnet: `{{network_device.subnet}}`
+- Sys object ID: `{{network_device.sys_object_id}}`
+- Tags: `{{network_device.tags}}`
+- Vendor: `{{network_device.vendor}}`
+- Version: `{{network_device.version}}`
+{{% /collapse-content %}}
+
 ### Matching attribute/tag variables
 
 You can include any attribute or tag from a log, trace span, RUM event, CI pipeline, or CI test event that matches the monitor query. The following table shows examples of attributes and variables you can add from different monitor types.