For OM as topology source to OBR: make selectable wheather disabled nodes shall be included

For OM as topology source to OBR: make selectable wheather disabled nodes shall be included

Brief Description

In an OBR setup where OM(L) is acting as the topology source only nodes that are "controlled" Node-Type are included and provisioned in OBR. The idea is that OBR should be configurable to include also other Node-types (i.e. "monitored only", "message allowed" , "disabled" ) in its topology and for OA-collections. 

Benefits / Value  

In an environment where the lifecycles of a Node in monitoring and reporting is different, a proper solution can be build:
For example a node is not yet under productive Monitoring (= "Disabled" in OM) but it can and should be already get the performance data collected by OBR. Or OBR should do Perf-Collections from a Node, even though the node is "just" message-allowed in OM. ... many more scenario are possible

Design Details

Have a configuration file, to incluence the SN-Collector's SQL query to the OM-Database. In this config file the desired Node-Types to include can be given ("controlled" is the default) 

 

Tags (2)
1 Comment
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.