What CI type should be used for SaaS\Cloud applications where you have no visibility?

mark_oldroyd · ‎01-16-2023

I was wondering if there was a correct CI type to use when referencing infrastructure for application services that are SaaS\Cloud applications where you have no visibility into the actual infrastructure.

For example, I would have an application service for my Service Now Prod but what infrastructure CI type would it depend on or be hosted on to represent the Service Now cloud?

Robert80 · ‎01-16-2023

If I understand correctly, you are asking for a way to reference the cloud infrastructure without knowing the specific CIs within that environment. Strictly speaking, you should create an application service to represent the solution and stop there but I think you'd like to see a dependency so that you could, for example, identify the impact of a scheduled outage by your provider.

I don't think cmdb_ci_environment is quite the way to go because it's designed for concepts like "Production", "Development", "QA", etc. Rather, you could create a service offering that represents the underlying 'environment' and, using service builder, navigate to the "Operations" tab of your SaaS offering and add the other offering as an "Offering I depend on".

Alternatively, you could create a CI using the 'Cloud Host' class to represent your hosting environment and use the Runs On relationship between the Application (part of your application service) and that Cloud Host.

View solution in original post

Barry Kant · ‎01-16-2023

hi Mark,

I think there is no need for it (as it is consumed as a service).
With exceptions:
if it comes to eg mid-servers for integrations etc. The mid-servers are part of your own supportability (either outsourced as well, but still a separate sub-service).
the other exception is of course when it is on-premise (so non-saas )

Cheers,

Barry
I

mark_oldroyd · ‎01-16-2023

Hi Barry,

Whilst it probably says more about me than the CSDM, visually I don't like seeing nothing on the map.

Would there be any harm in using something like a cmdb_ci_environment? Or does Discovery have a use for this?

Thanks,

Mark

Barry Kant · ‎01-16-2023

hi Mark,

the Application Service level represents that environment you mention. So that would be kind of duplicate. (not needed).
What and when do you really mis?

Cheers,
Barry

Stuart Tucker · ‎01-16-2023

We are looking to adopt the use of the Product Model type called a Service Model. For all those cloud services with no hosted infrastructure, link to a Service Model which describes how that cloud service is supported, by whom, the lifecycle, the product owner etc. The same Service Model could be linked to multiple Application Services which represent different instances of the same cloud service.

You can of course link an Application Service to another Application Service if there is a dependancy between them.