지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for Virtualization Enterprise Edition 8.9.3 - Web Component Guide

Introducing the Web Component Framework The Web Component Framework Configuring Views and Context Queries Functions Bindings Additional Components

Node Associations

Node Associations bind a tag and a type to configuration for an object node in a topology component.

Node Associations have a tag (or set of tags) which are used to match the nodes against topologies which make use of them, and a Type and isList properties, that match an object type displayed in a topology.

Given a matching Node Association, the topology can retrieve the properties necessary to render the node.

Edge Associations

Edge Associations bind a tag and a pair of Type and isList properties that define the kind of nodes that the edge links.

An Edge Association contains:

•
One or more tags that are used to match the edges against the topology that uses them.
•
A pair of Type and isList properties defining the origin of the edge.
•
A pair of Type and isList properties for the termination of the edge. The combination of these properties matches a specific kind of connection within the appropriately tagged topology.

Given a matching Edge association, the topology can retrieve the properties necessary to render the edge.

Creating Associations

An association is used to house and organize references to entities. Create a new association either by starting with a blank association, or by copying an existing association.

To create an association:
1
From the navigation panel, under Dashboards, click Configuration > Definitions.
2
In the Module List pane, select the module where you want to create the association.
3
In the Module Contents pane, select Associations from the drop-down list.
4
Click .
The Add Association dialog box appears.
Figure 41. Add Association dialog box
5
Starting with a blank association only. Create a new, blank association by selecting the association type.
a
In the Add Association dialog box, ensure that the Blank Association tab is open.
b
Select the desired association type.
c
Click OK.
The new association appears in the editor pane.
Figure 42. New Association tab
6
Copying an existing association only. Create a new association by copying an existing association.
a
In the Add Association dialog box, open the Copy an Existing Association tab.
Figure 43. Copy an Existing Association tab
This tab displays a navigation tree containing a list of the modules that exist in your system. Expanding the tree structure shows the available associations and their usage.
b
Navigate to the desired association and select it in the tree.
c
Click OK.
The new association appears in the editor pane.
Figure 44. New Association tab
7
Configure the association by filling in the required fields in the editor pane. The fields for the different association types are described in the Web Component Reference help pages.

Creating Alarm Associations: Example

Alarm associations are used to link alarms to view components. Views that display alarms can use alarm associations. If you want alarms to use the Alarm dialog box, create an alarm association for each alarm type you want to display in this dialog box. If you want the Alarms table and Alarm dialog box to display agent information, the agent should be set as the monitoring agent for each entity it monitors.

Configuring the alarm association requires setting the following elements:

•
To define agent details to display, specify the time range and agent as context inputs.
•
Configure the Small Detail View property to point to a view to display on the Recent History view on the Summary tab.
 
* 
IMPORTANT: This is a small view. It should be approximately 130 px high.
•
Configure the Large Detail View property to point to a view to display on the Recent History view on the History/Notes tab.
 
* 
IMPORTANT: This view should be approximately 130 px high, but can be wider than the Small Detail View.
•
Set the Rule ID property to the ID of the rule that generates the alarm.
 
* 
IMPORTANT: There should be only one alarm association per rule. Otherwise, Foglight uses the first association it finds.
•
The rule that generates the alarm must have its Alarm Description property set.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택