all right let's get started well good morning good afternoon and good evening everyone and Welcome to our webinar thank you all for being here uh today we'll be covering on how I Tom visibility streamlines it Asset Management uh and today's session is part of our item visibility and governance webinar series which we host uh once per month here on the community so please feel free to join us for future events uh and today's session is also part of the live on servicenow program which is a program that we have to help you know connect to you guys with our product experts so that you could you know more easily deploy our products and so that you can gain faster time to value so please feel free to join us for different topics you know today we're focused on itom we've got topics across every area of the platform such as HR CSM itsm of course just a a quick bit of housekeeping so everyone's line is muted so please use the Q a feature uh just to ask your questions throughout the session we have a team of people that are going to answer them we may choose to also ask your question live and and um you know and answer it live uh so please also feel free to introduce yourself when you do ask a question we'd love to know who you are where you're from uh we're going to have a few polls today so we ask that you please take those polls it'll help us get to know you better and uh you know and plus where you are in your journey uh so this session is being recorded today and it will be shared on the the servicenow community Forum after the session's over uh and it will also be posted out to our our servicenow YouTube channel uh and then after the session ends uh you'll be prompted to fill out a short survey so we of course we always appreciate your feedback there so I'm Steve Emerson I am the host for today's session I'm the outbound product manager for itom visibility and governance here at servicenow been here for about five years uh prior to joining servicenow I've been in multiple I.T roles across multiple functions so I know what it's like to be in most of your shoes and today we also have several other panelists uh and you know and presenters so I'll start with SRI SRI if you could do a brief introduction hey good morning everyone uh srinivas subramanyam data product management for item been with service now five years uh prior to this I know worked with companies like Hewlett pack at Walmart Sovereign OT thank you very much my name is Chevron well I joined the stress team about two and a half years ago I'm focused on the agent Clan collector as part of item visibility right yeah hello everyone my name is Bradford Blair I'm a part of the I.T Asset Management outbound product management team and I um like everyone in the it Asset Management business unit we work a lot with our brothers and sisters and I.T operations management really happy to be here all right thanks everyone so I'm going to turn things over to Brad who's going to kick us off with our first area which is why automated visibility is critical for it Asset Management yeah thank you very much Steve uh confirming that you can see my screen share yes okay great we're gonna go ahead and jump right into one of those poll questions so everyone uh Steve's gonna go ahead and bring that up and this is our poll question how do you discover your it assets today you can select multiple choices so let's go ahead and take 20 seconds there to fill that out real quick I'm watching my clock here how are you discovering your assets today all right that's been about 20 seconds why don't we go ahead and close that poll please you can take a look at the results uh very excited to see that a lot of you are using servicenow agentless Discovery and then um we're starting to get some adoption for agent client collector those are definitely the premier ways to get uh your um Discovery information uh not only for your I.T operations management use cases but also for your I-10 use cases of course there are situations where third party tool may be required and we do offer that capability as well um and then for those of you that are uh discovering assets yet you're still in the right place um it's never too late to start doing that and we're going to discuss that here a little bit more so I'll go ahead and move on um and I do uh I'm traveling remotely today I apologize I can't meet you uh with my uh video on but um I'm traveling remotely and uh the laptop I have right now the integrated computer isn't working so I appreciate your grace in that um when we talk about Sam tools that are not run on a cmdb they'll often miss most if not all the current asset activity so when you have those Legacy tools that are dependent on imports and exports into your cmdb it's putting you in a position where the moment there's a break in that process for import or export you're going to have a situation where you don't have that current asset activity and when it comes to Asset Management that can be disadvantageous because for those of you that you know are aware of how servicenow really works um to Define asset management um we have a focus on the life cycle so that complete technology asset life cycle when you're starting uh at Inception all the way through deployment and then to retirement uh what we want to do is make sure we have that information uh primarily from Discovery but also we'll talk about the other data sources as well when it comes to entitlements so when we think about the uh value proposition of servicenow and we get into this here a little bit more with this slide when you have your Discovery data on the cmdb the now platform and then you have the ability within the same data model to then have that work hand in hand with the capabilities that come with Asset Management you're going to be in a position to have automation across that full technology life cycle and that's what this presentation is going to be about here a little bit more obviously very shortly we're going to get more into uh the discovery um parts of this equation but just giving you a Viewpoint as to how the that work will benefit your end uh your end results when it comes to Asset Management how software asset management works on the now platform you're going to get that raw inventory data Discovery is the Premier place to get that from whether it's agentless or the agent client collector agents and then you're also going to put your purchase information in there that's then going to get run through the content service to start normalizing that data so that you're going to get consistent versioning in addition for your various various products that are out there we're then going to run that through our compliance uh this is where the publisher packs come into existence so those license metrics that are unique to specific publisher things like that and then once we get those compliance positions you're going to be in a position to start taking action so whether that's you're looking for cost savings you're looking for risk mitigation whatever that may be and these are the some of the outcomes that are going to be driven by that compliance action and the great thing again as we were talking about earlier that content service feeds into itom and some of the other products on the now platform so you're going to have full uh asset lifecycle visibility these are the publisher packs that I mentioned and so these are powered with that data from Discovery so when we're getting into some of these more advanced use cases for some of the bigger uh software vendors these publisher packs um with software Asset Management have the license metrics and the metric attributes built in so that when we get that data and you import your entitlements and then you click compliance it'll begin to calculate those positions for you um right then and there and then as I wrap up here just a quick plug on how ham works on the now platform so Hardware Asset Management very similar there's obviously a bit more of a focus on the uh Discovery data if you will so that inventory data that you have out there again Discovery is a fantastic source for that and then we're also going to run that through the content service so a lot of times what will happen is you'll have semantic differences in terms of the product name or the model name and so our content service goes ahead and normalizes that so you have consistent naming for your five different flavors of a MacBook Pro 15 inch and then that's going to feed right into these workflows that are based on that life cycle that we were talking about and so those workflows again are going to open up some action-oriented uh workflows that you can take when it comes to asset spend or things like that and just like with Sam that content service feeds into it operations management that's everything I wanted to cover for Asset Management I'm really looking forward to a tree and several have to talk about here with um Discovery specifically uh you know that specific part of the use case here so thanks Steve for having me on thank you Brad uh behind uh all workflows we need to have a very powerful data layer and this is the place where item visibility comes in for a rescue because when you look into the data strategy we have a discovery technology which is agentless Agent based that can collect infrastructure Hardware information software information dependency data some of the licensing requirements that we need to solve for you demands different dimensions of data in today's webinar you're going to learn some of those dimensions and see how servicener Discovery can help you to collect the data on the endpoint side similarly you need to Source the data from mult no multi-source data sets like sscm titanium Jam of we also have agent client collector that can help you to collect the same set of data and Sovereign is going to show you how you can tap into the agent based technology to enrich your data sources let's look into the the meat of this webinar the software asset management and Hardware management that demands some critical data sets right when we look into this software Asset Management the install software estate is the foundational data set that is needed for you to know create Discovery models normalize and then attach it to a software model which then can be used for your reconciliation engine not to provide an effective license positioning the install software estate again can be collected by three different methods package manager method which is again the most easiest way to collect the data now looking into registry keys you know your deployed packages anything that is visible there is an easy data collection we have pattern based approach that can again collect some interesting data dimensions a good example is like if you want to have complicated data collections like Oracle database version edition SQL database version edition weblogic taxido no your no your other complex softwares that demands you to detect the insults of predata by looking into different dimensions of data sets that's available for patents we'll show you a demonstration of how this technique can also help you to collect the data the third important Dimension is file based Discovery a good example is log4g when no the shell hits uh hard right everyone was scrambling around how do we detect the you know the presence of java the presence of 4G and for software Asset Management in particular Java audits right demands you to effectively track you know where this software is deployed because it's an easy for any developer to download and install uh without understanding the legal requirements to meet the licensing uh no needs and the three methods that I am showing you like the package manager method is widely used uh no this is again very easy to activate I will show you the settings that is needed for you to activate this data collection uh this will collect the data into install software table a table that was specifically created for software Asset Management use cases the table called cmdb Sam SW install and once the data collection comes in then a Discovery Model gets automatically generated this will be used by the software Asset Management normalization layer to normalize this data and then a software model gets created which will be used by the Sam reconciliation engine to validate you know the entitlement checks up the second dimension is the pattern based approach which again you know will give you complex data collection the third important approach is the file based Discovery will show you a demo on all the three pieces before I show the demo on these techniques a file based Discovery in particular is very interesting technique because once you activate it you need to give them information like the location of folders that you need to scan typically program files like slash opt these are all common places where you put software you can also give extensions to scan like for example you want to scan star.exe in all program files you know it's a simple configuration to set it up uh we can also discover SW ID tags which is again important for IBM software if you want to detect them uh because this SW ID tags will have the iso tagging technique and some of the big players like IBM has adopted it so we can discover the tags we can also create install software data based on the tagging information and before I show the demo a quick note on the cloud Discovery because when you look into the estate majority of your workloads are moving to the modern infrastructure like cloud and containers so you are going to see how our Discovery technology can also help you to collect visibility to the multi-cloud setup by looking into the infrastructure as Services past Services we will be discovering this in an event-driven Discovery fashion but also for software Asset Management we collect some very interesting dimensions of data a good example is uh bring your own licensing pay as you go spot licensing identifying those physical servers these are all dimensions of data that is absolutely needed for your software Asset Management to car not to have this data set in your cmdb so that when you perform those complicated calculations now you will be able to comply with some of the regulatory standards or by the licensing terms and agreements defined by the respective vendors a good example is Oracle database deployed in AWS versus an oracle oci both have different licensing uh you know techniques and metering if you look into SQL Server deployed with Azure versus AWS will have different uh license and rules but also the output will be completely different so the first step is you need to know a SQL Server exists in AWS or Azure you need to know their uh know whether you have opted in for bring your own licensing or pay as you go so those you know types are going to really help soft Asset Management Drive some of those outcomes uh so with that like let's look into a quick demo of some of the capabilities that I just showcased so from the basics right when you install a software Asset Management you're going to see a workspace called software uh no asset management workspace this will give you visibility uh no for your licensing positions and and again Sam works with two sets of data your entitlement data which you have to import which you'll have to you know automate with your procurement right so that that data will tell you what you have purchased then you need data from Discovery and visibility which again you know is something that we can help you with our technology like primarily agent as an agent based and also with our service graph approach uh some of the major Publishers like Oracle Microsoft Brad showed you a wide spectrum of uh Publishers and if you look into those Publishers you you'll be surprised by the the complexity of Licensing metrics used by individual vendors a good example is Microsoft SQL Server uh you know will demand you to uh you know have licensing policies based on uh no per processor per core or Cal so all those different dimensions first has to be recorded on saying hey what licensing that you have purchased but based on the licensing metric that is defined by the contractual agreement as a software Asset Management module will go and compare and will give you compliance reports like here in this case it's a parkour metric so this means like the expectation is firstly we'll have to detect SQL Server we'll have to detect uh no the Windows machine where the SQL Server is running and thirdly we'll have to collect all the cores that are assigned to the SQL Server so that we can satisfy the data requirements needed for software Asset Management so let's uh you know give you a quick uh demo on some of those capabilities for login um so if I take a SQL Server as an example let's say I have discovered one uh that's running in my Azure so when the discovery runs it collects a lot of interesting data sets right so primarily when Discovery itself is no it runs through stages as you know like you know we'll do an ping sweep using Shazam Pros we will first I classify identify and once we have discovered those windows servers then the patterns gets executed the pattern will collect information like version and Edition and we've also extended the patterns to color SQL Server components like your Oracle options so those are all the complicated data collection where Discovery can help but along with this like you know when I look into the the actual form view of this Windows service obviously you might have seen you know the core elements that we collect the overall B course no that is B being provisioned for those data sets the install software as state especially in Windows the registry key is an excellent data source for us to collect this data when we find the running process data anything that matches a process fingerprint in this case uh no a SQL dot a server.exe a fingerprint that belongs to a SQL Server when this process is detected then behind the scene a pattern get executed and the pattern will you know come in like collect all those dimensions of data needed for software Asset Management not to be served for this data source and behind the scene like you you might have activated the entire node Discovery no with a very simple configuration console so if you have not seen it the setup itself will take couple of uh no minutes where you'll have to have mid server a server that is will be actually performing some of those uh scans mid server sets in your environment and IP range will be allocated to the mid or a group of mid server but once those uh no elements are available the infrastructure like credential either integrating with your vault is all available so then the configuration console allows you to quickly no setup what you want to discover like quickly set up things like hey you want to detect install software estate or not and once you have this setup ready and when the discovery runs uh the discovery will collect and start software estate for you the other important uh you know information that you should be aware of is like the entire data model uh where we store all this data it's called cmdb SW s what was that name so if I open up a Linux server account if I open up one of those records so you will see the all those software data that gets collected or maybe I'll open up this Windows server so we store this data in a table called cmdb Sam SW in Saw right so the stable I was looking for and and this data model is very important for you to understand because this is how the entire normalization process is being designed uh when Discovery goes and collapses raw install software data will populate the data into this table like let's take a very simple example like a Java jdk right so in this case uh the Java 1.8 version of open jdk is installed in several places but behind the scene you see this reference model called Discovery Model so if you remember my slide right the first step in the process of normalization is uh no the discovery will collect this raw data where Discovery knows that this this specific version of software package is being identified in 76 plus machines and Discovery will populate the discovered publisher product and version but behind the scene software asset management will try to normalize it with the normalized publisher product conversion and on top of it Sam also adds things like end of life end of support for the software technology so this will allow you to plan your life cycle management technology portfolio management uh no life cycles where a software like Oracle levenji end of life then you need to plan in advance like which application services are going to be impacted you know based on this end of life software so those are all the key outcomes that we can drive with the discovery and Sam and our APM solution uh no coming together to solve this complex problem statement for you the next dimension of uh not data that we wanted to show you is the um you know the software data that can come from file based discovery what is file based Discovery so primarily like you might have seen this documentation site it's a separate plugin that is needed for activating this discovery and once you activate this plugin there are some basic configurations that are needed I will show you what are them but it's a very powerful technique to go and scan a file system for a file for a switch tag and once we identify that file this data gets collected into a table called cmdb file information table where software asset management will have a set of library to identify what this fingerprint is all about and the fingerprint is defined by the name version and other dimensions of data that no we collect based on the Discovery like the size and once the fingerprint is available like you you will also see an install software data getting created within the table and the discovery sources will be SN file based Discovery and if you are a SW ID tag based data set is being generated you will have a different Discovery Source called SN swid tag based Discovery otherwise the discovery Source will all be serviced now and anything that is unmatched will go to a table called cmdb unidentified file set table and in your software Asset Management you know you will have an uh a setup called content Services setup typically we encourage our customers to set up know this data set for ham and Sam so that we can go and collect this data anonymously and the data that comes from this layer will be sent to a centralized repository where a set of librarians will look into the data set that is anomalized like no any Discovery models that we have not yet normalized or partially normalized any Discovery Model that does not have the life cycle data sets like the product lifecycle data and for Sam obviously there is a lot of other non-discoverable elements like part numbers and and other things where we can also help you the processor name normalization is also important especially because uh when we wanted to solve some complex calculations for Oracle and SQL Server uh IBM you will see the processor uh core Factor table which will demand you to map a core factor that is being assigned to the processor type one of the things that we do discover is like if I go to my you know Discovery data you will see that like you we are discovering the manufacturer model information of the processes and behind the scene uh no vendors like Oracle or Microsoft will give you a core Factor matching for this specific processor like Xeon uh no idea you know you will you have to use the core factor of uh you know 0.5 and which will be used for your software Asset Management calculation and hence it is important to discover these dimensions of data what CPU processes what course vcourse collect the data sets like uh node or version where the software is installed and then give these data sets to software Asset Management not to perform complex calculation and you may also ask questions like hey can you discover the same set of data uh no from cloud and the answer is absolutely yes in this example this Windows server is running on an Azure workload and it can also show you another example of an Oracle database deployed into AWS infrastructure and when you perform your Cloud Discovery schedule the first step in Cloud Discovery is like collecting know your Cloud assets data using you know the apis and service accounts and once we have the Deep dive Discovery data we can collect the same set of data like the V cores running process install software data on top of it the patent gets executed so that we can collect you know oracle versions editions uh you know and the entire complex data sets needed to satisfy your requirements and if you have not activated your Cloud Discovery like strongly encourage you to use the cloud operations workspace uh which is like again super easy to set it up have your service account in place uh AWS Azure Google Oracle Cloud IBM Cloud you know all we need is service principles and service accounts with read only permissions so that we can collect the metadata and then you perform the Deep dab Discovery data either by deploying an agent or agent list or by service graph there are multiple ways to you know collect this data for uh you know satisfying your software Asset Management use cases when you collect this data the other important use case for software asset management and item team is the cloud insights for cloud we also help in the cloud cost optimization where we need to collect the tagging data we have to collect the price information so the cloud insights module is also part of our software Asset Management Enterprise which again will use the cloud Discovery data to perform some of the software Asset Management you know calculations and before I give the flow to Severin I want to quickly show you a few other things one is the file based Discovery this is again my favorite especially when you wanted to collect uh you know identities based on files like here the activated a file based Discovery quickly performed a scan identified some of the files like including log4js and so on and setting up this file based Discovery is again you know pretty straightforward now all you need is like you know go to your configuration console and it is a separate plugin not a store application you need to request this plugin through high support once the plugin is installed on your machine then you can use the configuration console uh you can search for configuration cancel and you'll see a setup wizard where you will see this activate file based Discovery and there are some basic information that you have to input like I know the folder structures to scan uh what folders that you wanted to ignore any exclusion list or any wild cards extensions that you wanted to collect and so on you can also no no control your scans by providing effective throttling rates whether you want to scan the uh no SW ID tags or you wanted to use the process path so it's a very simple setup once you set it up the first time Discovery runs it deploys a script to the Target host uh the next time the discovery will collect the data that is coming from the previous scan so that we don't have to keep Discovery as on hostage right waiting for file based Discovery to run because it's going to scan the target file system again my recommendation is like no please configure the folders can in a limited fashion so that the results are effective you don't want to collect you know all the files sitting in SQL and right that was just going to create a lot of noise in the cmdb file information table and it'll be useless right so Target the folders and know the use the data for complex calculations like Java uh no and any other technologies that can be detected by purely by you know defining the file fingerprinting technique so with that I'm going to handle the flow to Severin so that you can learn about the agent client collector and how we can help you in the end point estate 7 over 10. all right thank you very much SRI and well thank you for for my own personal training well you've been working through a quite a lot of content here and uh well to everyone in the call you see that our platform the platform platforms is very configurable so as you on board into a new uh implementation project adding a new data source or configuring a new integration piece make sure that you review this kind of configurations you see what you need so that you configure it for uh for what works best for you and with that let me share my screen on the agent give me just a few seconds here there we go and feel free to ask questions in the Q a we'll have time to to go for this after representation all right so in the in our last poll we've seen a bit of adoption here in the audience on the agent Clan collector so for those of you who are not familiar with it this is a new way to collect information on your target systems extract that information send it to servicenow for processing and provide an alternative to your horizontal discovery which may be which may be more suitable for maybe some some of your Cloud environments some of your restricted networks in your data centers and also for endpoints so end user compute devices this agent is not just for one specific targeted purpose but to answer many of the needs you have that you can use on service no platform so we can ingest events and metrics with the agents that will feed into our aiops platform on service now with item health we can interact with the agent from servicenow instance for regular itsm use cases where we can provide live data from the agent to enrich your tickets for your ID support to better serve your company Associates and also we integrate with our secops sir product to enrich security incidents using the agent of course with the agent Clan collector we collect all of that um all of that information that you have normally with regular discovery on on the assets information and system information you know we'll go to that in a minute and last piece here this is about helping you to make smaller decisions on your licensing on a licensed products for some use cases the agent collector itself can execute additionally custom playbooks and we embed a open source solution that is called OS query that can enable you to extract data much more easily across multiple platforms on Linux on Windows on Mac and integrate them directly with servicenow foreign collector we enable our customers to collect two types of data sets for Sam Beyond just the in-source software on on your given endpoints we can collect the last access time of applications on Windows and on Mac and funnel on Windows we can also collect the total used uh the total usage time for specific applications all of this is collected by the agent and then as you define your software Reclamation rules we will be able to store that information into servicenow software usage tables so that you can make your own decisions to uninstall or relocate licenses for for the users that need that oh I'm sorry so time for the demo any questions so far Steve as I find a way uh no you can proceed I'm I'm just answering one right now all right thank you all right so the agent Clan collector is available on the store this is a store app um if you want to evaluate it uh you can always do a get here you select your non-production instances if you don't have licensing yet and you can evaluate the features from there as you have your agent Clan collector installed you will have access to the uh the Google dashboard we have that will help you to take your actions for maintenance making sure that the agents are working the way you expect on your platforms I can see a thing with zoom here all right so on my demo instance I do have a couple of environments available I do have some systems on Google Cloud on physical compute that is actually sitting on my desk some VMS on AWS on azure I do have a Mac OS over here as well um and regular VMS in data centers so opening up just a few records here here let's pick the Linux and the Mac you will find the usual information for physical assets so the manufacturer information model ID of course to get the asset created CPU or arm information so your numbers as well as the system information fqdn DNS Etc and just like usual with a traditional Discovery you will find the serial numbers storage devices partitions file systems tsp connections running processes we also introduced recently the data collection for OS users that can help you to identify those user accounts or shared accounts that maybe should not be there anymore so we help you for this kind of use cases by collecting that information and then as I have item enabled on this instance all of the in-store software is being stored into the sample tables that you can see here software installations so this is what you have with just spinning up the agent basic uh how we say out of the box installation and for endpoints you can collect usage data for a specific list of applications are we good on time yeah all right so I defined a few Reclamation rules some of them with just last used date where I select the type of my Reclamation let's use date instead of total usage time I assign a software product that has been normalized and with that mapping you can see the kind of processes we're looking after to do that mapping once the agent Clan collector runs and by the way it runs with its own policy right you will have this design Discovery for for Windows in particular we will collect that information and store that into the cmdb and as we collect the data we'll even store it into usage so you can see the destination for this last use date here for matching where I was able to collect that information and as you can see here very recently I was able to collect that on what is that system that's the uh the system on AWS on the small Intel knock on my desk same thing here collecting some data and assigned to that specific user so this is use case one you just want to get the last year's date you can enable that and we'll collect that from the system now the second option is to have a much more Surgical data collection that will require a bit more of deployment on the target systems configuring OS query to call every so often how many processes are running which ones for how long they have been using CPU Etc and by doing that we can give you uh quite some insights about how often that application has been used so for example here I installed Visual Studio code on a couple of systems software products that has been normalized Visual Studio code looking for this process normally code.exe I guess that's for Mac as well and from here well we have quite a bit of processing that is hidden normally from the customer but at some point the data is stored into a staging table that is here as we collect that information from our systems we don't want to have too many uh too many actions on the destination table and software users table so we have some pre-processing that is being done in in the staging area and from that we do have a scheduled job that one's normally um so so often I just forced it manually for the scope of this demonstration and you end up with your total CPU time that is displayed here any question on the chat Steve not specifically to this but it's more about Discovery in general maybe it probably applies to both this and agent list but how can the CI name be equal to serial number upon discovery how can the CI name be equal to the serial number on Discovery so normally the CI name is defined out of a box with a couple of properties that we have we normally pick up transport hostname but you can configure it to have to include the domain name into it uh actually on the store app I believe I put a link because I forget that link always here Discovery properties and you can change your behavior so for example you want to use um the wmi name you will be able to enable with wmi instead of a DNS configuration you want to have a full sqdn include domain there you go you have it I don't believe out of the box is required me if I'm wrong but we can just pick up the the host name the serial number instead and one of the problems watch out there are multiple types of serial numbers it's quite a mess to be honest on Windows on Linux you have a bios serial number you have a baseboard serial number but if you want to tweak that in the three processing pre-ira processing scripts for traditional Discovery I believe you can change that behavior to put the CI name as being the the serial if you want to have a specific format and for the agent current collector we we allow customers to change before it goes to the IRA to change the format that would be custom so be careful then whenever you update it what I can tell you is that for the agent Clan collector there are recently on our August release I believe we give you the choice of which serial number to pick up I was very insisting on that so if you prefer the baseboard over the BIOS you can tweak that just with a system property I talked a lot any other question nothing related to agent client collector all right thank you very much so thank you Sabrina yeah you see questions on in Danish right Hey What Can we discover within containers so that's and I think I missed this narrative but one of the things Discovery can collect is uh as you know like uh know the if you look into the dockerized versions right it's obviously this kind of Discovery can no discover your Linux missions but also Docker runtime we can collect information about uh I know those runtimes along with this we can collect information about your running containers so here I have a SQL uh you know container that's running on a standalone Docker image and if you look into this topology you will see the Linux server Docker engine but also the you know the entire Docker image and the running containers know that are running within the Standalone Docker runtime and if you look into the image perspective right you will have information like uh know how many places where the specific image is running and now you'll have information about the repo and so on the same is true for no things like kubernetes I know when you look into you know things like you know the things that we can discover is like Community Services spots containers uh one of the things that we can effectively collect us not just the you know the infrastructure view but also we collect the tags based on which we do the tag based service mapping but on top of it like the entire topology of data that can be collected with more event-driven Discovery fashion like you'll have visibility to the Clusters uh know where the services being hosted you know the pods and the runtime but the most important thing is like running containers but also the you know the docker image from which uh no those containers are provisioned and we'll have information like how many containers are running for the specific image ID which is again important for the software Asset Management tracking the the last piece of uh know the demo that I know I've been asked to run is on uh you know a deep dive into uh the the Oracle license certified mechanism as you all know like servicenow is being certified or validated or verified by the Oracle uh g-las services and the primary use cases uh you know to have give you the compliance position uh not for Oracle so with that like maybe we can start with the poll and then I'll do a deep dive into the narrative Steve please relay support let's just proceed I don't see that poll question here in Zoom got it okay perfect so the Oracle License Services uh the LMS or is the no previous term license Management Services so they go and partner with a lot of tool providers to go and verify and validate whether the data collection coming from the engine can be fully uh no be used for your licensing audit because a typical uh like a license audit or a license verification will take at least eight to ten weeks where you'll have to deploy the LMS scripts on the target host you'll have to collect the data manually you'll have to consolidate and you try to hire a third party auditor so it's your responsibility to you know be prepared to make sure that you are in compliant with the uh know the audit regulatory standards defined by the respective vendors and in case of LMS the good news is like yes we do have uh no an out of the box solution that can help you to proactively collect this data so if I can share my screen uh and the first thing that you should be aware of is the Oracle page that defines like you know where service now is verified and validated to collect this data mainly for the Oracle database and Oracle Fusion middleware uh Services the first step is like you'll have to download this app called data collection for Oracle glas and once you download this content uh it will like import certain patterns into your pattern Library so you'll see this scoped application called data collection for Oracle not glas and it will have some extended data collection you still need to have uh you know an user ID and a password that means an application Level user ID and password so you'll have to go to your credential table add an oracle user ID and password that will have select access to some of the tables for which like no the data collection will happen and and if you look into the actual data sets so let's go back to my instance and if you search for Oracle you will see a bunch of data here in this uh you know store scoped application so firstly a dashboard that gives you how many Oracle instances are there how many middleware components have we discovered like you know your Fusion software tuxedo and other software which can be easily detected with configuration files we're going to give you a breakdown on versions and so on but the most important thing for the audit is like these six different tables like the detail table options table overview table and these are all super important for node to meet your audit requirements for example Oracle options right and here the script that is provided by the auditing team right and again we are just using the exact same script that will be executed by the Auditors like we'll collect the data for you and we'll store all those data into a single unified table similarly Oracle DBA users right which will uniquely identify the list of all users where like you can even like uh you know see exactly what data is being collected we recommend not to touch or modify any of those automated data collection uh no because this will again go into the tampering view of the data but once the data is being collected the only thing that you have to do is especially when you and have been asked to provide this data is a simple dashboard where you'll have to go and say that hey you wanted to share this data for Oracle database or middleware download it download the vcenter information and VM information just three simple steps that can know where the data can be handed out to your Auditors with that right I'm going to hand over the flow to Steve to have his final thoughts yeah thanks very much SRI I appreciate that and uh we do have the last poll um added into Zoom so let's launch that really quickly uh before we wrap up the the session while we're doing that I'll just share my screen so we just like to know what is your experience with how long it takes for you to provide Oracle with the verified installation and usage data if you have a you know a request from them for an audit now what SRI just showed is the ability for us to collect the Oracle data um and to provide to Oracle for an audit right um it's always good to understand your license position and that's where Sam Pro comes in uh so what Brad talked about earlier in the session that's where Sam Pro would help you understand well what is my position right I've inputted my my entitlements and I've done all my Discovery to see what I'm using so uh we can go ahead and end the poll and share the results uh so the biggest answer here is I don't know right uh but that may maybe because most of you aren't involved in this process but weeks seems to be the prevalent answer here um and you know as Sheree mentioned it's about six to eight weeks on average so let's go ahead and and just wrap up with a few last slides here so we do have some time for questions do we have any questions in here that we need to get to let's see I don't see any open questions certainly if you have any you know questions please put them into the you know q a right now we have a team of experts that can answer them but I'm gonna go ahead and just wrap up here so we do have some resources available for you uh which we will put into the we um we will put these into the um into the chat but also uh we're gonna put this deck up on the Community page as well so have no fear you will get access to these resources one of the things that we do here at servicenow is we we create our roadmaps uh based upon a lot of customer input right so it's driven by the needs of the customer you guys so we have a an idea portal which has recently moved from our community over to our now support page uh so please make sure that you go to the right place now um this is where you can submit an idea and our product management team will look at it and possibly your idea if it receives enough upvotes uh we will consider it for the roadmap it's not guaranteed but we will consider it uh we do have some uh final areas here as far as uh well you know what we'd like you to take away um one being you know we like you to you know relo you know rethink your hardware and software Discovery approach based on what you learned today are you doing it correctly uh we want you to begin trying out some of these products in sub-production right get your stakeholders excited about it based upon what you've done uh of course we are here to help so if you have any questions please feel free to reach out to your servicenow account teams or drop a comment on the Community page and then finally we'd love to hear your success stories so please share them with us as you start to realize value from these Solutions please you know you know just let us know and we do have our next webinar coming up on November 29th uh which is where we're going to cover um our new capability around automated service suggestions and how you can speed up time the value for service mapping so please join us uh so with that said just a you know a quick recap on how item visibility can you know help you achieve service operations Excellence overall and I wanted to thank you all for attending today have a great rest of your day and we'll talk to you again in November thank you all