Data collected by Assets Discovery
Default data types and devices
The Assets Discovery tool will discover the following:
SSH | WMI | SNMP | VMware vSphere |
|---|---|---|---|
| Microsoft Windows® 95 |
|
|
Platforms included in patterns
We've tested the following patterns with Assets Discovery:
Linux/Unix | Windows | SNMP |
|---|---|---|
|
|
|
Data collected and available extensions
For details on what kind of data is collected by Discovery and imported into Assets in Jira Service Management, see Discovery data imported to Assets.
You can extend the collected data for all Discovery-Objects by using an ExtendedInformation-Object (as described in the table below). This way, you can add extra information to your assets before they're imported to Assets in Jira Service Management.
Using the ExtendedInformation-Object
You can use the Extended Information Object to impact the Hash of the parent object by setting the attribute UseValueForObjectHash to true in a pattern.
Attribute | Type | Description |
|---|---|---|
| Name | TEXT | |
| Type | TEXT | Valid Types: Date, Boolean, Integer, String (default) |
| Value | TEXT |
Using the object hash to define unique objects
In most of the collected objects by Assets Discovery, you can find an attribute called "Object Hash", which is used as a default Identifier for Assets in Jira Service Management.
These Object Hash Attributes define 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 of 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.
Analytics data collected by Discovery
The knowledge of how you use Discovery helps us improve the product and your experience. That’s why we’ve automated the collection of usage analytics, which you can turn off at any time. The data we collect includes information about the common settings, scanned system types, timing, and the features you use in Discovery.
We do not collect any personal information or user-generated data.
A Discovery admin can disable the analytics collection at any time.
Along with the feedback we get from you through Jira tickets, we’ll use the analytics to better understand friction areas and improve them quicker, as well as to detect potential bugs and fix them before they impact your work.
For more details, check our Privacy Policy, specifically the section ‘What information we collect about you’. You can also reference the End User Agreement to find out more.
How to manage data collection?
Data collection is turned of by default. A Discovery admin can opt in or out of data collection at any time.
To turn off data collection:
In Discovery or the Collector, go to the Common tab.
Clear the Send analytics checkbox.
How is data collected?
We use the Atlassian infrastructure to collect event data in Discovery. Analytics logs are stored locally and then periodically uploaded to a secure location.
What data do we collect?
We collect anonymous statistics about the operating system, application settings, data size and scanning performance, and others. We do not collect any personal information or user-generated data.
Here are some example events collected:
|