device42 · Nadia-JSch · Apr 1, 2026 · Apr 1, 2026 · Apr 1, 2026 · Apr 1, 2026
diff --git a/docs/auto-discovery/windows-and-hyper-v-auto-discovery.mdx b/docs/auto-discovery/windows-and-hyper-v-auto-discovery.mdx
@@ -12,7 +12,7 @@ This page covers prerequisites, how to create and run Windows and Hyper-V discov
 
 ## Prerequisites
 
-When using WMI, install the Windows Discovery Service (WDS) and connect to your Remote Collectors (RCs) before setting up your Windows discovery job. For WDS installation instructions and information, visit the [Windows Discovery Service Installation](/getstarted/deploy-device42/windows-discovery-service-installation.mdx) documentation.
+When using WMI, install the Windows Discovery Service (WDS) and connect to your Remote Collectors (RCs) before setting up your Windows discovery job. For WDS installation instructions and information, visit the [Windows Discovery Service Installation](getstarted/deploy-device42/windows-discovery-service-installation.mdx) documentation.
 
 ### WinRM Network Requirements
 
@@ -318,7 +318,7 @@ If the `DomainRole` value is one of the following, Device42 uses the `Domain` va
 Windows permission requirements are broken down into two parts:
 
 - Minimum required permissions for discovering **Windows host and guest information**.
-- Minimum required permissions for discovering **services and application data** for [Application Dependency Mapping (ADM)](/reports/dbb-cookbook/app-dependency-mapping.mdx) on Windows.
+- Minimum required permissions for discovering **services and application data** for [Application Dependency Mapping (ADM)](reports/dbb-cookbook/app-dependency-mapping/index.mdx) on Windows.
 
 WinRM-specific items are listed where applicable, but the permissions must be enabled on the target machine.
 
@@ -445,4 +445,3 @@ To discover a legacy Windows 2000-based operating system, adjust the following O
 
 1. Change or create the `HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel` element so that it has the value `1`.
 2. Change the WDS service user from `System` to one of the host users (like an admin account). You can try to run a discovery job without this step, but users report failure without making this change.
-
diff --git a/docs/getstarted/display.mdx b/docs/getstarted/display.mdx
@@ -9,7 +9,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 In the Display phase you will translate your validated, discovered data into actionable intelligence through various reporting and visualization capabilities, empowering users to make informed business decisions and integrate Device42 into their operational workflows.
 
 :::tip
-This is the fourth and final phase (Display) in the Device42 implementation process. See [How is Device42 Implemented?](/getstarted/how-is-device42-implemented.mdx) for an overview of all four phases.
+This is the fourth and final phase (Display) in the Device42 implementation process. See [How is Device42 Implemented?](getstarted/how-is-device42-implemented.mdx) for an overview of all four phases.
 :::
 
 ## Report and Dashboard Overview
@@ -20,7 +20,7 @@ There are two main types of Device42 reporting: Standard and Insights+.
 
 Standard Reports is the first place you will look for information. You can use and modify pre-defined reports, list reports, guided reports, and even use our Device42 Object Query Language (DOQL) if you are so inclined. You can export and schedule Standard Reports.
 
-Click [here](/reports/reports/standard-reports.mdx) for more information about Standard Reports.
+Click [here](reports/reports/standard-reports.mdx) for more information about Standard Reports.
 
 <ThemedImage
 alt="Creating a Standard Report"
@@ -40,7 +40,7 @@ Device42's Insights+ provides integrated analytics that leverage the breadth and
 
 Insights+ identifies patterns, trends, and outliers in data sets across your entire estate, elevating your performance with data understanding.
 
-Click [here](/reports/reports/insights-plus.mdx) for more information about Insights+.
+Click [here](reports/reports/insights-plus.mdx) for more information about Insights+.
 
 :::tip
 To view a video on ensuring success with Insights+, click [here](https://device42.wistia.com/medias/v1l5vahmem).
@@ -57,8 +57,8 @@ Below is a summary of each of the three Device42 reporting mechanisms:
 
 In addition to the above report links, below are links to additional reporting documentation:
 
-- We have created a [Data Building Blocks Cookbook](/reports/dbb-cookbook/index.mdx) that provides the 'recipes' to more easily create and run report-based queries.
-- The [Database Viewer Schema](/reports/device42-doql/db-viewer-schema.mdx) page explains how to view Device42's Entity Relationship Diagram and Data Dictionary.
+- We have created a [Data Building Blocks Cookbook](reports/dbb-cookbook/index.mdx) that provides the 'recipes' to more easily create and run report-based queries.
+- The [Database Viewer Schema](reports/device42-doql/db-viewer-schema.mdx) page explains how to view Device42's Entity Relationship Diagram and Data Dictionary.
 
     <ThemedImage
     alt="Data dictionary"
@@ -68,7 +68,7 @@ In addition to the above report links, below are links to additional reporting d
     }}
     />
 
-- The [InsightsAI Chat](/reports/device42-doql/insightsai.mdx) page explains how to use natural language descriptions to generate DOQL queries and tailored reports.
+- The [InsightsAI Chat](reports/device42-doql/insightsai.mdx) page explains how to use natural language descriptions to generate DOQL queries and tailored reports.
 
     <ThemedImage
     alt="InsightsAI chat"
@@ -103,4 +103,4 @@ Congratulations, You have completed the base Device42 implementation! Based on o
 
 Please contact [Device42 Support](https://support.device42.com/) should you encounter any issues, and please contact your Account Representative or your Customer Success Manager should you require assistance with any non-support matters.
 
-Please also refer to [Additional Customer Resources](/getstarted/additional-customer-resources/) for links that can assist you with your Device42 journey.
+Please also refer to [Additional Customer Resources](getstarted/additional-customer-resources.mdx) for links that can assist you with your Device42 journey.
diff --git a/docs/reports/dbb-cookbook/app-dependency-mapping.mdx b/docs/reports/dbb-cookbook/app-dependency-mapping.mdx
diff --git a/docs/reports/dbb-cookbook/app-dependency-mapping/_category_.yml b/docs/reports/dbb-cookbook/app-dependency-mapping/_category_.yml
@@ -0,0 +1,4 @@
+label: 'Application Dependency Mapping'
+position: 1
+collapsible: true
+collapsed: true
diff --git a/...bb-cookbook/business-app-dependencies.mdx → ...ncy-mapping/business-app-dependencies.mdx b/...bb-cookbook/business-app-dependencies.mdx → ...ncy-mapping/business-app-dependencies.mdx
diff --git a/...-cookbook/business-app-device-impacts.mdx → ...y-mapping/business-app-device-impacts.mdx b/...-cookbook/business-app-device-impacts.mdx → ...y-mapping/business-app-device-impacts.mdx
@@ -45,4 +45,3 @@ ORDER BY
     business_app_name ;
 ```
 </details>
-
diff --git a/.../business-app-hardware-eol-eos-impact.mdx → .../business-app-hardware-eol-eos-impact.mdx b/.../business-app-hardware-eol-eos-impact.mdx → .../business-app-hardware-eol-eos-impact.mdx
@@ -9,14 +9,14 @@ Use this if you need to analyze any of the changes needed when that EOL/EOS date
 
 You can easily shift the window or focus on either EOL/EOS by editing the included `WHERE` filter clause. 
 
-TIP: Additional information can easily be pulled in from the compute dbb as well. Please review the data dictionary with Device42 to see what information is available.
+Additional information can easily be pulled in from the compute dbb as well. Please review the data dictionary with Device42 to see what information is available.
 
 
 <details>
   <summary>Click to expand the code block</summary>
 ```sql
 SELECT
-    ba_comp.device_fk               AS eol_device_fk
+    ba_comp.device_fk               AS eol_device_fk
     ,compute.device_serial          AS eol_device_serial
     ,ba_comp.impacted_object        AS impacted_device_name
     ,ba_comp.business_app_name      AS impacted_businessapp

diff --git a/...business-app-operating-system-eol-eos.mdx → ...business-app-operating-system-eol-eos.mdx b/...business-app-operating-system-eol-eos.mdx → ...business-app-operating-system-eol-eos.mdx
@@ -13,10 +13,10 @@ You can easily shift the window or focus on either EOL/EOS by editing the includ
   <summary>Click to expand the code block</summary>
 ```sql
 SELECT
-ba_comp.device_fk               AS eol_device_fk
-,compute.device_serial          AS eol_device_serial
-,ba_comp.impacted_object        AS impacted_device_name
-,ba_comp.business_app_name      AS impacted_businessapp
+ba_comp.device_fk               AS eol_device_fk
+,compute.device_serial          AS eol_device_serial
+,ba_comp.impacted_object        AS impacted_device_name
+,ba_comp.business_app_name      AS impacted_businessapp
 ,ba_comp.businessapplication_fk
 ,ba_comp.impact_reason
 ,ba_comp.relationship_type

diff --git a/docs/reports/dbb-cookbook/app-dependency-mapping/index.mdx b/docs/reports/dbb-cookbook/app-dependency-mapping/index.mdx
@@ -0,0 +1,15 @@
+---
+title: "Application Dependency Mapping"
+sidebar_position: 1
+---
+
+These recipes are for teams planning infrastructure changes, migrations, or maintenance who need to understand the downstream business impact. They map how applications depend on devices and how devices support applications, helping you answer questions like "what breaks if this server goes down?" ([Business App Device Impacts](reports/dbb-cookbook/app-dependency-mapping/business-app-device-impacts.mdx)) or "which apps are at risk from this hardware EOL?" ([Business App Hardware EOL/EOS Impact](reports/dbb-cookbook/app-dependency-mapping/business-app-hardware-eol-eos-impact.mdx)).
+
+**Application Dependency Mapping Data Building Blocks**
+
+- [Business App Dependencies](reports/dbb-cookbook/app-dependency-mapping/business-app-dependencies.mdx)
+- [Business App Device Impacts](reports/dbb-cookbook/app-dependency-mapping/business-app-device-impacts.mdx)
+- [Business App Hardware EOL / EOS Impact](reports/dbb-cookbook/app-dependency-mapping/business-app-hardware-eol-eos-impact.mdx)
+- [Business App Operating System EOL / EOS](reports/dbb-cookbook/app-dependency-mapping/business-app-operating-system-eol-eos.mdx)
+- [Workload and Application Communication - Business App Communications](reports/dbb-cookbook/app-dependency-mapping/workload-and-application-communication-business-app-communications.mdx)
+- [Workload and Application Communication - IP Service Communications](reports/dbb-cookbook/app-dependency-mapping/workload-and-application-communication-ip-service-communications.mdx)
diff --git a/...unication-business-app-communications.mdx → ...unication-business-app-communications.mdx b/...unication-business-app-communications.mdx → ...unication-business-app-communications.mdx
@@ -73,6 +73,3 @@ ORDER BY
 
 </details>
 
-**NOTES**
-
-Use this query if want to move a Business Application to the cloud and need to know what clients communicate with it. This query will also give you the date of the last communication.
diff --git a/...mmunication-ip-service-communications.mdx → ...mmunication-ip-service-communications.mdx b/...mmunication-ip-service-communications.mdx → ...mmunication-ip-service-communications.mdx
@@ -3,7 +3,7 @@ title: "Workload and Application Communication - IP Service Communications"
 sidebar_position: 7
 ---
 
-IP Service Communications
+Use this query to identify what networks your servers communicate with — classifying client IPs as private or public per device.
 
 <details>
   <summary>Click to expand the code block</summary>
@@ -61,6 +61,3 @@ GROUP BY pp.client_device_fk
 
 </details>
 
-**NOTES**
-
-Use this query to if you need to identify what networks your servers communicate with (Private or Public).
diff --git a/docs/reports/dbb-cookbook/compute.mdx b/docs/reports/dbb-cookbook/compute.mdx
diff --git a/docs/reports/dbb-cookbook/compute/_category_.yml b/docs/reports/dbb-cookbook/compute/_category_.yml
@@ -0,0 +1,4 @@
+label: 'Compute'
+position: 2
+collapsible: true
+collapsed: true
diff --git a/.../reports/dbb-cookbook/compute-devices.mdx → .../dbb-cookbook/compute/compute-devices.mdx b/.../reports/dbb-cookbook/compute-devices.mdx → .../dbb-cookbook/compute/compute-devices.mdx
@@ -3,7 +3,7 @@ title: "Compute Devices"
 sidebar_position: 9
 ---
 
-Detailed Inventory of Compute Devices
+Returns a detailed inventory of all compute devices, including hardware specs, OS, cloud metadata, location, storage, and cost data. Use this to audit your assets for missing or incomplete information.
 
 <details>
   <summary>Click to expand the code block</summary>
@@ -17,7 +17,7 @@ Detailed Inventory of Compute Devices
          ,dc.service_level
          ,dc.device_type
          ,dc.device_subtype
-         ,dc.virtual_subtype 
+         ,dc.virtual_subtype 
          ,dc.device_serial
          ,dc.virtual_host
          ,dc.network_device
@@ -27,9 +27,9 @@ Detailed Inventory of Compute Devices
          ,dc.cpu_speed
          ,dc.total_cores
          ,dc.is_hyperthreaded
-         ,round((dc.ram_mb/1024)::numeric ,0)  ram_gb
+         ,round((dc.ram_mb/1024)::numeric ,0)  ram_gb
          ,dc.os_vendor
-         ,dc.os_category   
+         ,dc.os_category   
          ,dc.os_name
          ,dc.os_version
          ,dc.os_version_number
@@ -79,7 +79,7 @@ Detailed Inventory of Compute Devices
          ,dc.dns_A_records
          ,dc.dns_AAAA_records
          ,dc.local_used_space_gb
-         ,dc.remote_used_space_gb   
+         ,dc.remote_used_space_gb   
          ,dc.local_total_space_gb
          ,dc.remote_total_space_gb
          ,dc.local_free_space_gb
@@ -91,6 +91,3 @@ Detailed Inventory of Compute Devices
   ```
 </details>
 
-**NOTES**
-
-Gives the ability to manage your assets to see if you have any missing data.
diff --git a/...-cookbook/device-count-by-device-type.mdx → ...k/compute/device-count-by-device-type.mdx b/...-cookbook/device-count-by-device-type.mdx → ...k/compute/device-count-by-device-type.mdx
@@ -3,18 +3,16 @@ title: "Device Count by Device Type"
 sidebar_position: 10
 ---
 
-Count of Devices by device type.
+Returns a count of devices grouped by device type — useful for getting a quick summary of your device mix.
 
 <details>
     <summary>Click to expand the code block</summary>
     ```sql
     select
-         dc.device_type
-         ,count(1)                "count"
+         dc.device_type
+         ,count(1)                "count"
     from view_dbb_compute_v2 dc
     group by 1
     order by "count" desc
     ```
 </details>
-
-**NOTES**
diff --git a/...ookbook/device-count-by-service-level.mdx → ...compute/device-count-by-service-level.mdx b/...ookbook/device-count-by-service-level.mdx → ...compute/device-count-by-service-level.mdx
@@ -3,14 +3,14 @@ title: "Device Count by Service Level"
 sidebar_position: 11
 ---
 
-Count of Devices by service level.
+Returns a count of devices grouped by service level, useful for understanding how your assets are distributed across production, non-production, and other environments.
 
 <details>
     <summary>Click to expand the code block</summary>
     ```sql
     select
-         lower(dc.service_level)
-         ,count(1) as "count"
+         lower(dc.service_level)
+         ,count(1) as "count"
     from view_dbb_compute_v2 dc
     group by 1
     order by "count" desc

diff --git a/docs/reports/dbb-cookbook/compute/device-to-rack-inventory.mdx b/docs/reports/dbb-cookbook/compute/device-to-rack-inventory.mdx
@@ -0,0 +1,37 @@
+---
+title: "Device to Rack Inventory"
+sidebar_position: 12
+---
+
+Returns a physical device inventory organized by location hierarchy — building, room, row, rack, and U position. Use this to verify rack assignments and spot gaps in your physical inventory data.
+
+<details>
+  <summary>Click to expand the code block</summary>
+```sql
+select
+     dc.device_type
+     ,dc.server_location
+     ,dc.building_name
+     ,dc.building_address
+     ,dc.room_name
+     ,dc.row_name
+     ,dc.chassis_u_location
+     ,dc.chassis_device_name
+     ,dc.rack_name
+     ,dc.u_position
+     ,dc.device_name
+     ,dc.asset_number
+     ,dc.manufacturer
+     ,dc.hardware_model
+     ,dc.service_level
+     ,dc.in_service
+     ,dc.customer_department
+     ,dc.device_type
+     /* / used if renting bare-metal machine from a cloud provider.*/
+     ,dc.cloud_service_provider
+from view_dbb_compute_v2 dc
+where lower(dc.device_type) = 'physical' and  dc.rack_name is not null
+order by dc.server_location, dc.building_name, dc.room_name,
+dc.storage_room, dc.row_name, dc.rack_name, dc.u_position
+```
+</details>
diff --git a/docs/reports/dbb-cookbook/compute/devices-missing-device_type-or-service_level.mdx b/docs/reports/dbb-cookbook/compute/devices-missing-device_type-or-service_level.mdx
@@ -0,0 +1,27 @@
+---
+title: "Devices Missing Device_Type or Service_Level"
+sidebar_position: 13
+---
+
+Returns devices where `service_level` or `device_type` is missing, unknown, or set to a placeholder value. Note that `service_level` is set manually and is not directly discovered.
+
+<details>
+    <summary>Click to expand the code block</summary>
+    ```sql
+    select
+         dc.device_fk
+         ,dc.device_name
+         ,dc.service_level
+         ,dc.device_type
+         ,dc.device_subtype
+         ,dc.virtual_subtype
+         ,dc.cloud_service_provider
+         ,dc.cloud_service_name
+         ,dc.device_serial
+         ,dc.device_type
+    from view_dbb_compute_v2 dc
+    where lower(dc.service_level) in (null, 'missing', 'tbd')
+         or lower(dc.device_type) in (null, 'unknown')
+    ```
+</details>
+
diff --git a/docs/reports/dbb-cookbook/compute/index.mdx b/docs/reports/dbb-cookbook/compute/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Compute"
+sidebar_position: 8
+---
+
+These recipes give infrastructure, operations, and finance teams a detailed view of physical and virtual compute assets. Use them for capacity planning, hardware refresh planning, chargeback reporting, and identifying data quality gaps, such as [devices missing a type or service level classification](reports/dbb-cookbook/compute/devices-missing-device_type-or-service_level.mdx).
+
+**Compute Data Building Blocks**
+
+- [Compute Devices](reports/dbb-cookbook/compute/compute-devices.mdx)
+- [Device Count by Device Type](reports/dbb-cookbook/compute/device-count-by-device-type.mdx)
+- [Device Count by Service Level](reports/dbb-cookbook/compute/device-count-by-service-level.mdx)
+- [Device to Rack Inventory](reports/dbb-cookbook/compute/device-to-rack-inventory.mdx)
+- [Devices Missing Device_Type or Service_Level](reports/dbb-cookbook/compute/devices-missing-device_type-or-service_level.mdx)
+- [Physical Device Inventory](reports/dbb-cookbook/compute/physical-device-inventory.mdx)
+- [Physical Devices by Customer Department](reports/dbb-cookbook/compute/physical-devices-by-customer-department.mdx)
+- [Physical Devices Without Hardware Model](reports/dbb-cookbook/compute/physical-devices-without-hardware-model.mdx)
+- [Physical Inventory by Manufacturer](reports/dbb-cookbook/compute/physical-inventory-by-manufacturer.mdx)
+- [VM Density](reports/dbb-cookbook/compute/vm-density.mdx)
+- [VM Devices](reports/dbb-cookbook/compute/vm-devices.mdx)
+- [VM Inventory](reports/dbb-cookbook/compute/vm-inventory.mdx)
diff --git a/...bb-cookbook/physical-device-inventory.mdx → ...ook/compute/physical-device-inventory.mdx b/...bb-cookbook/physical-device-inventory.mdx → ...ook/compute/physical-device-inventory.mdx
@@ -3,7 +3,7 @@ title: "Physical Device Inventory"
 sidebar_position: 14
 ---
 
-**Inventory of Physical Device Information**
+Returns hardware specifications for physical devices — manufacturer, model, serial number, CPU, RAM, size, and hardware EOL and EOS dates. Use this to manage your physical assets and identify missing data.
 
 <details>
     <summary>Click to expand the code block</summary>
@@ -26,6 +26,3 @@ sidebar_position: 14
       ```
 </details>
 
-**NOTES**
-
-Gives ability to manage your assets to see if you have any missing data.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -45,4 +45,3 @@ ORDER BY
		business_app_name ;
		```
		</details>
Original file line number	Diff line number	Diff line change
Expand Up		@@ -73,6 +73,3 @@ ORDER BY

		</details>

		NOTES

		Use this query if want to move a Business Application to the cloud and need to know what clients communicate with it. This query will also give you the date of the last communication.