Capturing URLs in Service Now, would you and where?

danssnowquests
Tera Contributor

I had a request to capture all the URL's that my organisation manages into service now, Since I mostly focus on APM I considered putting them in APM but I could not make sense of where they would fit.  I asked my teams locally and they said they could add a custom field in APM or possibly on an app service,  that did not quite make sense to me. 
Essentially I could not get a satisfactory answer so. 

My two questions

  1. Does it make sense to track all an organizations URLs in SNOW
  2. Where would it fit, my guess is somewhere in the CMDB,  however I don't know what structure would be used to track it or would it be custom? 
1 ACCEPTED SOLUTION

mcastoe
ServiceNow Employee
ServiceNow Employee

I have seen this solved in a few ways.  I would not make the representation in APM as a URL is an "instance" of something.   A url would/should, in many cases, be associated to an Application Service (mapped) but i don't feel it belongs as an attribute.   I've seen these three solutions

1) add a new CI called Website URL
2) add a URL attribute to Web site [cmdb_ci_web_site]
3) use the out of the box HTTP(s) Endpoint [cmdb_ci_endpoint_http] class

I prefer the last option.

View solution in original post

6 REPLIES 6

Uncle Rob
Kilo Patron

Definitely interested in this myself.
Have you searched through the CMDB tables to see if there's anything that even looks plausible?

mcastoe
ServiceNow Employee
ServiceNow Employee

I have seen this solved in a few ways.  I would not make the representation in APM as a URL is an "instance" of something.   A url would/should, in many cases, be associated to an Application Service (mapped) but i don't feel it belongs as an attribute.   I've seen these three solutions

1) add a new CI called Website URL
2) add a URL attribute to Web site [cmdb_ci_web_site]
3) use the out of the box HTTP(s) Endpoint [cmdb_ci_endpoint_http] class

I prefer the last option.

Would this link to APM via the App services? 

Yes, create the HTTP(S) Endpoints, relate them to App Services (if you are just beginning to build out App Services, create a "nominal" App Service as placeholder).

 

Down in System Definition > Relationships define a Business App to URL Relationship so you have a nice tab on the Bus App form, build a CMDB Query Builder query so you can report and so forth.