From a7e826854a9ab2ad0b84570af692adc58122df29 Mon Sep 17 00:00:00 2001 From: stevenkline Date: Wed, 15 Jul 2026 16:45:27 -0400 Subject: [PATCH 1/4] steven.kline/Update variables.md with network device metadata Added network device metadata variables and their attributes to the documentation. --- content/en/monitors/notify/variables.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/content/en/monitors/notify/variables.md b/content/en/monitors/notify/variables.md index 63785f72121..b0b0a01d0d9 100644 --- a/content/en/monitors/notify/variables.md +++ b/content/en/monitors/notify/variables.md @@ -380,6 +380,23 @@ 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: +- Device ID: `{{network_device.device_id}}` +- Device namespace: `{{network_device.device_namespace}}` +- Device type: `{{network_device.device_type}}` + +The following table contains all available attributes: + +| Variable syntax | First level attributes | +|-------------------|------------------------| +| `{{network_device.device_id}}` | `canonical_id`, `name`, `description`, `model`, `vendor`, `device_type`, `os_name`, `os_version`, `os_hostname`, `ip_address`, `subnet`, `location`, `serial_number`, `version`, `product_name`, `sys_object_id`, `profile`, `status`, `ping_status`, `integration`, `namespace`, `tags`, `id_tags`, `in`| +{{% /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. From 74c0e1015ab624e9eb290b9ed931d54df353cea1 Mon Sep 17 00:00:00 2001 From: stevenkline Date: Wed, 15 Jul 2026 16:47:08 -0400 Subject: [PATCH 2/4] Update available attributes for network_device.device_id --- content/en/monitors/notify/variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/monitors/notify/variables.md b/content/en/monitors/notify/variables.md index b0b0a01d0d9..23c2375a559 100644 --- a/content/en/monitors/notify/variables.md +++ b/content/en/monitors/notify/variables.md @@ -394,7 +394,7 @@ The following table contains all available attributes: | Variable syntax | First level attributes | |-------------------|------------------------| -| `{{network_device.device_id}}` | `canonical_id`, `name`, `description`, `model`, `vendor`, `device_type`, `os_name`, `os_version`, `os_hostname`, `ip_address`, `subnet`, `location`, `serial_number`, `version`, `product_name`, `sys_object_id`, `profile`, `status`, `ping_status`, `integration`, `namespace`, `tags`, `id_tags`, `in`| +| `{{network_device.device_id}}` | `canonical_id`, `name`, `description`, `model`, `vendor`, `device_type`, `os_name`, `os_version`, `os_hostname`, `ip_address`, `subnet`, `location`, `serial_number`, `version`, `product_name`, `sys_object_id`, `profile`, `status`, `ping_status`, `integration`, `namespace`, `tags`, `id_tags`, `integrations`| {{% /collapse-content %}} ### Matching attribute/tag variables From b280424e0c17f69ae7c2d9bbfeb1ae80f732147f Mon Sep 17 00:00:00 2001 From: stevenkline Date: Wed, 15 Jul 2026 16:52:06 -0400 Subject: [PATCH 3/4] Alphabetize attributes for network_device --- content/en/monitors/notify/variables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/monitors/notify/variables.md b/content/en/monitors/notify/variables.md index 23c2375a559..37a8915731d 100644 --- a/content/en/monitors/notify/variables.md +++ b/content/en/monitors/notify/variables.md @@ -394,7 +394,7 @@ The following table contains all available attributes: | Variable syntax | First level attributes | |-------------------|------------------------| -| `{{network_device.device_id}}` | `canonical_id`, `name`, `description`, `model`, `vendor`, `device_type`, `os_name`, `os_version`, `os_hostname`, `ip_address`, `subnet`, `location`, `serial_number`, `version`, `product_name`, `sys_object_id`, `profile`, `status`, `ping_status`, `integration`, `namespace`, `tags`, `id_tags`, `integrations`| +| `{{network_device.device_id}}` | `canonical_id`, `description`, `device_type`, `id_tags`, `integrations`, `ip_address`, `location`, `model`, `name`, `namespace`, `os_hostname`, `os_name`, `os_version`, `ping_status`, `product_name`, `profile`, `serial_number`, `status`, `subnet`, `sys_object_id`, `tags`, `vendor`, `version`| {{% /collapse-content %}} ### Matching attribute/tag variables From a50d4869045a23338a8b6be2d77187bc7ae6afc8 Mon Sep 17 00:00:00 2001 From: stevenkline Date: Thu, 16 Jul 2026 13:31:32 -0400 Subject: [PATCH 4/4] Enhance network device metadata documentation Added additional network device metadata variables and updated the table of available attributes. --- content/en/monitors/notify/variables.md | 31 ++++++++++++++++++------- 1 file changed, 23 insertions(+), 8 deletions(-) diff --git a/content/en/monitors/notify/variables.md b/content/en/monitors/notify/variables.md index 37a8915731d..a1f5eb14b26 100644 --- a/content/en/monitors/notify/variables.md +++ b/content/en/monitors/notify/variables.md @@ -386,15 +386,30 @@ For Docs and Links you can also access a specific item with the following syntax 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: -- Device ID: `{{network_device.device_id}}` -- Device namespace: `{{network_device.device_namespace}}` +- Canonical ID: `{{network_device.canonical_id}}` +- Description: `{{network_device.description}}` - Device type: `{{network_device.device_type}}` - -The following table contains all available attributes: - -| Variable syntax | First level attributes | -|-------------------|------------------------| -| `{{network_device.device_id}}` | `canonical_id`, `description`, `device_type`, `id_tags`, `integrations`, `ip_address`, `location`, `model`, `name`, `namespace`, `os_hostname`, `os_name`, `os_version`, `ping_status`, `product_name`, `profile`, `serial_number`, `status`, `subnet`, `sys_object_id`, `tags`, `vendor`, `version`| +- 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