CMDB and URL CIs

NevilleLee · ‎12-21-2023

Hi All,

Is there anyone using URLs as a CI, if so, how are you using it.

Do you have a data model with URL as an Entity Type? If so can you share?

We are using URL as a data attribute on the CMDB Business Application table.

Daniel Borkowi1 · ‎01-03-2024

Hi @NevilleLee , I would create for each System stack an own Application Service and would add the HTTP Entry points to these Application Services to stick on CSDM.

Sorry there was a mistake in my original answer above: "Within Business Applications Application Services you can store End Points (e.g. URL) of the technical stack which delivers the Application Services"

As all Endpoints are CI Classes derived from cmdb_ci_endpoint and URLs are represented as HTTP(S) Endpoint (cmdb_ci_endpoint_http) you can also use this standalone with a depends on relationship from any Business Service class to this endpoint. But I recommend to add the Application Service level.

Here an example:

For sure you can also add this relationship to Business Application directly, but then it's not the CSDM way.

Btw. my example doesn't use Service Mapping the Endpoints are used to scan the vertical stack behind an endpoint like URLs.

Greets
Daniel

Please mark reply as Helpful/Correct, if applicable. Thanks!

View solution in original post

NevilleLee · ‎12-22-2023

Hi Rose, thanks for the reply, how are you handling multiply URLs for one Business Application?

Rose LeSage · ‎12-22-2023

Good question! The only example of multiple URLs for one business application that we have is when we have non-prod environments with different URLs. I don't capture the non-prods at the business application level, just production instances. We capture the non-prods at the application service level.

Community Alums · ‎01-02-2024

Hi @NevilleLee,

Out of the box, you can add one URL to each Business application, using the 'Application URL' field. If you want to add more than one URL, the 'official' method would be to add a relationship between the Business application and a 'Service' (Business Service) and add relationships from the Service to one or more HTTP(S) Endpoints containing your URLs. You can just add the relationships directly between the Business Application and HTTP(S) Endpoints, though. It would be a Endpoint >> [Depends on::Used by] >> Business Application relationship.

If you're using CSDM and Application Services, add the URLs as Entry Points for your Application Services, as @Daniel Borkowi1 specifies.

But, if for some reason, you need to log Incidents against the URL as a CI, then you'll need to store them as HTTP(S) Endpoints. Either that, or you end up logging your ticket against the Application Service or an underlying CI.

I personally haven't come across anyone logging Incidents, Problems or Changes against URLs.

Thanks - please mark as helpful, if this is useful.

Jason

Miklos Palfi · ‎08-07-2024

Both solutions suggested by @Community Alums and @Daniel Borkowi1 are very valuable for us.

We prefer the cmdb_ci_service_auto (Application Service) [Depends on::Used by] cmdb_ci_endpoint_http relation, because it gives us the possibility to store multiple URLs for different stages (prod/test/dev) and it is also working with SaaS solutions. (like myservicenow qa [depends on::used by] qa-mycompany.servicenow.com). Certificate discovery works also well with this:

Discovery relates the endpoints to deeper level to the application entries (cmdb_ci_appl) like described here:

https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/discovery/task/run-cert-inventory-mgmt-urls.html
"The relationship is: cmdb_ci_endpoint_http[parent] --> [Implement End Point To::Implement End Point From] --> cmdb_ci_appl[child]."