[Music] hello my name is gerard berte i'm an outbound product manager in the itunes business unit at servicenow this presentation may contain forward-looking statements this is the first part of a series of three videos on getting started with servicenow item health without any prior discovery or cmdb many servicenow customers have told us that they will deploy item health only after they complete a full discovery and a full service mapping to first create a healthy cmdb while we do not object to that approach this series of videos is actually to show you that you can deploy item health and benefit from its ai ops capabilities right away without any initial discovery any service mapping or cmdb and how you can gradually add elements in your cmdb either manually or automatically to further benefit from additional ai ops features so let's jump into the first scenario we will create a service from the service portal and we we will visualize that service in operator workspace we will then generate alerts against that service a lot of different severities and we will see those alerts in operator workspace and how ai ops was able to automatically group those alerts uh right away the business outcomes obviously is to show you that you can deploy item health right away in in production without any prior discovery or cmdb and the end result is that your operators will see a reduced alert noise because of the arrow grouping this will consequently reduce their workload and allow them to focus only on the primary alerts now let's jump into the demo this is where i want to create a service using a service catalog in the service portal i select the req register application service which i created which only asked me for the name of a service i would for that purpose of this demo i will call it production and i will submit it in operator workspace i still have zero services but as the service is created is going to show up in my operator workspace and i can look at the service details everything looks good no related alerts for the time being so let's create some alerts first i'm going to create an event from nagios as it came from a monitoring tool i'm going to set it with a minor severity let me clear the time of event the description will be a minor event from naius and in the additional information is where i will specify the name of the service so this is a very simple json document where i a service and the name of the service that's it all right so here i'm simulating with this form generating an event into item health i save it and that event goes into item event management is processed analyzed and then an alert is generated out of it if i really reload the form i can see that there is alert 167 and that the event was associated with the service production based on an event rule that was also defined for this purpose so if i go back into workspace i see that now my if my service has one minor alert if i click on it and refresh the page here there is one related alert number 167 and if i select this alert i see that it is associated with the event which has just generated now let me send another event now let's say from zabic's and i'm going to say it's a major alert let me clear the time of event let me say that it is ready to be processed i'm clearing the alert value saying it's a major event from savix i'm still leaving the service reference and i'm using insert and stay so that that event now is being sent to item event management being processed and it will be converted into an alert when i reload the form i should see it alert 168 and that event is associated with a service production going back into operator workspace i can see that now my service has turned to orange which is major if i click on it i can see that i have two primary alerts one major and one minor going back into the service details i have i can see the two related alerts here all right the 168 and 167. now if let's wait a little bit and see what happens okay so back into operator workspace i still have one my service with a major alert but now all of a sudden i only have one primary alert of major severity what happened well let's look at it remember i had two related alerts now if i refresh the page i find that i have one related alert and it's 169. the group is automated meaning that the correlation took place and ai ops actually grouped the two alerts that are generated into a a new alert so if i click on this alert 169 i can see that it has two secondary alerts which are the alerts that are generated from nagios and zabbix so this is a very important feature which shows that as you send events the uh ai and ml capabilities and the ai ops capabilities of item health are kicking in as needed in this particular case it grouped two alerts in under one primary alert thus reducing the the event noise and the number of alerts that the operator has to deal with thank you for your time this concludes part one of a series of three videos on getting started with servicenow item health without any prior discovery or cmdb