IT Operations Management (ITOM)

HP Service Health Reporter 9.30 - Master the power of Remote Collector - Part 2

HP Service Health Reporter 9.30 - Master the power of Remote Collector - Part 2


By Vageesh Hoskere


In the last post we started with some details on datasource configuration and covered configuring source using rules/patterns. Now, onward with other options!!


Second Option: Go by the VIEW/GROUPS linked-


The meaning -

Agent instances can also be configured to a collector based on View/Node Groups that they belong to in RTSM and HP OM respectively. When a node group/view is configured to a collector, all nodes belonging to that particular view/group will be assigned for collection from that collector. In case of a node belonging to multiple groups/views the same logic of contention resolution as in pattern based distribution is applied i.e. first match is considered for association. Please note that associating a particular view/group to one collector does not mean that data related to only that view/group will be collected from nodes configured to the collector but data for all installed content for a node belonging to a particular view/node group associated to a collector will be collected from that collector.



A few samples -

As an example, if a collector SHRCOLLECTOR1 is associated with SM_HYPERV view and one more collector SHRCOLLECTOR2 is associated to SM_VMWARE view, then all nodes belonging to SM_HYPERV and SM_VMWARE views are configured for collection from SHRCOLLECTOR1 and SHRCOLLECTOR2 respectively and the data collected from these sources is not limited to HYPER-V and VMWARE, but for all domains installed on SHR. 



Third Option: It is my choice -


What it means -

Agent sources can be explicitly associated against a particular collector. Whenever a node is configured manually to a particular collector, it is not considered for any other forms of assignment. So even if the node matches a specified pattern to some other collector and/or a view/group that the node belongs to is associated to a different collector, manual assignment of the node is retained and the other assignments invalidated. Manual assignment of a node is helpful in cases where there is a need to override the systemic assignment made based on the rules/views or if the nodes neither confirm to any pattern nor belong to a particular view/node group.



And how is it done?

To assign a node manually to a collector, on the “HP Operations Agent” configuration page of the SHR Admin UI, select the node and change the rule type from SYSTEM to USER. Once the rule type is changed, the user can then choose the collector where the node is to be configured for collection.


And what if I want to no more do things manually, but let SHR handle the distribution?

In order to let SHR handle the node association based on the assignment criteria, the rule type has to be changed back from USER to SYSTEM. Once done, the agent will then be put through the distribution routine to find its best fit.


So even after all this if the agent does not match to anything, then?

Suppose an agent ends up being not configured to any of the collectors even after being put through the distribution logic, it will be marked as UNASSIGNED in the same page. They can be manually configured to any of the collectors using the USER assignment or the rules/patterns or even the VIEW based assignments can be added/updated to handle the particular node or the ones similar to it that may be discovered via the topology collection in future


Individually it sounds good but what if I want to use them all?

As mentioned previously, nodes can be distributed amongst the collectors using any one or a combination of the logics described above. In cases where a combination is used, there is precedence order in which the options are applied.


First comes the Manual configuration of an agent instance to a collector. Any USER assigned node will always be configured for collection on the same collector until it is marked for SYSTEM assignment or is no more a datasource. Second is the RTSM View/HP OM Node group based distribution with the Rules/Pattern based distribution being the final mode of configuration. So all OA/PA datasource discovered in SHR will be put through this routine and whichever collector hits a match first will be the one where data will be collected from that node.


I hope this gives some insight on what goes behind the scenes and also on the options available for source configuration. Please do leave your thoughts/comments on the same.

  • operations bridge
0 Kudos
About the Author


This account is for guest bloggers. The blog post will identify the blogger.