Highlighted
Regular Contributor.. Regular Contributor..
Regular Contributor..
410 views

Health Top View

Jump to solution

Hi,

 

We are working on creating views/dashboard/pages for each major role in OMi. In the process of that we came across a question about how the Health Top View decides what view to display when the selected CI belongs to multiple views. We have a page that has the View Explorer, Event Bowser and Health Top View in it. We select a view in the View browser which displays the events against the view or CIs in the view. When we select an event, the Health Top View displays a view that is different from what we had selected in the View Browser. The CI effected by the event does belong to two different views. But how does Health Top View determine, which view to display?

 

For example, we have event1 raised against server1. Server1 belongs to NOC Ops View and ServerOwners view. We select Noc Ops in the view filter and select event 1 from the event browser. Health Top View shows server1 in the ServerOwners view and not NOC Ops view. How does it decise which view to show?

 

Any explanation you can provide to help with this will be appreciated.

 

Thanks,

Merry

Labels (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

When you create View Mapping definitions for a specific CIT (or you can check OOB view mappings) there is a field called "Precedence". The value of this field controls the order of views for CIs of a given CIT.

View solution in original post

0 Likes
2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

When you create View Mapping definitions for a specific CIT (or you can check OOB view mappings) there is a field called "Precedence". The value of this field controls the order of views for CIs of a given CIT.

View solution in original post

0 Likes
Highlighted
Regular Contributor.. Regular Contributor..
Regular Contributor..

Thank you so much for the quick response Dmitry!

0 Likes
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.