how's it going everybody my name is zachary easley i'm a solutions consultant here at servicenow and today i'd like to take some time to talk to you a little bit about how tag-based service mapping works how we get it set up and how we can start discovering our cloud resources today before we dive too much further i'd like to quickly just show our safe harbor notice this is just to cover my back in case anything changes in the future moving on here we have just a quick high level overview of the steps we're going to be walking through today we are not going to be diving too in depth into these first two steps as this presentation assumes that you have a basic understanding of the cmdb and discovery though we will quickly touch on how we can start to get this ball roll rolling with these first two steps so with that let's go ahead and jump into the instance so again we're going to briefly touch on those first two steps as we are assuming that everybody who's watching this video has a mid server and a discovery running on that mid server but for anyone who might not be quite there yet we're going to quickly jump into how we can get a mid server installed and validated and discovering so to get things started go ahead and type itom guided setup into your filter navigator and you'll have this itom guided setup module here for you to click into once you jump in you will have a get started button over here and that will bring you to these different guided setups that you can walk through for our case we're going to be walking through the mid server and our discovery so once you click in we have a couple tasks here to complete the first one being creating our mid server user this is going to be the user profile in your service now instance that is going to be logging on to that mid server as you can see here it's very simple form whatever username you want to give to that mid server user and its password as you can see here i already have one built out so i'm going to go ahead and mark this as complete moving on we have our download and install mid server task so as you click into here we have a bunch of different flavors of downloads for your mid server whether it be a windows msi installer a docker recipe or a linux download you can go ahead and grab those here as well as if you prefer to download it as a zip you can grab that right here i've already installed a mid server so i'm going to mark this as complete as well and the final piece will be validating that mid server now as you can see i already have a mid server built up and validated i'm going to jump into that just to show you as you can see everything's up and running and i have also run discovery with this mid server so let's go ahead and take a look at what that might look like from a discovery perspective i'd like to jump into the discovery schedules and from here i like to click cloud discovery this is going to give you an easy walkthrough for getting that cloud mid server discovering and grabbing all the information you need it's very simple you're going to select your provider in this case aws whatever you'd like to name it and then it'll walk you through the service account so actually let's go ahead and just take a look at what that looks like here it is so we can either build a new service account or we can select one that we've already created in my case i do already have one set up and created but i'm not going to quite walk through testing this as i already have run cloud discovery so let's take a look at what we've actually discovered and some of the resources that we have at our disposal so here i am inside of our cloud resources dashboard and really quickly i just want to show you the kind of data that we are grabbing now that we've run cloud discovery right and our main focus as for today's presentation is grabbing those tags right so when we've gone out and run discovery we've found this ec2 instance we can see all of the related items you know when it comes to the dependency maps but what we're really interested in are these tag values now these are tag values that were built in aws and discovered by servicenow and now that we have our tag values we can start to utilize this tag data to begin building our tag-based service maps now for today's presentation i'm not going to be using this specific uh ec2 instance but this gives you an idea as to what it is we were looking to discover so that we're set up to move on to the next step of getting our tag-based service map built now before we dive too too much deeper i do want to show you how exactly we grab those tags so if we jump into our discovery patterns here this module should be in your instance we can type in aws inventory and now we can take a look at this specific discovery pattern that goes out to your amazon aws instance and starts to search for those key and value pairs now this pattern should be by default in your instance but if it is not you can go ahead and grab that from the servicenow store but this will be a crucial part of making sure that we can build these maps so now here we are inside the tag-based services um module here now right off the bat we can see these have some kind of wacky naming conventions like rewards colon colon dev you know rewards processing colon colon qa we're going to get into more about what that naming convention really means in the near future but for today we're going to go ahead and just take a look at one of these service maps so we can get an idea of what the final product is going to sort of look like right so we have our entry point and we have our uh service map and that's relating us to these four ci's now we don't have a whole lot of data in here but that's besides the point the idea is this is where we want to end up so for today's demonstration i'm actually going to go ahead and whoops let me jump on back to there i'm going to go ahead and actually delete this rewards processing qa service map and we're going to build it up from scratch so give me a moment while this deletes okay so now that that tag-based service is deleted we can go ahead and move on to the next step of actually bringing it back so the first thing we want to do is go to our ci tag categories and from here this is where we can start to define the types of keys that we are looking to correlate so for this example i'm going to jump into application service and we can see here a couple different variations of tags that we're looking to grab for building this service now these all have very similar names like app app service application app service they all are relatively pointing to the same things the idea here being that if you have one resource that is marked as app for its key and another resource that's marked as app service or something else we can go ahead and correlate all those tag keys so that we are talking about the same application because as you move between different departments and different versions sometimes these keys can can shift in terms of their naming conventions so this way we can build out and ask for all of the keys that we're looking to add to this ci tag category i'd also like to note that there are multiple different categories that we see often like kubernetes or environment as being categories but again they all work the exact same way we are looking for these specific keys and from there we can start mapping those keys and values to building our specific maps so let's go ahead and move on over to our families so here's our tag based service families if we go ahead and click into one of these for this example our application services and here's where we can start to peel back that funky naming convention so what we're doing here is we are defining the logic for how we want to uh correlate these tag values to each other so as we saw earlier we built those application service tags those had names such as uh or key names such as app app service what have you and our tag category for environment with tag names such as env or environment or whatever what have you now what we've done here is we've said okay let's go ahead and take all the tags that have these application service keys and all the tags with these environment service keys and let's correlate their values together so if we actually scroll down here we can start to see kind of what this is starting to look like actually what a better way to view this is by taking a look at those candidates so here we can see our application name being rewards processing and the environment being in that qa environment same here here's the one we deleted earlier our rewards processing application key and our environment key being qa so if we actually just go ahead and select this service that we want to go ahead and begin mapping again these are coming from our aws environment and we go ahead and map the selected you'll see it's incredibly quick we've successfully mapped this service because we have all the data in the cmdb already now we've just gone ahead and built out that relationship so if we scroll down here to the bottom we can see our new map we're going to go ahead and recalculate it just to make sure everything is up to date great now from here if we actually go back to our tag based services there he is that's our uh service that we just deleted and now remade and if we take a look at our map it should be exactly the same as what we saw a couple minutes ago here it is and just to dive in a little bit deeper into this map we're actually going to open up this dependency view real quick not very important but what i really want to do is look at this form for the specific tomcat reward server and if we scroll down take a look at that here's some of those uh key uh tags i'm sorry here's some of those key values that we were talking about earlier such as our key named application and in this case it looks like there was a key named stage but the reason why we got the naming convention we did is because of these values so we've mapped our application value rewards processing with the stage it's in being qa now if we were to look at the rest of these cis will notice that they also have some flavor of of these keys as well where we're grabbing those values and building out our service map hopefully this presentation was helpful and gives you a good starting point on how to get those cloud-based tag-based service maps up and running thank you so much and have a great rest of your day