• Products
  • Get started
  • Documentation
  • Resources

Data collected by Assets Discovery

Assets Discovery uses the protocols SSH, WMI and SNMP to discover hosts and devices. In theory, all network connected machines that can communicate through one of these protocols can be discovered.

To assemble details information from a host or device, Assets Discovery needs instructions on how to do it. These instructions are specified in Patterns and Assets Discovery comes pre-packed with a set of patterns ready to use.

You can also write your own patterns if you have unusual assets to discover.

Default data types and devices

The Assets Discovery tool will discover the following:




VMware vSphere

  • Linux/Unix Based Operating Systems

  • AIX Systems

  • Mac OS X Operating Systems

  • BSD Operating Systems

  • HP-UX Systems

  • Novell Netware Systems

  • Solaris Systems

  • Microsoft Windows® 95
    or later Microsoft operating systems

  • Network Printers

  • IP Cameras

  • Routers

  • Switches

  • Network Access Servers

  • Device: Printer

  • Device: Monitor

  • Device: USB Storage

  • Device: VideoController

  • ESXi Hosts

  • Virtual Guests

The following default patterns have been tested with Assets Discovery:




  • Ubuntu (>12.x)

  • CentOS (>6)

  • Debian (>7)

  • Red Hat (>6)

  • OpenSUSE (Tumbleweed)

  • Mac OS X (>10.x)

  • Solaris 11

  • Oracle Linux (>7)

  • Xen

  • Docker

  • Windows XP

  • Windows 7

  • Windows 8.1

  • Windows 10

  • Windows Server 2003

  • Windows Server 2008

  • Windows Server 2012

  • Windows Server 2016

  • Windows Server 2019

  • Docker

  • Axis IP Camera

  • Samsung IP Camera

Collected information and possible extensions

The possible data collected by Assets Discovery and imported into Assets in Jira Service Management can be found here.

The collected data for all of the Discovery-Objects can be extended with an ExtendedInformation-Object.

All Discovery-Objects can have an list of these ExtendedInformation-Objects and opens the possibility to add informations from the Discovery side (Pattern) and make them available in Assets in Jira Service Management.

Using the ExtendedInformation object

Extended Information Object can be used to impact the Hash of the parent object by setting the attribute "UseValueForObjectHash" to true in a pattern.








Valid Types: Date, Boolean, Integer, String (default)



Using the object hash to define unique objects

In most of the collected objects from Assets Discovery you can find an attribute called "Object Hash" which is used as default Identifier for Assets in Jira Service Management.

This Object Hash Attributes defining the Object as a unique object in Assets (for creating a new one or updating an existing one).

On the Assets Discovery side you can find an ObjectHashSetting.xml file, this file contains the definition which attributes of the object will be used to build the unique hash.

Manipulations of this file will always have effects to your existing data in Assets.

For example:

If you set the value of <HostInfo_FirstNICMAC>true</HostInfo_FirstNICMAC> from "true" to "false" the NetworkInterface-MAC-Address of the first available NIC will not longer used to build the Host-Hash.

All Host-Hashes will be "new" and importing the data will create new Host-Objects in Assets in Jira Service Management.


Still need help?

The Atlassian Community is here for you.