foreign and I am a business process consultant here at Lightfest today I'll share with you the new cmdb 360 view in the Utah release starting with the Utah release the multi-source cmdb feature is part of the cmdb 360 View cmdb 360 provides all the functionality of multi-source cmdb and additional capabilities such as an analytics dashboard and you query functionality cmdb 360 view provides out-of-the-box aggravations and Analysis of cmdb 360 data which can be used to track activities and identify potential issues of your Discovery sources within this view you can create and schedule different types of queries and reports to explore the cmdb data in this new workspace experience you will notice that there is a new menu option for the cmdb 360 View here you can see any potential issues with the configuration item data that's being collected across multiple sources also you can get a summary of your sources created manage queries that you have created and you can configure the parameters of this view to your needs the cards in the discovery sources tile will show you aggregated counts across all your Discovery sources and the cards on the coverage tile will show you a breakdown of configuration items per the number of Discovery sources reporting those configuration items the Utah release includes a new Wizard that allows you to easily create and schedule custom queries across all of your data sources three type of queries that you can configure to your attributes first of that is a basic data query which you can create a query that you can use to explore your cmdb 360 data queries your cmdb 360 for CIS matching your criteria that are reported by specific Discovery sources the second of which is the source Gap analysis this type creates a query that you can use to analyze gaps in your reported cmdb 360 data it queries one or more Discovery sources that report a CI and one Discovery source that doesn't report a CI and finally we have attribute level comparison in the third type this allows you to create a query that you can use to identify CIS with attribute values that differ across multiple Discovery sources or against the cmdb it queries at least two Discovery sources and or the cmdb for configuration items that match your criteria now let's navigate to My Demo instance and see how we can enable the cmdb 360. the cmdb 360 dashboard for multi-source data is available on the servicenow store for customers that have an item visibility license Begin by activating the icon Discovery license plugin if you don't already have it next navigate to the cndb 360 properties by searching in the application navigator cmdb 360. properties you'll find it under configuration cmdb properties in the cmdb properties screen make sure that the first property here is checked this will enable the cmdb 360 View by default the cmdb 360 tracks Discovery Source information or CIS from both cmdb and non-cmdb classes however you can independently enable or disable tracking data of the cmdb and for non-cmdb classes by unchecking one of these two properties next let's navigate to the cmdb 360. to access the cndb 360 view in these in the cmdb workspace navigate to workspaces cmdb workspaces and the cmdb workspace menu bar select cmdb 360. now let's take a look at the various components within the cmdb 360 View the potential issues includes two cards CI not reported by Discovery sources and data mismatch cards on the potential issues Tile Show details about CIS with Discovery sources that are incorrectly reporting on the CIS CI is not reported by Discovery sources lists Ci's that are discovered by multiple Discovery sources but one or more of the discovery sources has stopped reporting within a specified number of days the number of days since Ci's were last discovered by a discovery Source dashboard setting is used in the cards aggregation we will look at the various settings that you can configure for the cndb 360 after we review the various components next we have data mismatch this list is Ci's for which different Discovery sources are reporting different values attributes are considered mismatched when different Discovery sources report different values for the attributes Ci's that appear when you drill down on this card can reveal issues with the individual Ci or your reconciliation rules next let's look at the tiles under the discovery sources cards in the discovery sources Tile Show aggregated counts for your Discovery sources the number of Discovery sources shows the total number of Discovery sources that report cmdb 360 data the total number or total cmdb 360 records shows the total number of raw cmdb 360 records and the cmdb 360 data store that contains records for each Discovery Source report per each CI attribute the reconciled CI card shows the total number of unique Ci's created in the cmdb after processing incoming data from all discovery sources including after reconciling data for multiple Discovery sources for the same CIS in my instance I have three Discovery sources and the total number of cmdb 360 records are 541 of which 540 of them have been reconciled the discovery Source overview card displays the distribution of cmdb 360 CIS across all reporting Discovery sources the coverage portion of the dashboard includes two tiles the CI with a single Source tile shows Ci's that are only reported by a single Discovery source with a breakdown by the discovery Source reporting those Ci's the CI by number of Discovery sources shows CIS reported by multiple Discovery sources grouped by the number of Discovery sources that are reporting those CIS now let's look at how we can configure the cndb 360 dashboard to get to the configuration settings click on the settings gear icon on the top right of The cmdb View under the global settings you can use the setting to limit the number of records that cmdb 360 must process out of the box the default setting is a hundred thousand records under the potential issues setting CI not reported by Discovery sources the number of days since CIS were last discovered by a discovery Source setting determines the number of days used in the calculation of the CI not reported by Discovery sources card by default it's set to 7 days scrolling down under the data mismatch settings these settings determine which classes to use for the card and the relative weight of each of those classes in the calculations the automatic data weights evenly distributes weights between the selected CI classes manual data weights allows you to specify a custom weight for each CI classes let's add a new CI class for the data mismatch card here I'm going to add the manual endpoint class click add and now here I'm presented with two options I could show the CIS where every attribute doesn't match and I can show the CIS where any attributes does not match and this allows me to select the attributes let's select IP addresses added and also add another attribute location and we'll add that as well so this is going to show the CIS where the IP address and location attributes don't match I also have the hardware class configured where the class fully qualified domain name manufacturer model ID name and serial number attributes so this will show me the CIS where these attributes don't match between multiple Discovery sources and then the other one that I have here is the application class this will show me the CIS where the IP address most recent discovery name and version attributes don't match between multiple Discovery sources next let's look at the coverage settings classes you want to include in the coverage card can be defined here so again the same concept applies where you set the automatic data weight or manual data weights let's add another class click add next let's change the waiting to manual data weights so here I can assign for the cloud Network to be 30 percent and then the manual endpoint to be 70 percent and then once I'm done my configurations I can click save and here at the top it tells me that my settings have been successfully saved in the last portion of this demo we will look at saved queries navigate back to the cmdb 360 View under these saved queries card you can edit and run queries you've created in the past or you could create a new query by clicking create query here you're presented with three types of queries that you can create the first one get records allows you to create a query that you can use to explore your cmdb 360 data the second one find Gap this creates a query that you can use to analyze gaps in your reported cmdb 360 data and the third type compare attribute values allows you to create a query that you can use to identify CIS with attributes values that differ across multiple Discovery sources or against cmdb in this demo we're going to create a find Gap query there are three steps to configuring the query selecting a class Gap setup and results layout for this demo we're going to use the same class that we used in the past when you click the down arrow you can further filter vcis are in the manual and point class by setting up the condition here for my example I'm going to leave it empty click continue to go to the second step in the second step under the non-reporting discovery sources I'm going to select agent client collector so what this is going to do is it's going to show me everything in the cmdb that is in the manual endpoint class table that is not reported by agent client collector Discovery source you can also select reporting Discovery sources however this is optional for this example I'm going to leave it empty click next to go to the last step so here we have two options we can show the unique cmdb 360 records or by default you could show the CI records by Discovery source I'm going to leave it as default and the limit results I'm going to leave it as all next click save and here you can give the report a name you can also add a description now I'm going to click save and run so here we could see the results of our query it's showing me all the CIS under the endpoint manual class where the source is not agent client collector this concludes the demo of the cmdb 360 in the Utah release thank you for watching and don't forget to like And subscribe [Music] foreign [Music]