[Music] hello my name is gerard berte i'm an outbound product manager in the itunes business unit at servicenow this presentation may contain forward-looking statements this is the third part of a series of three videos on getting studied with servicenow item health without any prior discovery or cmdb the scenario today will be to automatically populate an application service using tag-based service mapping we will discover a kubernetes environment and identify a specific service based on its specific tag value we will visualize the service topology and the dependency view in operator workspace the business outcomes is that we will see that how we can actually create services in the cmdb using automatic creation of those services by you leveraging tag-based service mapping this allows us to get more detailed impact and root cause analysis thanks to the ai ups capabilities of item health which further reduces the time for operators to identify the main cause of alerts now let's move on to use case number three with tag-based service mapping so the my setup here is that i have openshift running on aws i'm running a very simple web server http 24 centos 7 and it has currently three parts as you can see down below here it has one one tag called app with this value of http 24 center s7 so what i did with in my instance was to do a basic discovery of kubernetes simply specifying the endpoint and the credentials and it discovered uh everything about kubernetes now in openshift is the red hat's version of kubernetes so it's a very same type of discovery it discovers the pods the containers the server it discovers the images the volumes etc etc when kubernetes discovery occurred it collected all the tags that he could find all the different keys and the different values now out of this i want to specify that i'm only interested in certain keys as i saw in openshift the key that i'm really interested in is app so in my instance i specify what we call a tag category and specify that i'm only interested in the tags called app and application and then out of those i'm interested in a service in my apache service for which the tag value is http 24 sent to s7 which is the tag that i saw in openshift as soon as i do that um servicenow is going to run a service mapping based on this tag and propose some some service candidate i already went through that step and identified that this service is indeed the service that i'm interested in and as soon as i make it operational i now can see it on operator workspace so here it is if i look at the service map it shows that my three pods with three containers and if i look at this dependency view of one of these pods first i have to go into the full map if i right click on that part and look at the dependency views i am going to see a very extensive map of my service here the tag-based service ci is here it is running on this pod which is running this container this container is actually and this kubernetes part are actually running on this linux server as well as the kubernetes cluster running on this linux server and that container itself is associated with a docker image as well as other containers and my kubernetes pod as a kubernetes volume all of this was generated automatically out of my kubernetes discovery it is also important to note that if i were to change the number of pods whether increase or decrease the number of parts here or if i have auto scaling the topology map of my service would be reflected pretty much in near real time as we pick up those changes in dynamic dynamically so this concludes our use case number three which shows that you can very easily obtain a very sophisticated service map simply by using tags and doing tag-based service mapping this concludes part three of a series of three videos on getting studied with servicenow item health without any prior discovery or cmdb you