[Music] my name is colin christie with glidefast consulting today i'll be talking about machine learning powered service mapping and enhancements that have been made around traffic based discovery and utilizing the machine learning based connection suggestions for the rom release so when we're talking about the enhancements that were made to machine learning connection suggestions we're also talking about traffic based discovery when it comes to service maps and traffic based discovery previously would have gathered netstat data while running discovery on these servers and it would have started drawing outgoing connections from the servers based on the netstat data that it found now this would lead to connections being drawn and servers being included in the map that are not necessarily part of this application service and because of this customers have traditionally been disabling traffic based discovery because it brings a lot of clutter into the map and it makes them pretty unusable so now with the enhancements that have been made to the traffic based discovery we can utilize the connection suggestions instead of just getting all the connections that were found to be drawn on the map and for this application what was discovered so far was discovered by the out of the box patterns so i haven't had to do any additional development work to get this result but now i'm at the point where i know there should be another connection from this apache server and i know that because i sent a questionnaire to the applicationsme and he provided me the details on this application and what was indicated on that questionnaire was that there should be an outgoing connection from this apache server on port 5678 so before the updates to the connection suggestions if that connection was found it would have been drawn but so would every other connection that was found so now i can click on that ci and say show me connection suggestions and here we go we found uh an outgoing connection and then showing us which ip and it's telling us it's on port 5678 and that's exactly what i'm looking for so before the enhancements i would have had to either create a new extension section or connectivity section or i would have had to just manually add this in so this gives us a third option now that i can tell servicenow hey this is something i want to be included in this map and i can just go ahead and say add now we should see that the service will update and include that connection so i'm just going to go ahead and refresh the map and so now we're seeing that the service update is in progress and i expect to see that new connection get brought into the map just do another refresh there and there we go there's the new connection that i was expecting to see and there it is port 5678 that's the host and that's the ci that was discovered based on that connection so i was able to do that very quickly without any development work and now every time discovery re-runs on this application service map to refresh the data it will include this connection in the map so now that i've included the connection i was looking for into the eu billing service map my work is done here well that is true as long as i want this connection to be included in every application service map where this apache server exists and a connection to port 5678 is found on this host and to demonstrate what i mean by this let's take a look at the apac billing application service which is the apac version of the eu billing application service we were just looking at so we can see the same apache server exists and we've got the same worker process ci and the same connection on this host to port 5678 so you might be thinking now okay well isn't that essentially the same thing as the way we had it before where traffic based discovery is drawing connections to cis that aren't actually part of this application service well so here's where we get to do a little bit of fine tuning and really tell the service mapping what we do want and what we don't want so if i wanted to only include that connection in the eu billing application service i can set up a connection rule to tell it to do that so for 5678 on apache for eu and we're going to specify similar conditions to the connection suggestion record that we had only now we're gonna add an extra step okay so we've got our ip port is five six seven eight and source ci is the apache server so now i still have a field i need to fill out and that's discovered application service and i have this available to me because the scope is set to local if i change the scope to global now this rule would apply to any application service but by setting the scope to local i can now specify i only want this rule to apply to the eu billing application service so i'll go ahead and save this and now i've got a connection rule that will be specific to the eu billing application service so the next time discovery runs on the apac billing application service i am going to go back here and do a reset and then the next time discovery runs on the apac billing that connection should not reappear and i expect it to disappear now that i've removed it from the connection suggestion let's do another refresh and there it goes so now let's go back to eu billing and i expect to see it gone from there as well and it is and that is because this will apply to every application service if i go ahead and add this into the map if i only want it to apply to a single application service i can utilize the connection rule you