right I see plenty of you have joined so I guess we can get started so good morning good afternoon and good evening everyone and welcome to another session of the iton visibility and governance webinar serieses this session is part of the live on service now webinar serieses and I guess you're very familiar with this session if you're not don't miss out on the recordings of the preview sessions that you can find in our community website today we're going to talk about the service mapping leading practices and we have a super special guest today we have Bill eind U but we'll proceed with the introductions in a little while so uh just as a reminder as I was mentioning there this uh particular webinar is part of the live on service now webinar serieses which is an event series that is quite interactive and is meant to speed up the deployment adoption and really achieve value faster uh for your businesses you can either scan uh this QR code here on this slide or alternatively you can use the link that has been just posted via chat so just make sure that you will uh subscribe to this uh particular event series now if you housekeeping items before we get going so please make sure that everyone's line is muted and make sure to please use the Q&A feature to really ask questions throughout this session and we'll make sure they will uh answer all of them also whenever you are asking those questions feel free to introduce yourself and uh really would like to know uh to to know who you are please also participate in the polls we're going to have a few polls today uh throughout the session so it will be really uh great for us to understand your perspectives and and your maturity levels and again this session as I mentioned before as for the previous session this one specifically is recorded and the recording uh will be shared not only on the service now Community page where you actually registered for this session specifically but also on YouTube and uh on the actual very same page you will also find out uh the slides that we're going to present today for uh after this session please make sure that you fill out the short survey you'll be prompted at this is really important feedback for us so um you've done a great job so far please uh just keep meeting our expectations that's great so again for those of you that don't know me yet my name is John Mario de Luigi I'm part of the outbound product management team here uh for item and together with me today we're going to have the Superstar as many of you asked for it is going to be William Inland also known as bill so bill please introduce yourself good morning good afternoon good evening everyone thank you for joining today my name is Bill iffland and a little bit about myself I have been a practitioner of service now since 2007 and I joined the organization after being a practitioner for 13 years so in a little bit uh around 2018 I BEC became a itom ranger and with that uh my uh expertise areas are around cmdb csdm iton visibility and more specifically service mapping and again just a shout out to my manager danila makula and the other rangers just want to thank them for their support and also their encouragement I get a lot of uh guess Challenge and iron sharpens iron so again thank you for your uh attendance today and I hope this is a session that meets your expectations absolutely I'm sure it will bill this exciting stuff to have you on this specific session as very very few people out there can have your level of expertise on these topics especially when it comes to item visibility and service mapping so uh before we proceed into the content and we just wanted to make sure that you understand that throughout this presentation we could be potentially making some uh forward-looking statements so uh don't necessarily base your purchasing decision on these uh forward looking statements that you could find throughout this presentation and most of the content either way is about current Solutions but we just wanted to make sure that you're aware um there could be something there is um again a forward looking statement so today's topic as I said is service mapping and it's very important to really understand why are we doing this session and this is exactly the intent of these very few slides at the beginning of this presentation so let's get started I'm pretty sure that if this is not the first time you attend our webinar series is you're by now familiar with this slide and the key message that is Li wants to convey is first of all the visibility is really Paramount for your business technology excellence and we I want to always use the analogy that is always mentioned in the uh iton workshops that we do together with all of you which is you can only manage what you know so visibility helps you to have a real understanding of what you have in your infrastructure what applications you have uh across of course uh multiple um either cloud or onr environments and also makes you uh understand what are the relationships between those CIS so really the cmdb as you may be familiar with is the real data Foundation of your organization and IT service now data Foundation uh of course but especially the most successful cnbs are the ones that are not only populated with um all the um information about the infrastructure uh elements if we will or about the applications but is the uh really uh service aware cnps that are the most successful ones and that's exactly why today we're going to talk about service aware uh cnbs what does this imply and uh we're going to see now in more details with the following slides so the cmdb can have different levels of we can say awareness or maturity so item discovery allows you to have the technology awareness so uh to really be aware of what your infrastructure resources are across different environments we're talking about on Prem we're talking about private managed and public clouds really so what is your technology stack and then on top of that we have service mapping which is going to be exactly what we're going to talk about today then let you understand what are the relationships uh between the very same application services and those CIS that we have discovered and so that technology layer that is underneath so uh we can take uh data driven decisions on top of uh those CIS because we know exactly what impact do they generate on the application services on top of them and then uh the csdm which uh my understanding is most of you will be familiar with gives you even a bigger perspective on the actual business context of those application services so tiing that up to the very same uh business application so this is uh a very important slide that lets you understand the the the reasons why we're talking about service mapping in csdm today and now talking about csdm this is the uh very latest uh common uh common Services data model is the 4.0 version of it and in particular I'm not going to focus on all these um elements that are very important to the csdm but today specifically I want to highlight the importance of the application service that is at the very center of the CSD M because they have actually uh many implications but specifically they are the very uh ones that allow us to have a service aware cmtb and together with them the there are the configuration items so our CIS that we populate into the cmdb and the dynamic CI groups that have relevance from an application uh service point of view so these are going to be three of the uh Main uh pillars that we're going to talk about today and they give the uh main importance of uh why we're doing service mapping now there are different approaches to service mapping clearly but we're still in the section where we want to understand why we want to do service mapping and here um there is a very clear answer in general when we want to populate the application Services into our cmtb this is done because we uh want to make sure to have an answer uh if a given infrastructure CI that we have previously discovered is a member of an application service and if not uh well we still be able to make a well-informed data driven decision so not having the knowledge of the application services and so the uh relationship between infrastructure CI and any application Services leads often times to Long meantime to resolutions and certainty in terms of ownership and uh the impacts on the very same customers and then we can have missed approvals because of the missing information in that site also unplan outages are typically part of not having service aware cmdb and at the same time uh it's very hard to allocate resources because they are not really aligned with the uh issue they were trying to um address now instead if we have a service aware CNB if we reach that level of awareness typically we have shorter meantime to resolution we have uh exactly uh the determination of which customers are impacted by specific issue we can understand the resource that needs to be allocated to that very same issue we can uh make uh informed and managed uh plan um assessments of the uh specific plant origes and then we can also have uh the um proper change of risk assessments and approvals these are a few of the very important um aspects that we need to consider whenever we approaching a service award in Tob but um I think this is enough for the introduction of the why so now we want to make sure that you provide your inputs as I said we need to make sure that you are participating enough in this session and we have the first poll already that I'm going to launch right now so I want to really understand which of the following statements is the more accurate for uh your organization in particular so are you currently discovering any resources and if you're doing so are you doing that through item visibility and specifically item discovery uh are you otherwise daging service graph connectors to popular your cntb or are you uh discovering uh resources and um mapping your application services so actually gaining that service awareness of your cmvp well please select the most accurate of these statements I see already plenty of uh answers here in this poll so this this is great this is great participation so thanks everyone for answering here I'm going to give other few seconds so everyone has the chance to decide uh which one is the most accurate statement for your case even if I see a very uh important common Trend I see someone is trying to raise their hands please make sure that you insert your answers in the Q&A box so we can make sure to actually uh address them for for everyone so please don't raise your hands there right so I guess we can end the poll and I will share the results with you so it looks like most of you the actual 58% of you is uh discovering the resources uh via item discovery which is great followed by 21% there is actually having that further layer of service awareness into their cmdp and then we have uh almost the same percentage of people that are either primarily leveraging service gra connectors to populate the cdb or discovering uh not currently discovering the resources so thanks very much for sharing these insights right so this was enough for the Y now we'll uh I will leave it to you bill for the how section and I think your muted there we go yes getting the control panel in a nice place so yes now we're going to jump into the how and we're going to be looking at the different methods or practices of populating a service map if uh we go with the concept earlier of a service not service aware cmdb right we're going to be trying to answer that ven diagram that question which CIS belong to which service so remember earlier we talked about the CN theb is the center of our knowledge Exchange in handoffs between our processes making it data driven but I also want to make the claim that it's delivered through application Services where we start relating that infrastructure giving it context so to answer a question you know a service map is different than a dependency view a dependency view just shows all of the connections being made regardless of the flow of traffic but based on what CI is in the center of that diagram and what it's connected to whereas an application service has context usually has an entry point but also we have in our toolbox three other techniques to populate our service Maps so that we're not just constrained to a top-down experience a process to process experience so specifically uh again when we look at the common Services data model we see that the application Services Center but also the dynamic CI group is something that allows us to capture Technical Services and it may be something that you could use also in the meantime or as a bridge to your service mapping uh Journey so that you can capture your CIS for your application the business service that you're delivering and being able to articulate what CIS belong to that service of course there's manual uh which essentially is drawing the map and then there's tag based which comes from uh your resource tagging where you have name value pairs you have a key name and a value U that gets used in a query to build a collection for that tag base map and then alt lastly is the top down experience where you're providing some sort of uh TCP information either HTTP entry point or a um database entry point uh some s of middleware typically it's a it is a web entry point and of course the machine learning aspects are contained within the top- down experience uh at the bottom of the deck I'll have a breakdown or the appendix of the considerations for these a deeper consideration and for also the technical aspects where they live in the cmdb and what's their service type okay so take it away again John right so the second poll here is uh really important for us to really understand which uh processes is are you currently using or do you plan to use your application um services for with which processes so I'm going to launch the poll now so please uh enter your choices in this case we have a multiple choice option so I saw that for the previous poll a few of you wanted to actually choose different options the aim of that poll was to really understand the uh closest scenario for each views but I understand that there's no black and white in could be very often in Gray there so thanks for sharing your insights in the chat now I see many of VI are entering their ANW so we really appreciate it and I'm going to give another few seconds so you can think about it more right so in 5 seconds I think we can close the poll and again great participation from all of you we really appreciate it I see hoping 66% of participants has answered already so that is great perfect so I see most of you has answered here so I'm going to end the poll and share the results right so they were the answers were in perfect order here as a matter of fact 89% of use is using the application services for it change management uh processes then we have 78% of you there using uh incid management and M uh for processes and then we have 50% of us that is using application services for aops and event management uh purposes and the remaining 42% for security incident and vulnerability response so thanks a lot and please be over to you thing yeah um so yes all of these and many more I know that there may have been um a missing item on the poll but that's all right I did get the sense that you know some teams are also using application portfolio management ties into our um strategic portfolio management where we can look at things like total cost of ownership not only from a Ops perspective but from a plan build run so as we venture into the different approaches right uh these are all the tools in your toolbox and um you don't have to use one over the other right there could be a lot of business drivers that could um limit you today and maybe tomorrow you could Venture into a more detailed more Surgical mapping with top down the um and so a dynamic CI group right is very easy to pull together it's a query of the cmdb and you can use one or more um methods of quering the cmdb to build the list it doesn't have topology it's a large list or it could be a small list and when used with uh itom Vis excuse me itom Health right we can quickly identify from a um which element or item in it is uh is unhealthy or critical and severity the um it can be treated or substituted much like an application service because it has uh the ability to update the service C Association table that's the vend diagram table or the intersection table of my service and my CIS that belong to that service so uh I consider that a a peer to application services and it could be something that can be quickly put together and tends to be utilized around um technology uh platforms or I guess you would say uh users or con providers of uh Technical Services in the data center so show me the list of production uh Tomcat servers show me the list of production IIs servers something of that nature so that you can have a quick uh look up Manual of course is just like painting on a on a on a map uh you you select your manual CI at the top and then you go to the UI and you can draw by adding CIS your connections typically these CIS tend to be more server oriented and not so much the process ones that are found by Discovery uh you know from the URL or from the entry point but this uh also um gives you a quick visualization gives you quick membership and perhaps is suitable for those things that don't have a high volume of change uh for example you may have uh some of your Mainframe or as400 or some other systems that you do not have uh IP based Discovery but they are loaded in your cmdb and you can quickly build the a map now for tag base we're talking about uh Cloud native either private or public and that they can be uh captured through the tagging of your resources when they're provisioned most most of the time though I've seen organizations uh have a u have missed that opportunity to tag their assets but through our tag governance feature that you can manage with policies which devices are missing their tags and then you can uh remediate those from the cloud providers and at this time uh VMware remediation isn't possible but again we're here we're using categories of uh either based on application ID a location a consumer a cost center something that basically you know identifies that resource either you know uh ec2 server S3 Lambda or kubernetes objects in the cloud anything that actually um you know represents a stack or uh container in in the cloud and lastly the top- down Discovery uh of service mapping is what most folks uh I guess consider when they hear about service mapping I start with a entry point IP and a port and we do host detection to determine what is that running process and then from there we either use patterns to read a config file or we use the um machine learning through um the traffic based collected data to build that process topress connectivity they can be used I guess when I say they the connection techniques right through the machine learning suggestions or the patternbase can be used on the same map as well as service mapping Plus actually takes it one step further and looks for large process-to-process chains to see if they can uh be represented as a application service candidate uh up until now our candidate method was using data that was collected from our load balancers and uh so some of those VIPs can be top level some of them can be intermediate level uh resource or IPS here with the machine learning we stretch that out to find the most resources connected and then present that as a candidate if you already had a service map built the connection suggestion feature takes that same concept of all of the uh if you will Downstream nodes that are on a map if they uh if they have any more connections to further progress the the the poy just a couple of notes the tag based manual Dynamic C group doesn't have a concept of clustering when you're looking at itom AI Ops or health whereas the top- down Discovery with connection suggestions or ml excuse me or the pattern connections there are the concept of clustering is capable there and much like any um kind of want to answer one of the questions um um the idea here is that shared resources can be a member of more than one of these types and you can use one of these types or two of these types to map the same application or uh as you progress through your life cycle of your your service mapping Journey it may be uh the quick visualization you need now so that you can leverage your uh event management space or change management and then as your um organization matures and you can Leverage The the process to process connections hopefully this kind of uh convinces and and shatters the notion right I don't have to do just discovered top down I have other capabilities in my toolbox to get my value right it's the outcome the service map itself is not the final Sol the result it's the capability of the to share the information to it change management Incident Management portfolio management strategic um portfolio management Etc so you know and also need some strategies how do I want to approach those techniques um where I look at you know the prioritization is being something separate from the the method I choose right it just tells me uh what I do first looking at Mission critical then key operations and then the remaining applications in my Enterprise and notice that you know ideally we want to do that top down right that might be a level of maturity that's not achievable today so we can always use a different technique but there may be a time and place and resources and funding to get you there that you can do the top down Discovery so what we I'm showing here basically is that uh through this decision tree you can get um where you would I guess you would want to be ideally so of like uh back to the itom health I need clusters or I need process to process topology that's always going to drive me to the discovered or top down with the two connection practices if I just need a simple list of CIS to manage my change management or if something is up down then a dynamic CI group may be the best outcome or the right size fit for Duty for utility okay any questions that haven't been fully answered uh John and Kim yeah we do have a few um that we are trying to answer in the back end not sure if you can open the chat yourself um maybe just pick one really okay so the business application is linked directly to the sdlc components and app service guessing calculated app service so um the concept of a calculated app service does come into play and I'll actually you see it here on this Matrix um if we dig deeper into the uh csdm 4.0 the sdlc domain um is optional version 3.0 is still very much applicable and depending on the white paper you have there is a relationship that'll go directly from the um from the the business application to the service application service there is still that is a part of the uh entity diagram and the entity diagram relationship so so we're not um deprecating or losing that connectivity but it is still there between a business app and application service the business app represents your portfolio it doesn't have any suffixes like prod or Dev it doesn't have any version numbers on it it doesn't have any uh Geographic designations as far as its naming convention it represents the business uh capabilities of a particular product in your portfolio through the to other elements of the design domain and so depending on how uh far your Discovery reach is or what you're using for your Discovery sources can determine how much service mapping automation is possible the first two you know dynamic CI queries I'm sorry Dynamic CI groups with the cmdb queries and manual they do have a lot of human intervention but you can um execute them in a way that they keep up to dat uh tag base has less and of course discovered top down is the most automatic way and perhaps this is probably where we were talking talking about our um Safe Harbor uh in the near future accv will be able to do uh patterns in in the potential future so that we would be able to do uh a form of horizontal top- down Discovery with accv there is a community article out there that allows you or shars with you how to uh add logic to make it tag based to feed the seem to be key value table our service graph connectors some of them actually do create calculated Services consider those much like um manual Services where the relationships are predetermined either by the CI relationship data or predetermined by the uh product that as that's being ingested app Dynamics and din Trace have very uh specific uh perspectives when it comes to mapping their services but we take them and then bring them in and land them in the appropriate infrastructure tables and then build a calculated service from that in in that fashion so that it cannot uh be uh changed manually but only through the service craft connectors okay let's see so next poll right so the final Poll for today and then we're going to go on our demo is uh we really want to know okay for those of you that are actually mapping their services so how many application Services have you created and populated so far we have different ranges here so you can uh just tell us if you're literally getting started with that or if you are somewhat in the middle of it or if you became an expert so you're um creating and populating application services at scale I see many views are already uh putting their answers here it's a another single Choice poll and I see many many answers uh keep coming here so another 10 seconds and we can go ahead head right so five 4 3 two one and I'm going to end the poll and the results so uh the majority of VI is actually getting started with creating and populating application Services um with the 48% uh of you is doing that and then we have 24% of you that is actually uh creating and populating application Services a scale and then 18% that it's somewhat still getting started and 10% is somewhat at a medium advanced level so thanks again for the great participation today this is absolutely exciting and we see many many uh questions in the Q&A uh section uh coming in for you so uh Bill not sure if you uh want to cover one more question or we maybe since we only have about uh 20 minutes you want to go and demo yes yes so really quickly uh accv agent client collector visibility that is um our agent-based solution whereas um most of our Discovery or initially was handled through agentless right through mid servers and credentials there are going to be some devices that don't um uh won't have that kind of uh Freedom or um security U policies May restrict um agent list Discovery right sharing password so that is our um agent-based solution for those kind of scenarios uh and also a quick question do I need to implement csdm before service mapping the uh that csdm is a part of a framework that should establish where you land your CIS um through the I would continue to um I guess you would say Advocate doing the crawl walk run I know not all organizations can do something like that in a green field situation so you're going to have various levels of maturity but following the white paper and some of those questions perhaps that might be uh useful in a another webinar so um but I'm going to go ahead and start looking at the mapping approaches and even with the calculated Services all of these techniques populate a service map which means the service C Association table gets populated therefore giving that exposure to impacted Services either be it change or be it um incident or perhaps even through my vulnerability in security or portfolio so today's demo I'm going to focus on pretty much a two-tier application H that is a web application layer talking to a database layer which is going to be front-ended by a software load balancer and I know that being time is a little tight I'm going to move a little fast with our demo but hopefully get through the key Concepts here so let's go ahead and go log in but what I wanted to share with so I've got five servers in my application stack for production and three servers in my application for my um uh de development so let me go back one here we go so these are essentially the servers that are running the processes for my uh collaboration and documentation application so I'm using the service operations workspace to help demonstrate or show some of the um the outcome capabilities here where we have our csdm relationships and then we have our built-in relationships of our CIS that built this application or standing up so this is just a simple list that can be used for um impact analysis and for itom AI Ops so here's our three services or excuse me servers for my um application let's look at the production one and this is one that I'm going to do more of a Hands-On demo with right now I know that I have five servers but I only have three of them uh or two of them excuse me loaded here we need to go find the other um three and the technique for building a dynamic CI group you first start with a cmdb group and what's exciting uh or special about a cmvb group is that it gives you a a way to um um gives you a way to use multiple queries to produce your list here we go so my so I'm going to just jump into the production one so it it yes it's one layer away from the dynamic CI group definition but we start with the cmdb group to to elaborate on our different ways to query the cmdb I can identify it explicitly I can do it through a list View and I can do it through a cmdb query Builder query and this is a part of the takeaway I guess I would hope that uh perhaps uh everyone would have a a learning opportunity here so you saw you know that I can if I do the show allc here it it should match with what I saw on the uh details tab of the service operations workspace I have my two servers the first one was identified based on it explicitly being um labeled in a slush bucket so to speak the second one here was done through the um list View or enhanced query um excuse me enhanced qu yeah enhanced query um encoded query on on the Linux table built in a ways that would always keep it up to date so we're looking at operational status as operational used for production as its um is another element of its filter so let me go ahead and show that while we're here so this is kind of one of those Pro tips when you're building the you uh uh leverage something where you know that you're using operational status right it depends on the Discovery capabilities and your cmdb life cycle management and this is the a way to keep it up to date over time over change so jumping back to the the other element of this where I'm using this query to identify it this is something that you may be able to leverage for uh products that are in your Enterprise but you don't have a discovery pattern quite yet for it or you haven't taken the application fingerprinting and uh made your own pattern so what we're going to do is uh take the running process data which is provided by horizontal Discovery and we're going to add it to the map and because the computer column is on it it has a natural inner join here and and because I may have a uh useful naming convention I can employ that as well either here in the query Builder or in the um encoded query so we similar what we had before show me all servers that match this but now I want to constrain it such that I I want to only bring in the servers that are running Apache so and I know that the name of that uh um process from service excuse me from horizontal Discovery comes in as httpd and again another approach I only want the ones that are recently found during discovery not those that have missing so if I run this I should Now find three servers and this same technique can be done for anything you know about the running process but you haven't quite built out the application fingerprint pattern for it so this could be very effective when you need ad hoc um Services being shown in Dynamic CI groups or um or onboarding a new technology so now that I go back to my uh definition here of the dbci group this is now going to bring in those three additional servers so if I actually now show all CIS I'll have all five and there we go that same technique that I showed with the cmdb query Builder can be also done using the CI relationship table to other C I that have already been discovered say tomcat web spere web logic IIs and so on all right doing a little bit of housekeeping so now hopefully my uh service now will be up to date with five CIS and this is stored in the details um like um the the list CIS that are on the the the service mapping view of this form you can list CIS and get the same content so that's quickly the um using it with the um query based approach manual is essentially the same thing uh like it says you start uh you specify a service I may not go through the whole thing here uh given the time constraint um but also need to share with you that the manual maps are also stored in the same table as the top down they just happen to have a different they just happen to have a different um service type and this get this allows for parity between a manual map and a discovered map so looking for service type here we go so you can quickly see um and then of course I've got extended classes also showing up in in this uh group but here you can see manual map and the way it was built I fixed it or hardcoded if if you will my entry point by using the manually created feature and this is table specific so uh it does not Cascade through so when you pick when I picked it for this I actually picked the Linux server class and specified it and then once I was on the map I was able to use uh the UI rightclick and add CI so right right click adci gives you essentially the same dialogue and you connect the dots like you would normally see in in the um Vis diagram or an architecture diagram just a quick question uh in the chat bill so we want to make sure that everyone is aware of this so you're asking if the media Wei service was manually created application service so yes the the the the CI class application services and that's a good point um with with the csdm you can specify or identify all your application services and then at the appropriate time populate them so so these CIS application service CIS are I guess I would call them gray matter CIS you have to give them a name you have to give them uh criticality status and you have to choose the method of population and that can be done um via the left nav picking the right Class Type you see here I've got top down tag baseed and so on or you can actually use the csdm manage Technical Services application Service uh wizard here you can specify the name and put in the uh gray matter attributes like owner managed by support group um he other values and then at future date come back and put in the um the population method and you may be able to populate it right there directly from The Wizard or it takes you to an advanced screen like this and you would come and and continue to populate and to answer a question uh that I saw earlier can I get the list of CIS that are in the map and that is the short answer is yes using the list CI feature um you saw that here and that would allow us to um export that data it's coming from service CI Association um so again in light of time I wanted to go ahead and begin the tag based one um because most of us are familiar with the top down and there may be um opportunity for another webinar on top- down pattern best practices I was going to cover that but I think given the time we're a little bit short but I want to encourage everyone to uh keep their Discovery patterns up to date and from the store uh Discovery and service mapping patterns as well as visibility content those are two of the store plugins that you would need to keep up to dat at as you um continue your service mapping your itom visibility um Journey so back to the workspace so here I've created a service map based on the application but it it has everything in it um what I mean by everything it has all of my eight servers and I really need to make a distinction between the two and to be able to do that in the tag space you leverage multiple tag categories so tag CI categories here I've already created um two but I want to show you uh quickly how some analysis of your tag data can come and support the um which Keys you use typically you'll have something that shows application ownership or um application ID application name um you might have something for environment so in this case I have two ways of saying environment and that's what lot uh categories allow you to do just like we did have here for two ways of saying app you may have multiple uh Cloud teams provisioning and they did their they rolled their own keys and this is allowed the category allows you to standardize normalize those um key values so here I'm going to make something called a key environment key and I'm going to use both environment and EnV is my inputs here okay now that I've done that let's go back here and right now I have applications that are out there like Mei Wiki but I have not made the distinction of development of prod I may also want to combine it with location typically I like to do at least two uh Keys sometimes three if you have multiple data uh data centers to be able to identify those assets uh so go back here and tag based families so once you've defined your categories now we can create a quickly an outcome of um of service Maps once you've select the order of your categories it is static I guess you would say it's immutable for those CIS and so I'm going to do application key first and then I'm going to do environment key second so all of the CIS that match both of these unique values will become our candidates so every possible combination um will be in our list today so you see media Wiki production mediawiki development and it uses the value of the tag as its default uh name but you can come back and actually rename it now that I've created them from the candidates they have to be enabled or populated uh manually first and then nightly there is a recalculation job that keeps these up to date and you saw that here's the category values what was chose first what was second and this is what I mean by immutable we don't want it to be um it's changed if you need to reorder the keys if you have two or more then I would recommend you create a new family from that another question that comes up often is can I uh take my tags tag Based Services and convert it to another type and the short answer is no that is not possible these are multiple right you can have two service Maps representing the same entity just different ways of representing the data um so going here really quickly I know um we're going to be short on time but I wanted to finish this out really quick with the uh tag based um key uh Service Group now I have my five servers and the last piece that I want to share with this is the reversal rules this will wrap up the um presentation then the traversal rules com combines both your tag information and perhaps some horizontal Discovery information that um can take the runs on data or hosted on data and apply it so that it can bring topologies because in depending on the the type of CI that's tagged in in most cases it's going to be the virtual machine instance that's what these CIS are but let's get the actual OS server that it represents on the map just navigating over to the other UI and going to recalculate notice right now all the CIS that are here are the end points that created the map and my original VM instances we go ahead and recalculate it it's going to take the additional discovered information IP Discovery and bring it into the map so now my list CI list is going to be much larger because it's going to capture the runs on Apache web servers and the MySQL and the um as well as the ha proxy a quick question on this actually will how often do we recommend to run Discovery in order to have their companies can have service Maps uh continuously updated without compromising performances uh I like to you with the leading practice of doing it nightly I know that you may need to you daisy chain your schedules right so that you do one area or data center or VLAN at a time so and doing it so that it kicks them off when the previous one finishes so that you get the best outcome but uh ideally every evening and I know that through some of these vo motion or events even in the cloud there are event opportun driven opportunities to either ReDiscover an asset or update the cmdb based on an event not not a up down event but actually you a change in configuration kind of event right I think we are about to wrap up else from your site Bill yep the takeaway here is the bottom row is all the items that were tagged and then using traversal rules was giving me the ability to map out more detail in this map cool so uh that that should do it for today and I'll go ahead John and go ahead and close CL us out that is great so hope you can see my screen again so really we had many many interactions with all of you so thanks for your great participation today um and make sure as we said before to really subscribe to your series as our next topic is going to be leveraging the agent C collector that we mentioned before for Sam cases that's going to be be on November 14th so make sure to uh enrolling into that session and we'll make sure to share the recordings together with the slides of today and the appendix actually so you can have even more value out of that deck so again thanks everyone for the amazing participation and it's always great to have you back to the series and we again thanks again bill for your absolutely amazing leadership and expertise that you brought to this event it was really um a privilege to have you on this and thanks Kim as well for helping answer most of these questions uh this is a great effort so thanks everyone and we look forward to see you all very soon please make sure to fill out the survey that you'll be prompted at right now and to recommend us uh whatever you feel like will be should be covered in the next episode so again see you all soon and take care