Can I create HTTP(s) Endpoint CI relationships from Tag-Based Services

[jowaldo]

I've got a use case where the event management team is creating a catalog item to register new synthetic monitors for applications where a user selects an HTTP(s) Endpoint CI and an associated Application Service CI. They would like to create a CI relationship between the Application Service (Mapped or Tag-based) as the parent and the HTTP(s) Endpoint as a child so that alerts on these monitors can leverage the parent Application Service as the CI on the incident. Most of our applications are Tag-based, and I believe the HTTP(s) Endpoint CI is used for entry-point based mapping. Does the usage of a HTTP(s) Endpoint on a Tag-based Application Service interfere with the functionality of the Tag-based service map at all or can I create these relationships at free will to represent the dependency of an application on a website?

Thanks

#itom #cmdb

[Gary Ault]

This is something we would like to do as well in some way.  We are 100% tag-based service mapped, but there are cases where we want to tag a URL as a CI to go with the application service. 

[jowaldo]

We went ahead and did it, and we've had no issues! I'm using Depends on::Used by

[danesh]

@jowaldo  Did you use service mapping to identify HTTP(s) endpoints as part of your application service topologies or manually created the endpoint CIs?

[Gary Ault]

Did you manually build the relationship or tag the endpoint so it would link to a tag-based service. 

It's been a while since I attempt this and we have done an upgrade.  At a minimum I should see how it works now. 
At the end of the day, I want to link monitored http endpoints to a tag-based service by tagging them just like we do everything else.