all righty I think we can get started so good morning good afternoon or good evening everyone and thank you for joining another great session today so in this session we're gonna talk about a one of the greatest and best innovations that we have released this year and in uh the recent uh releases for sure regarding item visibility for sure and we're going to have a special guest as you may read from here already so it's very exciting to have you here thanks all for keep participating to these sessions because we see that the audience is just growing and growing we receive great feedback and we have amazing presenters and amazing panelists and amazing supporters that are making sure to answer all of your questions there so thanks all and we really appreciate this now for those of you that are not familiar with this format uh this is this series is part of the live on service now webinar series and specifically it's the iton visibility and Cloud accelery Academy now I mentioned live on service now uh which is a great and successful uh webinar series that I really suggest you to unroll to because not only because our events are part of it but because they will really help you to implement our Solutions speed adoption and Achieve value faster if you want to can scan the uh QR code that you see in the slide or alternatively you will find a link in the chat now housekeeping items and you may be familiar with these uh please sure you should be already uh muted up on Entry but in case you're not muted please make sure you are and we have the Q&A feature that is dedicated for you to ask questions and we have amazing experts with us that are going to make sure that you will uh be able to uh have your doubts and questions uh properly addressed and whenever you're asking questions make sure you can introduce yourself we will really appreciate who you are to know who you are and uh what you want to chieve from this webinar as well uh we're going to have couple of polls in this session as well which we would really like you to uh participate into and then the session is being recorded and will be shared on the uh service now Community forum and after the session ends you'll be prompted to fill out a short ser and that really means a lot for us because we can really understand better what are your needs how has the session been for you if it really helped you achieve what you wanted to achieve and yeah it basically helps us keep it improving so we would really appreciate that now for those of you that don't know me my name is John Mario deluigi and I'm part of the amazing outbound product management team here for item and I'm specifically covering itone visibility and Cloud accelerate but get together with me we have a superstar today once again which is uh Shri Shri please feel free to introduce yourself yeah Shri suban I did the itam inbound product line of business what thank you sh I don't know if it's just me but um the audio was a little bit low maybe um you can check it maybe your settings are okay but yeah thanks for for introducing yourself she is leading the inbow efforts for the itun visibility product development so um specifically sorry for product management so it's a privilege uh for us to have him here with us today and uh before uh we keep going save hardboard notice we're going to talk about potentially some forward looking statement today so just wanted to make sure that you guys you all are aware and we can proceed now in today's session U as I mentioned earlier on we're going to talk about a huge Innovation that we brought to the market which is the ability not only to run patterns from the ACC but also to basically run service mapping with ACC which is a huge massive Milestone that we were able to achieve but first of all I just want to make sure that everyone is aware of why are we talking about service mapping in first place now you may have been uh familiar with this uh representation here that we gave of the level of surface contact awareness they can achieve for your infrastructure we have the basic layer which is the technology layer where you can have more awareness about how your actual infrastructure is and so having more information about your customer data center or your private management public cloud and all the infrastructure piece uh that are residing on top of that so all the middleware database web servers Etc and that's achieved with iton Discovery then if you want to have a business aware uh cmdb or an application awareness into your cmdb uh you need to gather application context so you need to better understand how the different pieces of your infrastructure are impacting your application services and that's achieved by uh mapping your application services and that's uh that means that you need to deploy service mapping and then you might be familiar with the csdm uh and basically uh that's where you really understand the overall business context so how your application services are eventually impacting your business so you can uh go from the deeper level of the infrastructural piece to the actual business impact now uh um we I just want to um for those of you that are not familiar with Discovery itself I will go really quickly through the main Concepts around Discovery and independency mapping and the four main steps of it basically it all starts with the soal Shazam probe right where we do the scanning phase we're basically scanning the network and see uh which ports are open so to find the active devices and uh you know within the defined IP ranges that we want to scan and after that we'll be able to gather the device uh type information and even additional information about the version or the OS uh information itself uh for the uh technology specific questions and that's called the classification phase where we're actually leveraging the classifiers and double determine what we'll use in the next two um uh phases we can see of discovery which is the identification section where we gather more information to determine whether we already have that CI in the cmdb or not so if a new CI will need to be created and we need to gather even more information uh to be able to eventually uh reconcile that information to the cmdb and then we have the exploration phase Where We Gather again uh just additional information on top of that as an example what uh what is the software that is running on the particular CI running processes TCP connections Etc that would allow us also to create relationships then between the different CIS this is in a nutshell What discovery does and how we get the dependency mapping view so we know how the different devices are uh communicating with each other so how they are related and then uh after we discover our infrastructure we need to be able as I was saying before to be aware of okay how how does that infrastructure piece relate back to the application services that we have running on top of those very same um elements of our infrastructure and that's when we have service mapping that can be done in multiple ways so whenever you have good uh tagging policies across your infrastructure State you're able to leverage uh the tag Bas service mapping you're basically leveraging the uh existing uh tag is tagging EST stat with the U possibly proper policies that have being preconfigured so that you have reliable uh tag based service maps and uh that can be achieved via the tag based uh families and uh CI tag categories and um that's essentially very easy for you to achieve value that's a quick way let's say to get to the service mapping once you already have those policies so you're leveraging what you have already in case you're staring from scratch and um you are collecting the right amount of data so you're collecting the uh TCP and basically traffic uh connections data um in between the different elements of your infrastructure you'll be able to perform the so-called ml based service mapping in this case what we want to do is to uh solve the big issue that you may encounter when you need to Define your entry point when you're trying to Define and to map your application services and instead will automatically provide you with mbased uh um service suggestions uh and uh basically you'll be able to get to new maps or to add to the existing U maps that you might have created just in a very simplified way and then whenever you instead have very Mission critical application services that you want to make sure that are mapped properly and for whatever reason and they are extremely important for your business you may take a slower approach a more manual approach where uh you uh really need to have a almost surgical approach to service mapping and that's the so-called top- down service mapping the top- down service mapping is so a slower approach that uh allows you basically to really have a deeper understanding of the uh of the service uh application service and know the service snap itself in this case you'll need to start from an entry point which can be a URL or connection parameters whatever you want to Define as the your entry point and you'll be creating an application service record based on that very same entry point that is been defined then you have the house detection phase where you are basically uh performing The Discovery or capturing via Discovery the uh sufficient information uh about the uh CI basically the CI details uh for mapping purposes and then uh you will have the CI identification phase where you'll be identifying really the uh applications that will be running on the uh discovered hosts the ones that you just discovered um and uh on based on the information that is provided from the entry point itself and then you'll be able to actually uh create uh do the connection Discovery so you'll find the configure relations for all these CIS that you have discovered checking the outbound connections so as you can see it's a more surgical approach that uh is uh again recommended for um just more application Mission critical application Services now um I know that there are a few questions and I see that uh than thanks so I see that bill is actively answering some and we have Steve as well and free that are uh giving the contribution there so thank you very much and I just want to have another quick look at why uh ACC basically we're going to be really quickly uh going through what ACC is it's basically an agent that you will install either on your endpoints or in your DMZ environments it's essentially an alternative to the traditional Discovery method that we saw before uh that um basically allows you to discover all those environments for which you don't have the right credentials you can't access them for some reason and again that can be your your Cloud uh you know uh Cloud VMS or you can have end end points that you want to monitor for whatever reason and basically you have the agent client collector that really uh is an agent that you deploy and you install on that very same endpoint on that specific BM and provides data back to your uh service now instance now the ACC is useful in many different use cases and helps different teams to achieve value faster specifically helps it teams for live asset view use cases or even Playbook Automation and virtual agent conversation use cases aops we have ACC uh that can be deployed for monitoring uh to collect uh metric data or live streaming and then for uh software Asset Management use cases it's possible to deploy the agent to collect software usage and and user asset and really reclaim unused software as an example as a result or for sa Ops use cases where you have security incidents inv investigation that can be uh performed thanks to um uh the agent client collector they sending back the proper data and so this is a very good view of how many use cases really the agent CL collector can help us with but primarily we're always starting from uh discovering from collecting data from those and points from those environments really and now uh we have a few polls as I said today and this is going to be the first one what we want to know from you is to really uh better understand uh why are you considering the if you are considering the agent client collector over the traditional agent Discovery approach is that because you have credentials issues you can't get your credentials or is it a push versus pull um approach that you're considering or is it a network and firewall issues that you might be facing or do you have airup networks or you have security requirements to support zero trust you can select all of these that apply and I see a few of you have raised their hands please make sure that you insert all of your questions in the Q&A box and we'll make sure to answer any of your questions now I see that thank you very much I see great participation already in this webinar which is fantastic and I'm really excited really about these new Innovations and we're going to get there just uh after this poll so um yes I'm going to give you another three seconds and we're going to end the poll and see how the results are I will end the poll now and the uh I'm just sharing the results so it looks like most of you have credentials uh issues to get credentials and we have networking and firewall issues and security requirements to support zero trust they seem like the most common use cases but also push versus Po considerations and er Gap networks are there as well so thanks all for chipping this great contribution and we really appreciate it now um I wanted to Showcase all the efforts that we put uh together with our engineering teams in order to really improve the agent client collector in the recent releases so um Shri has been coordinating most of this work so please Shri you can add your comments on this slide yeah I mean like agent client collector uh has been an huge Evolution you know you might have seen like service now launched ACC a while ago and uh the product uh has been maturing over the years where uh we added supportability to many operating system flavors uh uh we introduced new security posture measures for software Asset Management the agent now can collect uh total software usage metering uh on both Windows and Mac uh a lot of great enhancements uh not that was introduced uh uh but the interesting thing that happened in uh the late Feb store release is now the agent client collector officially can support two things one is the patent execution the other one is uh support for service mapping so previously the agent client collector uh was not able to execute a pattern and U in My Demo I'll showcase some of the examples on why you need uh these patterns to be executed to get U uh extended context of your application stack uh so now if you have deployed ACC now the same agent without any credentials will be able to execute all the application patterns uh that we are shipping through uh store. servicenow.com and secondly uh the on the service mapping side uh when you are adding an entry point like a top down URL uh then service mapping can also be fully supported with agent client collector on the target end points uh so you're going to see a live demo uh just uh know uh absorb all the other content uh that's there in the slide and we'll do a deep dive into this topic All to You JN thank you Shri yeah amazing Innovations uh really uh that's a significant amount of work that has been put through all these uh steps now uh what's new uh we saw there what has been the product Evolution we have a few slides to really dig deeper into the biggest innovations that we have released now so just with the uh Washington release it's finally able as three was mentioning to execute patterns by leveraging the actual um uh connection the existing connection from the ACC instead of trying the SSH or winm or Powershell to really connect to the system where you have deployed your agent and this is a massive massive Innovation because it also gives the flexibility to secure Discovery patterns for both agent less and uh really agent based Discovery for those that are supported and um you can really execute these Discovery patterns or environments that typically wouldn't be accessible or we saw there all of your pain points that you just share with credentials and so on and so forth so um that's one part of it and the other part is that you can finally now leverage the agent client collector to run both top down and El based service mapping that's because the agent client collector is connecting is basically uh collecting running process and traffic data and is running uh connection suggestions so that you can uh again leverage and exploit the Amo Bas service mapping features and leverage the uh uh basically Amo base uh suggestions and on top of that you'll be able to go to the hybrid mode we call it so uh the Discovery admin is going to be able to run service mapping by leveraging both agent L and agent based discovery that can vary on the type of environment that you're are discovering really um so this again a huge uh Innovation this is supported from Vancouver release so um you you can definitely make sure to test it out and we're going to see in a moment now how it works we also integrated uh directly in the service mapping workspace the unified map support and I see a few of you are raising their hands please uh we can't uh unmute your uh each single of you we have many many participants today so uh we can only uh listen to you via the Q&A um section and that's very appreciated um basically with the unified map support you can directly access the combined let's say dependency View and service map in a new uh view a new uh way of visualizing them both and that's directly done via the service mapping workspace so this is a way more Innovative and more modernized experience that is going to allow you to get the best of both worlds let's say uh which is very very uh exciting as well and also we really listen to you now many of you have been voting for the uh mid server affinity for service mapping feature and this is one of the top voted ideas on the idea portal so if you're not familiar with the idea portal this is a very very useful tool for you to suggest us uh some announcements or some new features and this is the demonstration that we actually listen to you because we uh have introduced the uh basically Mar way to select the mid server for service mapping we're uh practically leveraging the um Mid selection uh from the horizontal Discovery history with service mapping which is allowing larger organizations that let's say with hundreds of locations to really improve their uh overall service mapping posture and um this you know service mapping is basically supporting this new feature from Washington release so Washington in this case will be a prerequisite but now without further saying we have a great Deep dive session that sh is going to bring us through so please three over to you yeah thank you John appreciate it um uh so we'll first cover some of the concepts and then we'll show know things uh know in Deep dive mode uh let me know if you are able to see my screen yes yeah are you able to see the Deep dive slide yes okay perfect thank you uh so firstly uh know uh let's look at the prerequisits right on how to get uh some of these new Innovations into your production environment so on the pattern execution for agent client collector you need to have the latest uh agent client collector framework and the visibility package uh that is shipped through Feb release uh we do have backward compatibility support for ACC over patterns which is primarily going to support the horizontal Discovery and uh once you have the Feb so release for ACC framework and visibility have the latest uh pattern Store app as you know like we have two content uh that we ship one is the Discovery and service mapping patterns uh which is again having all the net new content and the itom visibility content stab uh which is primarily to have all the other patterns that was not shipped to through out of band releasers all the patch fixers uh are all getting through this content so I would strongly encourage you to uh deploy both the store applications into your production uh know setup on other the service mapping side you need to have the new service mapping plus which is the latest uh uh code know that is shipped through uh store. serv.com we'll again show you some of the latest release um but the new uh know ACC over service mapping is supported only with Washington uh family relies because some of the code has to be supported in the family release code and hence there is an a dependency to Washington time line uh but we don't have like backward compatibility support similarly the uh Affinity uh on Mid server for service mapping it is one of the top most voted idea that is also shipped through Washington tamland and hence we recommend customers to upgrade to Washington uh if you want to VI the ACC over service mapping feature so that's the prerequisites and uh the first step okay so when you install all all those applications right the first and four more important step is to go and activate a a property setting uh called APPL classification Behavior Uh setting and this setting once you activate uh it is going to know allow the agent client collector to run patterns so to give you an example how uh know this setting looks like uh for example I've activated uh no the setting so in the CIS property file you would see this APPL classification Behavior setting and it has three important uh choices one is off the other one is simple the other one is full off means you're not going to create any application CIS when uh no ACC is deployed and an apci is a it's a category that you would see in csdm called CM dbci app to give an example when uh an Oracle database is deployed into a Linux server uh when a Pon process is detected right you using the process classifier you run the pattern in the exploration phase and the pattern will create an oracle CI and that CI if you look at from the parent class it sits in the cmdb C PPL so in a real pattern world the pattern gets executed but in the agent client collector world before patterns were executed we were still allowing customers to create a simple application shell C based on the process classification so in your um scenario if you activating pattern execution the default is simple I would encourage you to uh know change the setting from simple to full and once this is uh done then you may need to restart your mid server which is again an very important prerequisite uh after updating this property the mid server should be restarted so then the next time the discovery runs on the agents primarily the ACC runs all the policies based on uh know the defined intervals and during that point in time when the process is detected when the process fingerprint is uh uh is uh classified right then the these process classifiers will start executing patterns instead of creating shell C so this is a prerequisite uh know for all of you to know make a note two things activate the setting make it to fold and restart the in right and then you will see an uh a checkbox like know with your instance name where it will say that hey we are going to now run all the patterns and in your agent client collector environment if you have configured allow list uh it is super important to go and configure the allow list to have those commands wh listed on the target ACC this is again a feature that is being added for security uh use cases so just in case if you in your environment if you have activated allow list uh you may need to know take that allow list uh and then start um updating some of the commands that uh know you can activate and you may ask me like okay how am I going to know what commands should I whitel list and there is an fantastic KB article which will have a default allow list that will have at least a quick bootstrap experience it'll have a set of commands that we have already whitelisted for you and uh so you can use this KB article and then uh know take some of those uh automated allow list and if you have not seen this application uh called patent designer enhancements so this application once you install uh it again comes with an interesting utility called command validation task uh where uh we will allow you to have uh uh some of the commands that can be tested over uh uh know uh your credential as uh uh no uh use cases and here is again a place like where we have a table of all the commands that patterns use and this is another place for you to go and do pro no research on what commands gets executed by patterns and then you can also curate your own all love list know to see what commands can be approved the edge and the at the ACC level right to go and execute uh on the target device so this is another approach so strongly encourage you to take the out of the box uh allow list that is already documented in the skabb article uh but at the same time you can curate your own allow list there are two important settings that you should be aware of uh one is the uh uh know primarily the uh the mid Discovery agent command mid time out setting which is primarily like the max duration the mid is going to wait for the command to get executed on the target device so I have seen customers using uh mid server in know some us region targeting servers in apj right and you would have a long uh uh no weit time right you need to plan those timeouts in such a way that when mid is executing a command the default is 60 seconds uh but if you are uh know having an complex architecture and you have resources all around the globe but your mid is centralized then you may need to know reschedule some of those timeout settings similarly there's another setting which is primarily the max execution time which again like an ACC can wait for default 60 seconds to run a command uh if this is another uh know variable that will give you more control on uh know how long you are ready to wait for the agents to run if the resources are busy if the machine is like already struggling know with all the CPU Cycles right so this is another setting for you to consider if you want to wait for more times so with these two settings like now you're all uh know uh good to go to pretty much uh Kickstart your Discovery right with agent client collector you install the ACC framework and ACC visibility and now you have activated the application uh CL know parameter that I showed you so now the agent is all ready to run the patterns and you may ask me how do I know that ACC is being used to run the pattern so we created a view like in the agent client collector you can activate this discovery view so in my instance um let me go to my agent client collector firstly when you install all the ACC the ACC is going to register all the agents that that you have deployed into know this table where you would see some of the discoveries being completed so if I click on any of this uh no discovered host you can see an uh in a section where like know these agents are able to collect the same set of data that my agentless uh know technology gives me right where you can see all the P know the application C you can see the uh TCP connections install software data which is super important for your software Asset Management outcome uh running process data and if you look at it like we are already collecting a whole set of good information that can be used for service mapping so in the later part of demo you're going to see how the ml based mapping is going to consume this data and then provide uh some automated recommendations uh but on the agent client collector side like say once you uh know you have installed uh know these agents let's pick up uh uh one of these agents where the agent is installed the data collection is all happening but on the right side you see this uh pattern logs right where uh some of those patterns that I'm executing on this target uh uh node using agent client collector and you can see uh know the logs and in order to get this view you just need to go and instead of default view you can go and add to disc Discovery view so this way you would be able to see uh know all the patterns that are getting executed by agent client collector uh it's again not going to give you more conformance that like okay my ACC is deployed my patterns are getting executed on the ACC you can see the pattern logs and you can see what commands are successful what commands are failing if you want to more add more commands to your allow list right this is your methodology to uh know do some trial and runs right and make that allow list much more workable model the other thing that is very important for you to note down is uh so in the uh pattern Discovery pattern log we added a column called executed on agents and whenever a pattern gets executed with the help of an agent this flag will be now set to true so you can also do uh know some good troubleshooting by directly going into the pattern logs where you can just use this flag executed on look for all the ones ones that are true look for the managed IP address and see whether the patterns are know successfully being executed and the other validation that you can also do is like whenever uh know an agent is executing a command you're going to see this text in the pattern debugger log using ACC connection to execute a command on a Windows agent or on an know Linux agent uh so you would see this text which is also giving you more uh conformance that uh when the uh know the negotiation is happening between the mid and the target end points you don't need any credentials it's automatically recognizing an agent and it's bypassing all the credential requirements and the mid is sending all the commands that you want to execute on the target either for horizontal Discovery or for top down Discovery the agent is executing the command and then collecting the payload and then sending it to Mid and then know it get processed into your instance so these uh troubleshooting steps are absolutely important and then like a few more tricks right on your patn debugger which is again uh you know the debug option that many of you users to troubleshoot uh know each and every line of code right that we ship uh you can now use use ACC agents if you use ACC connection so this means the patent debugger is smart enough to recognize that hey I should not wait for a credential uh you know in order to do the debug but I can use the existing agent client collector on the target device it will make connection and then you can still write trible shoot the patterns exactly like how we have done in the agent list discovery mode uh where the know the individual steps can be validated you can know collect lot of more evidence whether the commands are successful on the target uh no host or not uh the last one is like primarily getting into no even the mid mid side right like where uh uh when um this active session is active then you don't have to give any mid servers because the agent already knows that which mid server the agent is communicating to there is already an full duplex connection established between the agent client collector and the mid server and this intelligence is already there within the platform so we know how many mids you have how many ACC connect s are there how which M mid server each ACC connection is using so we are not going to ask you to give a mid right during the debug just use this connection and know and then the magic happens and the last one is like even when you are running uh certain commands uh you are still like going to have detailed uh know error which will actually tell you whether the timeout has happened because you don't have privilege or even if you are installing an agent not with the local system account or with some service account and that account does not have access to certain files and folders uh especially in the top down map right when you want to read a certain config files you need read access to go and uh know uh look for those config files look for the connection strings and if you don't have access right you're are going to see those error codes on hey I I'm trying to execute a command and my agent is trying to run that command but somehow the ACC no agent that is being executed with the process does not have access uh to go and read it right and then it uses a default timeout and then you going to see those failures all those pattern uh debug options are all super important so with that note like uh know I can show some quick demo on how this works so when the agent CLI collector is installed as as I said you're going to see all the running process and from the process when there are fingerprints uh that we have given in terms of process classifiers you're going to see all those patterns getting executed so in this case uh know if I take this agents I can click on host collect collect host data it's going to perform a collection uh in near real time on the target host but you can have an simple policy that can also you know collect uh data programmatically when this happens when the process uh know is detected in the exploration phase like how you do it in IP based Discovery we are going to run a lot of patterns and these patterns are application patterns and these patterns will be executed when the agent is deployed right so this this is again absolutely needed for your uh uh you know all the horizontal Discovery use cases know where you have this uh uh agent client collector uh know visibility uh and uh you have collecting inventory data and you're also now going to collect all the application CI data right in this example like I have an oracle mission where all the Oracle related uh uh know uh data sets and web logic and all the other uh topology data that is needed uh for your typical horizontal Discovery is all being collected by agent client collector so previously we used to create just a shell C so now with the Feb release right now you are executing the same set of patterns and uh you'll be able to see the same set of topology that you expecting typically from an agentless technology right so that's Point number one the next thing is like how do I run uh service mapping which is again a very important topic right so for service mapping right I have another environment where uh know in this example know added uh in simple uh SharePoint endpoint like where have an IP address and port number uh when I see the map so in this case again the agent client collector is deployed on the target host so previously we never allowed uh know any top down mapping or any ml based mapping to happen with ACC but now with this entry point uh I can actually see uh how ACC is able to discover the hor izontal Discovery CIS but also it's able to build that surgical mapping experience so if I see the discovery LW and if I search for using ACC connection you can actually see like from the entry point how the ACC that is deployed on the target host is able to take some of the top down uh execution patterns right where if it is a config file based detection uh know where you need to go and look for connection strings uh so you need to on those patterns and when ACC is deployed now we know how to execute those patterns without asking for any credentials and you can actually see this using ACC connection where the top down mapping is able to know perform the same set of uh data collection and uh know perform a quick top down surgical Discovery you may also ask me like hey what about the the new MLB mapping uh which is again an awesome feature if you haven't activated it uh no you can actually go to store. servicenow.com uh install this application called service mapping plus and uh once this app is installed uh you're going to see uh no inexperience workspace like this right where in the workspace you would see the service mapping plus and what it does is like uh know something very interesting right where both your agent base and agent list is collecting lot of interesting data sets like because in a iCal service mapping you need to give an entry point uh it performs the top down Discovery from the load balancer goes to webform app form database forms so it has to build that surgical mapping experience but in the last year we introduced this machine learning base map where if the traffic data is already visible in uh know in the cmdb can we latch onto this uh golden data sets analyze synthesize can the ml give give me any recommendation so that's how this capability was built and all you need is like once the uh service mapping plus is active you can go to this uh uh application Readiness checklist dashboard uh you can pretty much run this checklist and except adme all other settings should be active because these are all some of the prerequisites for machine learning to uh look into your data sets uh the predictive intelligence plug-in will do clustering analysis and then it'll start looking at building recommendations and one thing that you're going to see is like all those ml candidates so these candidates like where machine learning is saying that hey I'm automatically looking for Meaningful traffic that is happening between these uh resources and I can build those recommendation in this example there is a an application that's talking to TNS listener which I know that it belongs to know my Oracle database I can always like click on this recommendation do a preview map and one thing that you would see is like now with the Washington release we introduce this new unified node map and you need to have the latest cmdb workspace experience and there is an simple property field that once you activate you will be able to see this brand new unified experience node map but in the preview map like now you are able to see the map that can be created without giving any entry pawns so you as an customer purely looking into those ml based recommendation building a service map on the fly so I did like build an ml based map like call checkout services if I click on view map you can see how the brand new experience of unified node map uh uh know it's it's visually stunning it's uh simple for consumers you'd be able to use and consume this uh even in cmdb workspace experience uh and all the know the related Chang related uh know incidents and uh know your timeline view everything is all know embedded and we are making lot of Investments to make uh service mapping uh know available in aops experience and uh in itm service operations experience and so on so this is absolutely super important for all of you to take away so if you are like uh trying to do service mapping with ACC have the latest version of agent client collector and framework and visibility have the latest uh patterns code that is shipped in the latest March release uh deploy the service mapping plus uh and look for all the potential traffic data uh run the check you know Readiness checklist and then uh you can start curating some of those service Maps the other thing you may ask me is like hey in the ml powered candidates all you are seeing is like process to process communication right there is uh uh like sometimes these are all cryptic in nature unless like you know exactly this TNS listener belongs to an oracle listener right how how am I going to understand all those application fingerprints we have also solve that problem for you so all you have to do is like search for Discovery admin workspace uh which is again a brand new workspace that we are building for all the discovery administrators it is supporting Vancouver and Washington DC and once you install this app like I've installed Discovery admin experience here one of the things that you would see here is like uh uh know uh a place called content 360 uh where some of the tabs that you're not going to see it's all coming out in the future releases uh but what you're going to see is content 360 and you will need to go and configure for this content services it's primarily like uh know a data sharing where you're going to say that like hey I'm going to send all my unclassified machine learning cluster process that is sitting in the cmdb process cluster groups and once you start uh know shipping these things uh we are going to send a whole set of classifiers so if you look at it like almost like uh you know we are build a a set of process classifiers uh based on uh know some of the standards that we see and and the good part is like now know we have an service that is fingerprinting every single process that's running on your estate and now we will give you an better enriched topology in terms of horizontal Discovery and you can also use this to create an install software data it helps your service mapping so I strongly encourage you to uh know deploy know this specific Discovery admin experience once you install go to content Services setup activate the uh know the process fingerprinting and SNMP oids and the good part is we are going to ship this content on weekly basis right a typical pattern updates comes on monthly basis but now we are going to ship all those fingerprints to you on weekly basis or all the oids that will be shipped through know the same content distribution services and when more and more customers are joining this Community Driven uh fingerprinting we have librar who are looking into know these process classifiers they're cataloging and they're using the normalized publisher and product from software Asset Management library and they are curating these application fingerprints they are sending it to your instance on weekly basis uh which is again uh know an absolutely and most important thing that you should take advantage of so that your cmdb Discovery topology becomes much more comprehensive your service mapping becomes uh much more meaningful and context rich and you have more context in terms of uh your software Asset Management use cases where you're able to identify how many of those uh uh know installed application is also running because your uh cmdb Sam SB installed table will give you that context of what software is installed but it doesn't give you whe whether the software is running or not right so that running uh estate can be now visualized by your uh application fingerprinting and strongly encourage you to activate it and more and more experience will be unlocked with this new discovery admin experience uh and we will do future webinars on how this brand new experience is going to enrich your error handling like I saw a lot of uh questions around like hey do you have an catalog of error because Discovery errors are super noisy today so we are applying some of the machine learning tactic to do clustering to perform uh analysis of what errors are are super important for customers like credential errors how to troubleshoot credential errors uh know we're building a lot of tool chains like command validation task which I again strongly encourage you to try and then make your experience seamless so with that in mind like John maybe need your help know to run the next call and then we can uh maybe answer some of the questions absolutely just one second I'm going to share my screen again see it's here right you should be able to see the poll right now so we have poll number two for today and I'm going to share it right now where we really want to understand and by the way thank you so much free that was an outstanding session and demo and we really received positive feedback already and thank thanks everyone for answering via the Q&A uh function we have a great fantastic dream team today there is supporting on so thanks all and yeah we basically we want to better understand uh how do you want to uh leverage the ACC if you're planning on using it and which outcomes are you planning to drive with it so are you going to uh use it for cmdb outcomes or for software asset management and software optimization uh specifically outcomes security incidents response it service management for incidents or Regulatory and compliance use cases I see yeah I see a great uh engagement so far so this is really appreciate it I see a lot of answers are keeping coming so I'm going to give you another few seconds and then we can uh stop the uh end the poll basically right so I will end up now and I can share the results with you all and we can see that U most of you are going to use the leverage the ACC to drive cdb related outcomes followed by software management and IT service management outcomes uh and then also Regulatory and uh security Insurance response use cases so thanks all uh this is amazing and thanks for your great interactions um now question I know that we had a ton of questions there in the chat and specifically the Q&A function so thanks all for this great participation um maybe uh stre you want to pick up some of the U most important ones uh some that are worth to mention here live yeah mainly like uh one of the uh no question I see is like okay we have multiple service mapping techniques right especially in Cloud uh I see like lot of uh know questions tailored towards like okay I'm trying top down Discovery for cloud right what should I do so what we see is like we have a lot of cloud Discovery customers uh and customers who are using it know our Discovery even in containers with the kubernetes iner and the CNO uh that we launch and predominant most of the customers are using tag based mapping uh where uh uh know the strategies to democratize service mapping and setting up standards uh uh you can always challenge saying okay I don't have good taging standards right that's a common uh theme that we see uh but um in in the world of service mapping especially if you are starting a cloud Journey have some good tagging strategy we also have tag governance application that can tell you what resources are tagged and not tagged uh but at the same time I would strongly encourage you to democratize service mapping process where otherwise you you'll be having a bunch of team members and all they will do is like just do service mapping day in day out right uh it is a complex activity uh it requires uh knowledge on the application stack ml gives you some kind of an bootstrap experience by with 60 70% coverage because machine learning is again using the existing traffic data and some of the questions uh we did see that okay what happens to passive nodes right so those uh servers will not be definitely included in that ml based recommendation and machine learning um based experience and top down can coexist so you can always start with your top down and you can augment your topdown mapping with machine learning based recommendations uh as well so a lot of questions around uh uh no fingerprints and uh patterns like yeah strongly encourage you to uh try uh the new discovery admin experience go and opt in and uh maybe if uh uh know if you are ready to even partner with service now right reach out to me or Steve or John we will be happy to have one-on-one with your uh or and do these sessions one-on-one right primarily to socialize how the new machine learning based mapping can help you to accelerate your mapping experience how the know how what is the pattern Road mapap right that we are chasing for the next 6 months and even the application patterns that we are creating through this new content distribution services right if you have uh know some immediate needs we have customers reaching out to us saying hey I've been audited and I need help uh know we can now do surgical file based fingerprinting as well using uh running process uh detection which is again a pretty cool concept that is already available with the uh know the this uh new experience so yeah please reach out to us and we can uh do more enablement session with your customers fantastic uh sh thank you thank you for that do we have I see questions keep coming so you want to check do we have a last one maybe that we want to address before we wrap up yeah it's like I think predominantly we answered most of the questions uh uh so we will be publishing this uh webinar uh know again a quick key uh takeaway and in this webinar is update your agent client collector to the latest uh febru relase have your store uh content for Discovery and visibility content to latest release install your service mapping plus to the latest release Discovery had been experien and opt into content services and when you're ready to execute the pattern activate that property setting from simple to full and then setup timeouts and that's it right you are ready to run patterns on the agent client collector and if you're thinking about uh service mapping uh both top down and ml right can be supported on on top of ACC and we do support hybrid strategy where you can have agentless Discovery and agent based Discovery together in your environment and we can take uh traffic data from both uh Technologies and we'll be able to process and uh fingerprint and provide you this service mapping experience so with that note thank you again know for the opportunity fantastic yeah thank you Shri uh for sharing all of your great knowledge here but we have a great scam that has been helping us throughout so uh thank you Bill Ean dog Schulz Ryan Zuli Steve Amerson uh and of course Tre uh for presenting this was a mega team effort and uh I see a lot of questions which mean that there was definitely a lot of interest in this topic we unfortunately need to wrap up now because we are at the top of the hour so um please make sure that you will uh enroll into the live on service now webinar series with the link that we previously uh provided there and uh we're really looking forward to see you in the next episode that is going to be held on uh April and yes uh so unfortunately uh we we wanted to keep talking to you and keep answering questions but it is a time constraint for today but again we really appreciate your time and we ask you for just one big favor please make sure that you fill out the uh survey that you're going to be prompted up after this webinar ends and make sure that you express uh all of your um uh Impressions about this webinar uh you give us feedback so we can keep improving this session but again thank you for being disengaged thank you so much for your constant participation we really look forward to see you soon and thanks all for really presenting and participating here thank you