---
title: "Exploring Discovered Assets"
canonical: "https://docs.infoblox.com/space/UniversalAssetInsights/1614250495/Exploring%20Discovered%20Assets"
format: markdown
---
> ⚠️ This feature is exclusively available to participants in the Early Access Program (EAP). For details about the EAP, visit the <u>*[Infoblox Early Access Program](https://info.infoblox.com/Early-Access-Program.html?_ga=2.126781636.874685606.1708970662-432134868.1674780450&_gl=1*35y1f7*_ga*NDMyMTM0ODY4LjE2NzQ3ODA0NTA.*_ga_D4JXVXQTYG*MTcwOTMyNTYxOS4yNTAuMS4xNzA5MzI1NjMwLjQ5LjAuMA)*</u> page. Infoblox consistently updates our documentation as we introduce new features to the EAP.

The asset explorer helps you visualize and navigate your discovered assets based on their physical or cloud-based locations. Whether your assets are deployed in the cloud or on-premises, the asset explorer automatically organizes them into a clear, hierarchical structure to make exploration easier.

For cloud assets, the asset explorer applies a built-in, non-editable structure that groups assets under the following provider-specific hierarchies:

- **AWS**: AWS → Region → Availability Zone
- **Azure**: Azure → Region → Availability Zone
- **GCP**: GCP → Region → Zone

As assets are discovered, the regions and availability zones are automatically populated and grouped accordingly. You can filter by region and availability zone to narrow your search and quickly locate the assets you're interested in.

For on-prem assets, the asset explorer also uses a built-in non-editable structure, which you cannot  customize. By default, it uses the NAT IP address of the host running discovery to determine the asset’s location, and organizes assets under the following hierarchy:

- Provider → Country → State/Province → City

You cannot customize the structure. However, you can control where an asset is placed within that structure by assigning a location as follows:

1. Create a Location Profile. For more information, see *[Creating Location Profiles](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/217680578)*.
2. Assign the location when creating a NIOS-X Server. For more information, see *[Creating NIOS-X Servers](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/119210910)*.

By creating and assigning locations to your servers, you can tailor this structure to better fit your environment and preferences.

To view and interact with your assets using this structure, go to **Monitor > Asset Explorer**. You'll see a tree view that separates cloud and on-prem assets, allowing you to explore your environment in a structured, intuitive way.

To view the asset explorer:

1. Go to **Monitor > Monitor**.
2. Click **Assets** at the bottom of the page to access the **Assets** workspace.
3. Click the `⋮ `menu at the upper right hand corner and select **Asset Explorer**.

## Tree View

The following is a representative of the tree view:

**Cloud** 

*Azure *

<Region 1>

<Availability Zone 1>

<Availability Zone 2>

<Availability Zone n>

<Region 2>

<Region n>

*AWS*

<Region 1>

<Region 2>

<Region n>

*GCP*

<Region 1>

<Zone>

<Region 2>

<Region n>


**On-Prem **

*<Country 1>*

<State/Province 1>

<City 1>

<City 2>

<City n>

<State/Province 2>

<State/Province n>

*<Country 2>*

<State/Province 1>

<State/Province 2>

<State/Province n>


## Node View

The node view shows three nodes - Asset, Network, and Service.

The following information is shown when you click each node:

- Device node: The following branches are shown with a count for each branch:
  - Workstation
  - Server
  - Computer Instance
  - Windows
  - Linux
  - Mac
  - Uncategorized
- Network node: The following branches are shown with a count for each branch:
  - Router
  - Address Space
  - Network Infrastructure
  - Subnet
  - Switch
  - Gateway
  - Firewall
- Service node: The following branches are shown with a count for each branch:
  - DNS
  - Storage