hello everyone my name is steve emerson and i'm the outbound product manager for itom visibility here at servicenow and today i'm going to demonstrate how you can manage multi-cloud resource visibility using a single pane of glass just like your on-premise resources having automated visibility of cloud resources is key to driving technology service operations excellence servicenow item visibility discovers resources across all major cloud providers and adds them to the cmdb which is the data foundation for your organization and for servicenow cloud discovery discovers your cloud resource configurations including tags and it automatically creates dependency relationships you can configure near real-time updates to occur so that your cmdb is always up to date with the latest cloud resource changes and once your cloud resources are in the cmdb you will be able to leverage technology workflow solutions to keep them secure and healthy to control costs to reduce risk and to ensure change governance but to effectively manage multi-cloud resource visibility you need a centralized platform with an easy to use experience servicenow's cloud operations workspace provides a single pane of glass for visualizing the entire cloud resource estate now let's see a demo of cloud operations workspace this is the cloud operations workspace homepage the cloud operations workspace is built on servicenow's next experience that debuted in the san diego release the next experience provides a modernized look and feel including the ability to use dark mode like you see here now we all love dark mode in our personal lives so it only makes sense for it to be available for us to use a work let's take a look at what we see here up here on the left we see a trend of configuration items over time this enables you to see how many cloud resources you are discovering and see if it's going up if it's going down and you can click on any of these data points to see the detailed resources here we see the events by provider for the last 24 hours servicenow has the ability to ingest cloud events so that you can get real-time updates of your cloud outside of your regular discovery schedules and those can be reflected in the cmdb and of course we also see our discovery errors today so that administrator could take a look here and see what's going on to try and fix them you also have some applications available to help you manage your cloud which i'll get into shortly let's first take a look at settings here cloud provider selection this enables us to choose which cloud providers we can integrate with from our servicenow instance so for example what you see here is all of the cloud providers are able to be integrated with but let's say you only subscribe to aws and azure in your organization maybe google as well you could unselect the rest of these click save and now effectively what that does is it prevents cloud credentials cloud discovery schedules as well as cloud service accounts for being created for those other clouds in the future if you do subscribe to any other providers you can re-enable them and they'll be accessible for people to start using again now let's see the two applications that we have that are going to help you better manage your cloud first we'll start with cloud discovery which is your one stop shop for managing all of your cloud discovery schedules when you first come in here you'll see an overview your cloud discovery home page which shows lots of different things you can see here your most all of your cloud discovery runs in the last 30 days how many have completed how many are still active how many are cancelled your upcoming schedules these are schedules that will be ran in the future here you can see that configuration item trend chart so that you could see if you're trending upwards or downwards in your cloud resource discovery over here um you could see your cloud discovery errors uh it's also a trend you could also click into any of these to see the specific errors down here we can manage our credentials so we have 15 credentials being used across aws azure and gcp at the moment you could go into these credentials if you need to update them you can do that if you need to set up new ones you can do that as well here you can see your mid servers and here you can configure your mid servers to be used for cloud discovery and service accounts so you could here you you can see how many service accounts you have across the clouds that you have set up for discovery and then down here you could see cloud vms by data center so if we were to go ahead and create a new discovery schedule it'll simply ask you for a few things and i'll show you what those things are by looking at an existing cloud discovery schedule for aws first thing we see here before we get into creating a new one or seeing the details of it is we see a summary specific to this schedule so we see the total number of cloud resources that have been discovered by this schedule we see anything that is newly discovered since the last run anything that was absent since the last run any cloud discovery errors as well as how long the last run took to to occur and then down here we see charts of resource counts from from the recent runs once again anything in servicenow you can click into you can see the specifics behind it as well as average time it took to complete these discovery runs so let's go ahead and look at the details of this discovery schedule by clicking edit and we can see that it just asks for some basic information we have to give it a name we have to choose which cloud provider it is and we have to choose which mid server is going to run the schedule next we will pick a service account we could use an existing service account or we could you know choose to create a new one here we have the ability to test the account as well here i mentioned earlier about credentials each service account requires a credential record in servicenow that has rights to the clouds to be able to do that discovery if we click next we'll see we can choose which data centers we are discovering so for example this one here is only doing these two or you could choose to do all the data centers and then the last thing here is or second to last thing is do we want to discover the virtual machines and do more of a deep dive os discovery if you turn that on assuming you had credentials on the servicenow instance that had access to those os's you could gather the os level details from all the virtual machines behind there and it would automatically run right after this cloud discovery schedule finishes and then finally what schedule do we want to set right so here i have daily at noon and then we can choose some other parameters here if we cancel it if it's running longer than one day or one hour we can finish and run it or we can just go back to the cloud discovery schedules page go back to the cloud operations workspace homepage we just saw how to set up and manage discovery of our cloud resources but where do we see the resources that we just discovered this is done through the cloud resources inventory dashboard which is a new feature of our may 22 release of the cloud operations workspace here we have an overall view across all clouds of the number of resources by configuration item classes by region by cloud service account as well as a view of the incoming events across all cloud providers that will help us keep our seamdb up to date in a near real-time fashion we also see our cloud discovery errors as well as our stale cis now stale cis are those that have not been discovered in the past 30 days these ci's have typically been taken offline and can be removed from billing from monitoring etc right now organizations typically have a process in place for managing the life cycle of cis and these would normally be cleaned up through that process we can filter this dashboard by cloud provider by region by service account and by ci class so for example we can choose just to look at the us east one region and what this does is it filters the dashboard and shows all resources that are part of that region and maybe our goal right now is just to see our virtual machine instances so if we click on the ci classes and we start typing in virtual we can click on virtual machine instances now here we see the dashboard now shows data that just pertains to the filter that we just selected so let's click into the bar chart to see our virtual machine instance resources now this this list of resources here or all 456 are all those that meet the criteria that we had to filter on if we go into this specific resource this is a vm instance that i own and we can see that all of the configuration details about this server these next few tabs showcase why multi-cloud visibility is critical in managing technology service operations now the power of using servicenow for your technology service operations platform is that it's underpinned by one architecture and one data model one architecture means that all platform applications can seamlessly work together and are enhanced by a set of core capabilities such as workflow integrations aiml you know just to name a few things and one data model means that all applications leverage a single system of record or that same db that is built following a common data model so you have visibility into the life cycle of all service operations functions that occur against your resources and for example we see there is a change request open against this vm instance to upgrade it to a larger size because of a performance issue and here we see the incident for a slow performance that spawned the change request right or the need for the change request and then here we see a list of all the tasks that are currently open against this resource this could be any platform task right so i change an incident or part of it service management but certainly you could have security incidents here alerts vulnerabilities any any type of resource that the platform can relate to the ci now we see that this vm has eight tags associated with it and we see that there is a key called app and a value of train operations as well as a key called env and the value of production right application and environment tags are extremely useful in creating tag-based service maps to quickly gain business context of cloud resources and we can also use the tag governance application to set organizational tagging policies and audit tags against these policies and then remediate the tags in the cmdb and you could also do that in the cloud with our itom governance solution but this will ensure that we can easily create tag-based service maps and understand the impact on our cloud resources to our business and i've included links below to how-to videos for both tag-based service mapping and for tag governance so that you can learn more about these features now if we open up the dependency view we can see the relationships for this resource right here we see the virtual machine instance and here we see all of the cloud metadata we see that this was a t2 medium we see the storage volume we see the cloud management network the storage mapping and the data center right us east one we can see all the information about the data center as well and here we see there is a tag-based application called train operations right so if we look at our details a little bit further we can see all of the associated ci's in the map we see our current changes that are you know that are happening we see the incident that we opened up and we see related services so i said earlier that application and environment are really extremely valuable in creating tag-based service maps so if we look at the service map that was created automatically with tag based service mapping we see that now you know our application is called train operations and we see that we have our this is the ci this um this windows server and we also have a cloud database so now that we've seen all the details about this specific cloud resource i'll go back to our cloud operations workspace so we just saw how cloud operations workspace provides a single pane of glass for visibility of your multi-cloud resources state we saw how you can choose which cloud providers are available for integration with servicenow we saw how you can create and manage your cloud discovery schedules and we saw how you can visualize all of your discovered cloud resources so by using cloud operations workspace you'll be able to gain automated visibility to multi-cloud resources very easily and drive technology service operations excellence if you have any further questions about cloud operations workspace please leave a comment below or reach out to your servicenow account team thanks for watching and have a great rest of your day