[Music] foreign [Music] it's Justin thank you for watching and welcome to Justin's house I've got a fun one for you and it's about one of my favorite servicenow features the cmdb or the configuration management database okay so if you're any bit familiar with cmdb you know it's something you have to actively manage you need to take care of it you need to care for it groom it put rules in place and stuff like that with San Diego and prior we had the cmdb data foundations dashboard and you can see here this was the first or maybe not the first iteration of it but I've got two tabs for data foundations I've got some indicators up top around Hardware CIS app with with serial numbers active CI and stuff like that I've got a few indicators down here below and then if I flip over to cmdb insights I got kind of a a few more indicators that I can look at and see what's going on so with Tokyo this got a big upgrade I'm going to go ahead and pull it up now you can see the new cmdb data foundations dashboard so we've got kind of what we were looking at before at the top the best practices with the remediation Playbook URLs so you can go fix these things or have some guidance on how to fix them right so Hardware CIS with serial numbers services with owners create asset business rule enabled and custom scene maybe attributes at the right level and we've got a priority for when we how we should be addressing those and then a result uh zero percent all the way to 100 for those particular best practices if we scroll down we've got a visual on those Hardware CIS missing their serial numbers we've got another visual on the services missing owners and Hardware CI is missing serial numbers by Key by key class um say that 10 times but what's new um in addition to what you just saw there that's kind of like some regurgitation of the same stuff that was there but now I've got four tabs not just two tabs gone with the cmdb insights Tab and now we have three new tabs around customizations data management practices and itsm processes so let's take a look at customizations there let that pull up I've got another batch of indicators around customizations and best practices there at the top so base system CMD relation type usage custom cmdb tables using standard naming etc etc use of custom attributes here it all looks a hundred percent so in my demo environment I've got zero on all of my indicators which basically means Justin hasn't come in here and customize his cmdb which is not going to be the case for most people using service now data management practices another new tab look at all these indicators I got nine on this one again nine remediation Playbook URLs and this is around keeping things clean and kept up so activeci is not updated in the last 90 days or they were updated in the last 90 days Ci's that are coming in not through the identity and Reconciliation engine so important that there'd be Automation in some kind of deduplication and source of ownership or attribute ownership right using that ire unique location servers with a location so look at that only 45 percent of the servers here have a location that might be something we want to address installed server CI naming reflecting hostname duplicate CIS etc etc you could see them I don't need to read them all to you and then I got visualizations down below not processed via the ire very important we want to process the eye through the ire unhandled duplicate CI so I've got 13 duplicates out there that no one's done anything with I got no CIS that are missing names I have active CIS not updated in the last 90 days okay 3000 not updated why are we not updating them manage CI is missing their models uh installed server Ci's names not reflecting the host name so we got a mismatch there between the name and servicenow and the hostname duplicate locations orphan CIS servers missing locations last tab here to show you itsm processes why are we doing the cmdb if we're not associating them with changes and incidents so here I've got some indicators saying only 3.55 percent of changes in Justin's demo showcase have changes referencing a configuration item bad bad bad bad bad incidents 9.56 bad bad bad bad bad bad but it's my demo environment right this isn't production um changes relating to both a service and a CI so two associations there what service are we changing and then what part of that service is changing so that's what's incident and change relating to both services and the CI Meme and then I've got again visual indicators or I'm not referencing a CI change is not referencing and then the same with the Service Plus the CI there down below now what I didn't show you let's go back to data management practices is that all of these are using performance analytics so these are configurable um uh indicators where I can come in and I can do breakdowns and see different things so if I look at CI is not processed by the ire I can come in here and look at breakdowns and of course Justin clicks on the one that has no breakdowns let's try that one more time before we give up um I'm gonna actually go to itsn processes because I bet you there's some breakdowns in here here's my incident it's not referencing a CI and I bet you hope that I can look at priority group and stuff nope I've got no breakdowns on that one either so two clicks and a fail there but there are supposed to be additional drill Downs on these particular indicators I'm taking one more try there okay good I got one where I can break down this Hardware CI is missing the serial numbers by class so you see their computer Windows Server AIX server et cetera Etc and I've got a visual for that so that is the new cmdb data foundation's dashboard in Tokyo now available it's a store app you can download it update it I hope you found this video helpful if you did please like Please Subscribe or share it with somebody who you think is interested in taking care of their cmdb in servicenow and until next time don't forget to always be learning foreign [Music]