[Music] this is the presentation of the tag-based service mapping feature of servicenow item we will be using an openshift deployment on aws here i have deployed two services in my namespace let's look at the first one it has four parts each part has one container and this service is identified by the tag with the tag key app and the value of httpd24 centos 7. let's see how that looks in operator workspace right here i see that this service is not operational is now being monitored and any alert that would come in would be reflected by the color of that tile based on the criticality of the alert how did that happen well to do that let's try to add the second service so my second service here is has two pods and each part has actually three containers it is identified by the thai key app with the value of dopey so first of all before you deal with kubernetes you have to discover kubernetes we create a discovery schedule with this execution pattern where we specify the namespace in which case we want to collect order namespaces with some credentials and the url once item visibility discovers cooperatives it will discover all the parts all the containers as well as all the tags which are associated with all these resources so the next thing you would want to do is say that i'm only interested in a few tags out of order tags that may have been configured so this is what we call a tag category here we have defined app and application and the two tag keys that we are interested in following that we define a tag-based service family that service family will allow you to view the service candidates you can see here that i've already discovered the httpd 24 centos 7 service but based on this app tech app tag category namely the thai keys are app and application what would be the service candidates let me if i select this i get a list of all the application services which have a tag key defined with a specific value the one i'm interested in is this one dopey so i will select that service and that service will now be added to my list of services that i want to manage here it is so if i select it in the interest of time i will force a recalculate of the service and subsequently i'm going to make it operational to make sure that it is now managed through operator workspace and as i make it operational and save this configuration if i go back to operator workspace now my service is here and any alerts again happening on that service will be reflected in operator workspace let me select this service and click on the service map as expected i see that dopey has two [Music] kubernetes pods and each pod has three containers this concludes the demonstration of the tag-based service mapping feature in servicenow item thank you