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:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
Provider Access node relationships
The relationships of a Provider Access node are as described in the following table:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.