Outages in DPM Workspace
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2024 12:09 PM
Looking for some guidance and best practices in recording Outages and having them show in DPM Workspace >Service Portfolios
It seems to me that Outage records need to be associated to a Service Offering to be visible in DPM - if we create an outage against a Configuration Item re: App Service or CI that outage record does not relate to the Service Offering directly.
We must create an Outage record and in the Configuration Item field we must add the Service Offering and then we get the Outage record reflected in DPM Workspace.
So 2 things 🙂
- Is this the correct process to create an outage record against the Service Offering directly? What happens if the outage impacts more than one Service Offering - do we need 2 records?
- Should we also create another outage for the server CI, App Service etc. so that we can keep that historical info that this server caused an outage and have that record be directly related to the lower level CI.
This means I could find the need to create multiple outage records for one outage - I hope I am missing something.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-01-2024 03:58 PM
At least in the older UI, you can add each affected Service Offering to the "Affected CIs" related list (or a tab in the DPM workspace) using the [cmdb_outage_ci_mtom] table.
This still provides outage calculations for the service offering even if the [cmdb_ci_outage.cmdb_ci] field is the infrastructure CI.
So no, you shouldn't have to create multiple outage records as long as the multiple affected offerings are recorded in the "Affected CIs" related list. This will still calculate availability against your relevant commitments.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-02-2024 10:10 AM
Hi Jim,
Thanks for your response.
I get it - we can open up the Outage Record for example against the CI = Application Service and then add in the Offering as a Affected CI related list on the Outage record and then DPM will show the Outage (against the offering). This can get cumbersome as now the team that handles the Outages must be knowledgeable on the understanding the relationship between the CI to Service Offering (i.e. server => App Service => to one or many Service Offerings etc.
I was hoping that DPM would show Outages against CIs that rolled up to Offerings automatically.