Default language.

Important This documentation space contains information about the SaaS version of BMC Helix Discovery. If you are using the on-premises version of BMC Helix Discovery, see BMC Helix Discovery 25.2 (On-Premises).

DDD nodes

This section describes the BMC Helix Discovery Directly Discovered Data (DDD) nodes. Directly discovered information is obtained directly from a target host via particular discovery techniques. All Directly Discovered Data is stored, regardless of whether it is understood or not. Target discovery devices are accessed as part of a Discovery Run, corresponding to a range of devices that are scanned. When Reasoning starts accessing a target device, it creates a Discovery-Access-node to represent the access and relates it to the corresponding Discovery Run. The Discovery Access node contains information about the time of discovery and the discovery method and credentials used. Each time a device is rediscovered, a new Discovery Access node is created, and the discovery information is attached to it. If a target host cannot be accessed, a Discovery Access node is created to represent the failed access.

The Host node

The Host node itself is not considered directly discovered information, since a level of inference is required to decide which Host a Discovery Access corresponds to. See Host-node for more information.

Discovery Run nodes are created first because they contain all other DDD nodes. Discovery Access nodes are then created, followed by the remaining DDD nodes. The following node kinds are described:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*