Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Downtime Managements select Ci by View and tick all

Downtime Managements select Ci by View and tick all

Ci are selected by views which is OK  as lots of things in OBM10 depend on views .
In complex dynamic environments it would be good to allow  to select all the Ci  ,which are identified by the rule.

So just tick the View name itself in the Select Ci menu (and therefore all subsequent CI) , rather than to  walk through all the layers of the view.

It would be possible to create a view which links to  Node Group which includes all CI , but  Node Groups are flatten and static , therefore a View is the object of choice.

Use Case: Monitoring a Management Instance wich is the source for a  tree of  Ci and Events .

 

 

Tags (2)
11 Comments
tbriet Super Contributor.
Super Contributor.

Hi,

We use a lot Monitoring Automation . our uCMDB instance manage the deploymenent of monitoring based on discovery and enrichmenet mecanism.

We want to do the same for downtime management.

Currently to create or maintain downtime we need to select one by one CIs of a view.

We want to be able to apply downtime on all CIs of a view automaticly. We could add / remove CI on this view and the downtime will be automaticly updated.

Also it could be nice to have more properties on CIT bsm_dowtime (like name, schedule definition ..)

BR

Thomas

 

Micro Focus Expert
Micro Focus Expert

Hi Thomas,

Have you looked at this alternative approach:

https://marketplace.microfocus.com/itom/content/one-click-ad-hoc-downtime-management

Will this help in addressing your requirement? Please check and post your feedback here.

Thanks & Regards,

Moderator, OpsB IdeaX

tbriet Super Contributor.
Super Contributor.

Hi,

It could be a solution but it is not based on Downtime feature.

If you create a downtime there is a nice feature in dashboard. There is adjustable wrench that appear during downtime that why we want to use Downtime feature.

BR

Thomas

Micro Focus Expert
Micro Focus Expert

even though this sounds like nice enhancement, i think it will be very difficult to implement, as Downtime is calculated on top of the Topology and not on top of Views.

in order to achieve your request you can use CI Collection. when downtime applied on CIC, it will take into account all the children CIs of it (assuming you will use Membership or Containment links). the children can be added to the CIC via Enrichment rule or Pattern based model, which will achieve the exact same functionality as you have with Pattern view.

tbriet Super Contributor.
Super Contributor.

Hi Asaf,

Not really sure to understand difference between the calculation on top of Topology and on top of Views.

We modified the hidden query bsmdowntime_topology to integrate CiCollection.

We did some test but it doesn't work. I will try again as you explain it must be able to work.

Br

Thomas

 

Micro Focus Expert
Micro Focus Expert

Hi Thomas,

Please let us know if option suggested by Asaf meets your requirement?

Thanks & Regards,

Moderator, OpsB IdeaX

Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes
 
tbriet Super Contributor.
Super Contributor.

Hi

 

Unfortunetly no.

 

BR

 

Thomas

Respected Contributor.. aixgolfgirl Respected Contributor..
Respected Contributor..

This would be handy for us as well.  Thanks for submitting

kedel Trusted Contributor.
Trusted Contributor.

Static tagging of all sub elements in an topology view would be good for ad-hoc downtimes. The Downtime for a complete view helps not in all cases, especially for ootb views.

In dynamic cloud environment it would be good to have a posibility to set a sub tree of an ootb Topology View in Downtime. e.g. an AzureResourceGroup including all it's sub CIs independing what CIs exists at Downtime definition time (to address new createt resources after Downtime definition). The AzureResourceGroup CI-set  is a subtree of the ootb 'Azure RM Topology' view. 

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.