Unsupported content

 

This version of the product is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Provider Access node

A Provider Access node represents the accesses to integrations (for example, a database integration or a query using the vSphere API) for a specific endpoint for a given Discovery Run node. It has relationships to each of the Integration Result node queries made by patterns to that database integration.

The endpoint attribute of a Provider Access node describes the IP v4 address at which that SQL database integration resides.

Provider Access Lifecycle

The following section describes the scenarios in which a Provider Access is created,updated or destroyed.

Creation

A Provider Access node is created when the first query is made to a database integration at that endpoint during the course of a Discovery Run. A Provider Access node is always created and stored, whether individual Integration Result node queries succeed or fail.

Update

The endpoint attribute on a Provider Access node is never updated. The hard_failure attribute can become true if a newly performed query represents a hard failure.

Removal

Provider Access nodes are removed when the Discovery Run node they are linked to is destroyed. See Discovery Run Node for more details. When a Provider Access node is destroyed, its related Integration Result nodes and their children are also destroyed.

Provider Access node attributes

The attributes of a Provider Access node are as described in the following table:

UI Name
Attribute Name and Type

Description

Provider Access Key
key string

provider_type/endpoint.

Provider Access Type
provider_type string

The type of the provider.

Range Prefix
range_prefix string

Distinguish overlapping address spaces.

Endpoint
endpoint string

The host that was accessed.

Dynamic Connections
is_dynamic boolean

Whether the integration point is for dynamic (endpoint supplied) or static (endpoint fixed).

Hard Failure
hard_failure boolean

True if there have been hard failures for this Provider Access type.

Retrieved by scanning appliance
is_consolidation boolean

If present, always have the value True and indicates that the data for this ProviderAccess originated from a scanning appliance before being consolidated on this one.

Provider Access node relationships

The relationships of a Provider Access node are as described in the following table:

UI name

Relationship

Description

Integration Results

ProviderAccess:
DiscoveryAccess:
DiscoveryAccessResult:
DiscoveryResult:
IntegrationResult

The result of the access.

Discovery Run

ProviderAccess:
Member:
List:
List:
DiscoveryRun

Discovery Run.

Discovery Access

ProviderAccess:
Member:
List:
List:
DiscoveryAccess

Discovery Access.

Session Results

ProviderAccess:
DiscoveryAccess:
Metadata:
Detail:
SessionResult

Session details.

Not displayed in UI

ProviderAccess:
InferredElement:
Inference:
Contributor:
DiscoveredAPIResult

Discovered API call result from which one or more attributes of this Runtime Environment were inferred.

Associated API call results

ProviderAccess:
InferredElement:
Inference:
Associate:
DiscoveredAPIResult

Discovered API call result related in some way to this Runtime Environment.

Was this page helpful? Yes No Submitting... Thank you

Comments