Service Mapping ML and ser_ci_assoc table

Cameron13
Tera Contributor

Team,

In application Finger printing, ML suggests "Connection suggestions"; beside others  "Policy based Rules" is one of the influencer for the suggestions. My question is what else is considered for the suggestion decision ? is there any role for svc_ci_assoc at this stage ? . Also what is role of of cmdb_rel_ci entries (if any) at the suggestions ? 

1 ACCEPTED SOLUTION

Aakash Bhagat
ServiceNow Employee
ServiceNow Employee

Connection Rules are of two types :

Global Rules: these rules run for all the application services (you can also add services to the exclusion list of global rules)

Local Rules: local rules run only for specific service that is mentioned in the rule.

 

When top-down discovery runs it identifies the connection suggestions for specific ci part of service determined by svc_ci_assoc.

If for a particular ci if any connection suggestion matches the criteria specified in the rule it automatically changes the decision for the connection suggestion to added by rule and adds rule reference to connection suggestion and also runs discovery on the IP/port of the connection suggestion to bring in the new ci to the map and adds it to svc_ci_assoc after successful discovery.

Previously prior to Rome customer had to change the decision of the connection suggestion to add manually in order to add the ci that gets discovered using the connection suggestion to the map.

From customer can configure rules to automatically add the suggestion based cis to map as application service discovery happens periodically this helps in growing the map periodically based on rules configured and hence provide more visibility to connections in application service.

svc_ci_assoc is used to identify all the cis parts of the service so if ci is part of service a and while running discovery all the rules configured for the service a will be executed for the suggestions for that particular ci.

also, the cmdb_rel_ci table is used to populate applicative flow, use endpoint, implements endpoint relation between the ci discovered using suggestion and the source ci in order to show the ci on the map.

All the relations created to show this connection suggestion traffic based ci on the map we add a mapping between relations and classification id in cmdb_rel_attributes.

View solution in original post

1 REPLY 1

Aakash Bhagat
ServiceNow Employee
ServiceNow Employee

Connection Rules are of two types :

Global Rules: these rules run for all the application services (you can also add services to the exclusion list of global rules)

Local Rules: local rules run only for specific service that is mentioned in the rule.

 

When top-down discovery runs it identifies the connection suggestions for specific ci part of service determined by svc_ci_assoc.

If for a particular ci if any connection suggestion matches the criteria specified in the rule it automatically changes the decision for the connection suggestion to added by rule and adds rule reference to connection suggestion and also runs discovery on the IP/port of the connection suggestion to bring in the new ci to the map and adds it to svc_ci_assoc after successful discovery.

Previously prior to Rome customer had to change the decision of the connection suggestion to add manually in order to add the ci that gets discovered using the connection suggestion to the map.

From customer can configure rules to automatically add the suggestion based cis to map as application service discovery happens periodically this helps in growing the map periodically based on rules configured and hence provide more visibility to connections in application service.

svc_ci_assoc is used to identify all the cis parts of the service so if ci is part of service a and while running discovery all the rules configured for the service a will be executed for the suggestions for that particular ci.

also, the cmdb_rel_ci table is used to populate applicative flow, use endpoint, implements endpoint relation between the ci discovered using suggestion and the source ci in order to show the ci on the map.

All the relations created to show this connection suggestion traffic based ci on the map we add a mapping between relations and classification id in cmdb_rel_attributes.