hello this is will hallam from servicenow and today we're going to talk about lightstep and servicenow event management so lightstep recently acquired servicenow company provides detailed insights into microservice based cloud native applications we also provide the native ability to ingest events sent from lightstep with the servicenow event management module and the reason that this is valuable and important is because servicenow event management can pull together events from disparate sources so the insights provided by lightstep are augmented by data from more traditional monitoring and or application performance management systems servicenow automatically coalesces these together in a single view and what this does is it accelerates root cause identification and reduces mean time to repair now let's get into the demonstration first a brief tour of my test setup what you're looking at right now is my example light step project in which i've defined an alert which will send an event indicating a critical condition into service now when the error rate is above two percent over here is a script which uses open telemetry calls to send open telemetry data into light step and i've given it two [Music] routes one which will perform a successful operation and then one which will perform a failed operation allowing me to then simulate successful and errored transactions within my example application then on the servicenow side what i've done is defined a tag based application service which consists of some azure functions and kubernetes pods and if we look at that service there's a service map which shows the components which make up the service and you can see that the service itself is in a a green state and all the components in the service map show operational so to simulate a an error condition i've created a which will send a combination of successful and erroneous transactions into my test application it's a for loop that hits the successful and the erroneous urls multiple times every second and then i've defined example events which will simulate error conditions within the azure function and the kubernetes pod so in a real life scenario these would be coming from one or more traditional monitoring platforms which are keeping track of what's going on within kubernetes clusters and an azure cloud account so the way i kick off my test scenario is first i start up my example web service and then i start generating transactions and see it's very verbose when it hits that error condition and this is the output from the example application again showing error a stack dump whenever it's hitting error and it's collecting both the erroneous and the successful transactions generating open telemetry data and sending it into light step now i'll simulate alerts coming in from the separate monitoring systems by toggling these simulation events into a ready state and then if we look at the event management event list we can see that the azure event and the kubernetes event i've already generated alerts and based on the content of the event map them to the corresponding configuration items then within this alert you can also see it's already correlating it to my tag based service and now if i go to the operator workspace i can see that my service has now turned red looking at the service map i can see it's highlighted the azure function which has indicated an error the kubernetes pod which has indicated an error and then it's rolling those up to the service the way the light step event management integration works is it ties it to a service and so the light step event if only the light step event came in it would just flag the service as having a a critical or warning or whatever the severity was the additional event sources and the ability of servicenow to automatically correlate those is what produces the kind of subordinate highlighting of the specific components which are also in a non-okay state so if i refresh the page i can now see that the related alerts have been correlated and all tied back to the service this can provide a real head start on mean time to repair because it's collecting all of the issues from disparate sources and putting them in one view you can also see that from the service map by selecting show related items over on the right here and then you can drill into each one by clicking this icon this concludes the demonstration i will include a link to a companion community article about this subject which also includes the little snippets of code that i use to simulate the web service and and generate a load on it in that in that article thank you for your time have a great day