all right so I guess we can get started so good morning good afternoon good afternoon or good evening everyone thanks for joining this session uh today we're gonna see uh a new episode of the item visibility and governance webinars series also part of the live on service now webinar Series in particular today we're gonna see how to discover kubernetes environments with the new service graph connector for open Telemetry my name is John Mario de Luigi and I'm part of the outbound product management team covering item visibility and governance and together with me today we're gonna have Dennis goyadin so Dennis please you can introduce yourself I don't think I think you're muted I'm muted sorry about that thanks bro hello everyone my name is Dennis guyadine I'm a senior staff outbound product manager in the cloud observability business unit and I'm focused primarily on the integration between Cloud native and um servicenow fantastic thanks Dennis so as I was saying this webinar is also part of live on servicenow webinar series which is an interactive series of events where you will have the possibility to talk to subject matter experts to speed deployment adoption and Achieve value faster with servicenow Solutions you can either scan the QR code here or just access the link that has just been posted via chart and you can enroll to this series and select the events of your interest now um before we keep going please make sure that everyone is muted and today we're going to use the Q a feature to ask questions throughout the sessions and please make sure that whenever you're asking questions you introduce yourself we're really looking forward to see who you are and also please participate in the polls we're going to have a few polls today and your insights will definitely be appreciated and this session will be recorded and will be available on the same page of the registration for this webinar so on the Community page and after this session it will be printed out to fill out a short survey so we would really appreciate your feedback I already introduced myself and Dennis as well so we can skip this light and we can get started with the first poll so um as the first poll that you're gonna see uh soon we want to ask you how you're currently discovering your kubernetes environments and you can select all the answers all the options that apply to your case so um thank you very much I see already a lot of views are participating very interesting insights that are coming up so please make sure your answer I see many views have inputted some answers so I'll give another 10 seconds and then we can see the results so I'll close the pulling five four three two one and we can see the results so we can see that the vast majority of views are still not discovering kubernetes followed by the 42 percent of views that are discovering um kubernetes environments leveraging servicenow Discovery patterns then um the rest are using either a third party Solutions manually importing records or using CNO but um they are the minority in this case so thanks very much for participating this is only one out of three so please keep engaged and keep me engaged with us now before we start with today's proper topic we wanted to first of all cover what's a service graph connector so whenever we think about options to populate your cmdb you may want to use a third-party data sources not necessarily um with the typical traditional ways of Performing Discovery and this is when service graph connectors are useful they are useful for many different cases because they reduce the staleness risk allowing you to always have accurate data and improving data quality by having multiple data sources so as we said as we just said having multiple data sources is very important for many organizations and they in general simplify the process for adding Resources with the certified and supported Integrations as a matter of fact as of the the plan for Q4 2023 we can see all sorts of connectors that are offered or planned or that are already The Early Access better version so we can identify many different categories here such as the cloud and the software or server Network or monitoring observability use cases or endpoint and ID Asset Management security or even manufacturing iot and Telecommunications so we really have a vast a very wide range of service drug connectors that are again very useful for three main reasons because they are tested and supported by servicenow and they are either built by servicenow or in ISD partner and they support multi-source and Reconciliation so you can leverage all the functions or the cmdb and how we configured in the best possible way so again um there is one single source of Truth for many companies and that needs to be the cmdb but uh we can populate the cmdb with HMS or AGM based Discovery the more traditional way that I just mentioned before when leveraging the mid server typically or uh with your currently existing tools so you have already pre-approved ways to connect to your existing tools and automatically populate your cndb to keep consistency in having one single data model in one platform leveraging one single architecture this was a quick introduction to have a a bit of a better context um to the service graph connectors which are effectively third-party data Integrations with your cmdb and now we're gonna see uh better what's the topic for today's session so the new service graph connector for open Telemetry so Dennis over to you all right thank you Gene you want me to share my screen let me go and please make sure uh to everyone to Leverage The Q a section so we'll make sure it runs through all of your questions thank you yep so before I start I wanted to highlight uh challenges with discovering kubernetes or just challenges with kubernetes in general uh the biggest one that's out there is security because of the just the nature of security it's of kubernetes because it's something that's not still fairly new um it's a has a lot of layers of abstraction so there's a lot of you know attack vectors that you have to be aware of and that's some of the challenges that's so relate to security from a complexity standpoint um it requires a lot of domain expertise I would say is because it is again there's a lot of moving Parts related to it there's a lot of teams that's involved and the environment that it does typically associated with is in a cloud or on-prem and those containers are very ephemeral so there's a lot of you know pieces to be worried about from a scalability standpoint it does go at a very large scale um but um you know as you scale it out you run into a lot of other challenges as well from a deployment standpoint monitoring load balancing resource allocation because if you're running thousands of containers in an environment you're going to worry that you're not starving some resources that are out there which leads to the next one resource requirements it becomes very expensive um to manage it because you have to manage all those various you know components and resources and the last piece is there's a there's a huge skill Gap in in kubernetes adoption so if your organization is moving towards adopting Cloud native Technologies you know the organization itself needs to also you know keep up and Pace you know with it and then this leads to you know how do you actually you know support these teams because at the end of the day the teams that are operating this is SRB and devops teams and they have this deep domain expertise in this space and typically uh when you're supporting this this kind of I would say a new world you want typically you want to use tools that are that are pretty much kubernetes Native you know that support this space because if you speak to them and you're talking about some kind of you know Legacy tooling that you want to bring to bear and start implementing it here um you know they're gonna probably ignore you you know they typically would ignore you because it's related to a security issue um because they don't want to give you you know super user access or things like a bearer token because those kind of things are constantly rotated and if you are had to have access to it you can you know exploit you know those clusters of somebody you know malicious has access to it the thing that I see a lot in this space is that folks are hacking kubernetes and doing Bitcoin mining although Bitcoin itself is kind of um you know having its own challenges right now which leads to the various kubernetes Discovery approaches so on the two on the left are the agent list approaches which is just using patterns we started off with the pattern-based discovery which requires again a bearer token in your Cloud credentials uh the automated kubernetes Discovery scheduling that's basically I would say patents for managed kubernetes so every cloud provider has their own kubernetes distribution and with those kubernetes distributions they make it easy because they don't make you they alleviate the need for you to manage a control plane you just focus on your coding containers and your workloads the CNO methodology is basically similar to ours it is requires you to run uh you know a set of containers in your environment from a cenal perspective it's really just the the mid-server and ACC that are containerized and running your environment and the SGC for hotels running the open Telemetry uh collector um there's several you know methods where they were useful at I would say the uh if you're all you're using is eks AKs and gke I would say the the automated kubernetes Discovery scheduling is great for you to use the only thing is from a security perspective you need to require you know Cloud credentials right the two on the right require you just to run these agents within the cluster itself um which alleviates the need for you to provide credentials to the servicenow admin and you can start you know deploying right away the thing that's unique with the service graph connector for open Telemetry is that it's I would say more kubernetes native but it is using something called open telemetry so I'll get into what open Telemetry is so before I go to poll two before whether the open Telemetry just go to poll two on you know what challenges are you facing today you know as you're discovering kubernetes you know some organizations uh you know are constrained because this environment constantly you know churns spins up spins down and they want to understand what the you know use cases are uh to bring the data in I would say for the most part as we're speaking to customers they still want to have that you know visibility and to understand exactly you know every resource that's getting spun up they want to do inventory auditing reporting and things like that how much longer for this poll I would say another five seconds and we'll end it yeah and let's stop right there and let's share the results all right so um the bulk of it is exactly what touched on before is the security constraints um there are a lot of a lot of sres and devops don't they're not going to give up the Keys of the Kingdom right the next piece is you're not using K8 okay so that's a third of you the next one is again no value describing ephemeral workloads and the last one is is cost because it could get very uh expensive over time thanks for that so go to the next slide let me just close this uh all right so let's go into open Telemetry and talk about what it is so if we talked about kubernetes kubernetes if you don't know is a cloud native Computing Foundation open source project the cloud native Computing Foundation runs under the auspices of the Linux foundation so any project there is not owned by any specific vendor it's it's open like like linux's itself and open Telemetry is the second most popular project right after kubernetes under the cncf Linux again is the most popular one um it's a vendor neutral you know and you know set of tools and Frameworks uh sdks apis and things like that and its focus is to really you know encapsulate that Telemetry data all those signals and really you know ship it to any back end so its goal is really to collect it um generate this this uh Telemetry data that is collecting and basically shipping it over to any back end so it's collecting uh traces metrics as well as logs um and right now every vendor that supports that does anything related to application performance monitoring or observability all of the cloud vendors everybody's adopting now this uh open Telemetry uh framework because the value that it has now is that in the past every vendor kind of dictates how you do your instrumentation and it leads to lock-in and also um if you're investing in agent technology a lot of you already goes into that that agent you know software itself and you can only go as fast you know as that one vendor so you're kind of Trapped and locked in in the world of cloud native every team um is typically adopting you know Cloud native you know in pockets they pick their own tools their own languages their own Frameworks and they have to have to start instrumenting their code base um right if they want to move to another team or they just want to ship their code and have another team you know take over now they have to relearn everything from scratch so this gives you that the high quality and then portable Telemetry to provide more effective observability and because every vendor is supporting it it's it's um as you can see uh it's picking up a lot of pace a lot of traction field foreign connector for open Telemetry so what this is again we're using that that open Telemetry framework to capture all this Telemetry data and then shipping it over to the cloud observability backend the cloud observability backend is taking all those you know Telemetry data it's taking the something called semantic conventions which is really just you know tags labels from a Telemetry standpoint and converting it all to CI data So based on what the you know the attributes are if it's a Daemon set or a deployment set and again these are all kubernetes nomenclature and terminology it's going to assess all of that and ship it over to the appropriate tables it's also going to take this span data and instrument or assemble these traces and then those traces are going to create these maps for you and then it's basically it's going to be imported into servicenow so what that means is that you do not need to create these service Maps the system this Cloud observability solution itself is creating those maps for you and all you're doing is importing it so once you set this up it's really just turning it on and specify how frequently you want everything to be updated so we're going to be discovering these Cloud native apps and workloads so these are going to be the kubernetes objects the kubernetes workloads we're going to tie it into your itsm workflows as well so now you can understand what your blast radius is whenever you make a change on anything you can understand what the upstream and downstream impact is and it's going to integrate with your existing applications so many organizations are not you know building these Cloud native apps in a vacuum these are going to be integrated with some you know existing you know application or infrastructure that you have been running the environment for a very long time but now with these Cloud native Technologies you're making it available to your your end users over the web um you know if your system or record is running on the database and on the weekend or some in a quarter you're making a change to it you wouldn't really know if it's affecting those customer facing applications so by with this integration you're able to assess what that impact is all the way upstream and downstream right and again this slide kind of highlights it uh I would say everything in left where it has those those logos on top that's all your your Cloud environments where you're typically going to be running your kubernetes clusters uh you can also be running red hat openshift which is also kubernetes um again we're bringing using a Telemetry data shipping it over to us and we're assembling those maps and bringing it over to CIS if you're using event management we could also ingest those alerts as well uh the piece there too and a relationship to traditional State that's the and I'll go into more details is those inferred services that we're also associating with these Cloud native apps right so again what's different than what we currently have is that we're not using a mid server or ACC we're just using this Telemetry data that if you're using kubernetes you're probably using open Telemetry in some shape or fashion either it's the Upstream open Telemetry with your vendor or the open Telemetry software is bundled in your your vendors um you know client software and their agent right so we're using the same Telemetry data and basically importing um those service Maps as well as those CI data as well so from an architectural standpoint um what you will need to do is run a collector in your cluster there's also an operator which is optional that's a kubernetes operator for open Telemetry it just does a little more heavy lifting there again it's optional if you're not using a collector today and all the collector does is if your instrumentals applications uh The Collector is the one that collects all of that Telemetry data and then the collector is the one that's going to be sending it over to the cloud observability back in and the cloud observability back end is the one that's you know assessing all that Telemetry data uh taking again there's a semantic conventions that it receives from the Telemetry data and associated with the CI records right if it's a uh a deployment if it's a replica set the nodes the pods and things like that uh and then as well as those topology Maps the way the solution is bundled again all you need is the Discovery license and you have access to the SGC for open Telemetry so there is no special licensing required for this all you need is the Discovery SKU all right this slide is actually supposed to be moved forward I'll happen here but uh going back to open Telemetry Gardner is also uh took notice of this technology as well and they identified some areas where it actually helps an organization from an innovation standpoint because um as I mentioned before previously um every vendor kind of dictates how you actually instrument uh your software uh from a cloud native perspective with open Telemetry it kind of unlocks this and democratize it for any organization to leverage it uh to provide improved observability again it's a very fast moving project uh it simplifies monitoring um we can begin because the a lot of the complexity is removed you don't need to read through manuals and things like that to use it it's hot it's documented and because of the project velocity they're they're looking at ways to actually improve it to make it even easier for customers to use better collaboration amongst teams I mentioned it before um again it's each team is not going to be in a vacuum of how to implement or use these tools they have the portability across teams and cost savings I would say at a high level you're not paying for agents if anybody can deploy open Telemetry you don't got to pay anybody anything right they're looking at this is something that's going to uh you know expand within two to five years and there's also something called observability driven development where you're incorporating observability into the development environment so instrumenting during the you know using something called similar to test driven development where you're bringing observability you know at the Forefront at the beginning going back to the architecture piece again all you need is open Telemetry in your cluster open Telemetry collected metrics logs and traces sending it to the cloud observability backend we're not going to go into the Cloud observability solution itself but it's a system to handle and process Telemetry data at scale and provides workflows you know there for you to quickly understand where the source or the needle in the haystack is and then we have workflows to help you you know quickly identify or you know triage or those those issues as well we can quickly associate that to a to a deployment to a new version change and things like that um to get to you know root cause but we're leveraging that solution for your um you know to integrate with the cmdb and the service graph connector is using an API that was purpose Built For This use case and that API is again all of this is enabling us to you know I would say uh extract the data and then convert it to data that's usable from a single DB perspective if you're using event management we also have a hook into event management as well where we can just ingest the alerts from cloud observability and provide additional workflows hold for one second losing my voice go to the next slide all right so I'll go to a demo now if we have questions hopefully it's already got people to answer it on your screen right all right so to get access to this service graph connector all you need to do is go to the servicenow store and at the bottom let me make this a little larger it'll tell you what the requirements are all you need is a discovery license integration comments with seem to be the class models this piece is optional and it's only required if you own event management and all this is going to be able to do is you know automatically help you with that webhook and for this demo environment I'm using the open Telemetry demo there's something to compare and contrast to this is how this open Telemetry demo if you deploy it in open in a kubernetes cluster how it will look like a service map doesn't typically go into this detail but it's telling you what protocol is actually in use here and how these pieces are communicating one another that's what this map looks like but let's go back to the guided setup and all you need to do here is you need to set up the organization what is the name of the organization that you configured again in the Cloud observability solution oops I've used unified demo I have an API key and then I have to test to test the connection and this PCO is really if you have the Cloud reservability solution setup you're going to add a bunch of projects typically by default you only have two well we will say prod one is Dev for here we're only using the SGC for open Telemetry demo we have to set it as false to say that it does not it's not excluded meaning it's going to be included that's what the setup is then after that you just execute and run it there's a few more steps here the real major piece here is when you want to actually configure to run and I go here and again this is nothing new with any service graph connector this is the same flow you specify the frequency here and then you click execute now now once you do that let's go back here we're going to go to our out of the box kubernetes dashboard and everything is populated here so this is out of the box this is not showing every single um CI class type this is showing the major ones you would typically look at and what I can do is I can go to my cluster I'll select the SGC for open Telemetry cluster and this is all the information that was brought over here via the that open Telemetry Telemetry data so we have your nodes we have calculated application Services which I'll get back to in a few namespace deployments replica sets these are some endpoints this is nothing specific to um kubernetes but this is how these pieces are you know attaching to one another and point from and there's some more stuff here if I go back to calculated application service any service map that gets imported from a third-party system falls under calculated application service meaning that it's not something that was created natively within servicenow right we're just importing maps from a third party it's called calculate application service but just think of it as a dynamic application service that's dynamically assembled from a third party we go into our dashboard View and again this is anybody that's a scene to be owner you have to worry about completeness compliance correctness Jean already mentioned that this is a service craft connector uh when we build service craft connectors it has to adhere to the identification reconciliation engine to of you know to make sure that there's no duplicates and stale information or incomplete data we also adhere to the common service data model if you want to you know expand on this and have your you know service portfolios and things like that as well integrated here also that's also going to be set up here and then last but not least you can integrate with your with your change workflows your itsm workflows so you can see there was a change associated with this cluster and somebody's making a change to a service we have some information here if we want to go into this record we can go into it and me as a a person that cares about this stuff I want to make sure that okay if somebody wants to make a change to the service I can even go into the Cloud observability solution again if you have the license and see if you know how is this thing operating if it's operating normally then okay I'll approve or we can go ahead with that change so that's all for for this part which is pretty straightforward the next piece is the calculated application service so these are all of these Dynamic service maps that got imported um via this service graph connector if you get this integration you can see right here it's coming from open Telemetry we have 21 of them and what I would like to do here before I go into this well actually once I load this map I just want to go back to this demo architecture here it is a little um can't really see it too clearly but I also want to show you how the map looks like in um the Cloud observability solution so does that a map looks like here you there is a way to get to an advanced map that looks into the the one that I showed you before that looks at the grpc and things like that but we really just want to look at this one what we also want to see is that inferred service I think it'll have this this is a pure Cloud native map but again these maps are not going to be running in a vacuum they're going to be integrated with some Legacy or some existing application this application can also be you know in the cloud as well right that you did a lift and shift for so it can be an Oracle database but for our scenario this is a SQL component this part that's associated with this feature flag service if I go back here this is the same map here and you see that this feature flag store is running on a postgres database so let's go back to our calculated application service well I guess it never loaded let's open it up all right so this is our map that was imported and you see that this postgres database here is here also so there is some work that has to be done to bring this over so let's go back here and let's show you the inferred services so we go to this inferred Services piece you'll see this component here you had to actually manually Associated this together if I go back here you have to go over here and search for so and select the one you want to bring in once you select it and bring it in it becomes part of that map right uh what we can also do here if I want to go into this front end component and open the dependency View I talked about all the various CI types a service map doesn't show you all of that it's just you know it's a service to where it seemed to be let's go into more details here let's make this a little larger let's um Force this so we see the calculated application service here the feature flag we see the postgres component we get to see the hotel demo piece we see it's a kubernetes deployment good to see the cluster so we get to see all the level of detail we need to see over here and again we see all the associated sea ice and everything else here as well if I go back here let's go into this postgres component because again all this is is that there was a span that made a call out here but this is a non-instrumented application that's what it inferred services and inferred Services a non-instrumented application or if there's a service that there was a span associated with it if we want to we can go into this postgres database now let's take a look at it and see what this is related to all right so we see this postgres is running on Linux it's tracked if we want we see as a tomcat component so it's part of another map so if I go back here whoops go to service map let's go to application service we see that this postgres is part of this rewards processing application let's go to rewards processing and here it is here's your rewards processing application and here's my postgres database that's to validate 1835. 1835. so we know that there actually we're actually sharing so we deploy this application we deploy everything kubernetes but we don't want to deploy in that new postgres database so we're sharing this postgres database with the rewards processing application so now somebody made a change here we can assess what that impact is you know for this application but also to the application we're running okay we have running here as well and that's the end of my demo but I'll pause to take questions yeah we answered most of the questions actually AC Rossi is answering um the second last one and then we have uh just the last question here that has been announced first so uh they're asking if the clients should use the open Telemetry application what else a little over there um so yes so so client should use I'd like to clear out a question so really anybody can use the open Telemetry SGC all you need is a discovery license to use it and the application it's really a it's an agent um we'll post links to it actually let me go back to my slides I do have some links there yeah I think when it's just to be clear this only works if a customer is already using open Telemetry we wouldn't necessarily recommend that a customer goes and implements open Telemetry just to use the service graph connector actually that is that is a recommendation that is a recommendation of Steve can you explain that further then yep yep so again for the most part observability itself is a is a journey onto itself and if you have challenges bringing data over to the cmdb and the current methods are something that uh you know your SRE your devops team are not improving because it breaks either a security model or it's a resource constraint they can go ahead and use the open celebrity collector it's it's roughly it's less than 50 Megs in size right and once you deploy it all you need to do is specify an oauth key on where to actually ship the Telemetry data over to on the on the on the kubernetes side and after that you're doing everything from a SGC perspective so yes we do recommend customers uh if they're still starting and we haven't speaking we've spoke to almost 100 customers already about this um service graph connector some are more mature than others and already you're adopting open Telemetry but some organizations are still early in their journey and they're having challenges bringing data into the seem to be and bringing data seem to be you know I know it's uh not useful to some organization but many organizations they want to keep track of every single every single component has an IP address there was one vendor that their VPN went down it caused uh some business impact to the organization and now they need to keep track of everything that has an IP address and I have you know thousands of containers so now they want to bring everything into the same DB some other organizations that need it for you know auditing for reporting for those kind of use cases as well they also want to bring that data scene to be uh so you know for them using otel was was a very easy way to do it plus it helps kick-start their observability Journey as well plus again I'll keep it hammering on this but it's something that's kubernetes native so if you are an SRE or an engineering organization or a devops team it's using um the tools and some of the Frameworks that are very familiar to them already so it's not something they have to like uh you know reinvent the wheel to do something that uh they're probably not familiar with using today uh so we did the demo um I want to go back to this poll I just want to highlight that um as we're going through this poll because we're using open Telemetry kubernetes is not the end game it's really any technology that can use open Telemetry can also be brought over to the cndb right because everything all of these newer you know toolings and Technologies out there that'll that fall under Cloud native it's focused on organizations building these net new applications and as I build these new applications they still need to basically have the ability to to you know leverage a you know some kind of observability solution to understand where that needle and Haystack is because there's a lot of moving Parts some of these microservices are you know tens to hundreds or thousands of components Spotify is actually a a customer of ours as well and they're running the stuff at really massive scale and for you to get the uh pinpoint where the bottleneck is you need some kind of observability solution to help you get there so these are some that we have identified to add uh to a roadmap as we're speaking to customers we just like to know which ones you guys feel is the you know the next you know key technology we should be focusing on yeah we have time still okay I guess we'll end the poll because it stopped I want to share the results wow so that's that's great to hear uh so serverless Computing and function as a service is number one by far the next one is API Gateway then Kafka and last but not least is service managed so so actually thanks sir thanks everyone for the poll this actually helps us from uh for from a roadmap planning perspective uh let me just share this foreign share my screen now um I see there are still a couple of questions there that need to be okay answered before we keep going can you see my screen yeah yep let me go answer some questions yeah can you see the questions there in the Q a yeah I see it okay so the first one that might be for for you or Steve do you have any plans to implement service graph connects for Fortinet we submit a request early on this right we don't actually own the service graph connector roadmap there is another entirely different uh product team maybe Steve has some insight from them we do not have um I do not have any insights into that um we are working on patterns for 40net for our firewall Audits and Reporting solution so perhaps that would help without requests but we can find out and get back to you guys thank you all right the next question we are currently implementing kubernetes Discovery sometimes I am asked by the business how will this data be used what is the eligibility to pitch answer to this question so I kind of uh touched on it I would say from a CME perspective it's around auditing reporting enterprise-wide governance things like that those are typically um what many organizations are use it for so if you use it seem to be for those kind of use cases you can use it for that there's also I would say the asset management use case maybe you want to look into the all the software running inside those containers and keep track of that as well that would be not a use case and then we also have some other Integrations with the with kubernetes from a security perspective so you can also integrate into your uh enterprise-wide um you know secops practice also I don't know if you have any other questions Steve or gene on that because you probably have seen that too in the past okay [Music] um yeah we we still have another uh question on again so for Steve so uh one question is that they are challenging to discover Fortinet wireless access points and they are able to discover Cisco wap's webs so understood that questionnaire is not specific to this webinar we can take that one offline yeah it's about another service graph connector that's outside of open Telemetry so yeah we can follow up with that if so uh I see Ross is entering Troy's one and Kim is Anthony avinash's one there's the last one by Daniel what are the cstm implications of automatically creating calculated services will there need to be manual associated with existing business applications so I did speak to one of the product managers here um any um any um microservice uh this is what it what is what they are that gets imported via this integration falls under Business Services is what I was told but if you want you can go in and modify that but Windows was built this is adhering to the the common service data model so you could um you know associate it with existing applications too if you need to nice so Kim is working the last one yeah so yeah thanks everyone for the uh great engagement today um we will share on the same page of the community where you could reduce her to this webinar we'll share the deck and you will also find the recording so these are some resource of the resources that you will be able to leverage once uh you will download the deck and please we saw many ideas even in the Q a section we always encourage all of you to submit your ideas in the idea portal when you really listen to these ideas as a matter of fact those ones that um get submitted for more than 10 different um in more than 10 different cases let's say will be directly prompted to the product managers in order to be considered for the roadmap so this is another great tool for all of you to influence our products in the future of our products now we have a few call to action items so first of all try out these capabilities in sub production and showcase really the value to the stakeholders in your organization and get them really excited about these uh capabilities um we are offering these capabilities specifically they can be tried out for free as of now before it's GA as we mentioned uh before um you can connect with your new friends of course outside of this Workshop and we are here for you so uh you already asked a few questions but we're always here for you to help and please please um whatever success stories you have we're more than happy to listen to your great success stories so just feel free to share them with us um we'll have uh as usual further um future sessions especially for the item visibility and governance and further episodes uh in the rest of this year so please just make sure you're enrolled you subscribe to the live on service now webinar series that includes also this series of webinars this is the overall value that you can achieve specifically for service operation Excellence with item visibility and that was it for today thank you very much please make sure you fill out the survey at the end of this event we are very happy and thankful for all the great interactions we had today so we're looking forward to see you until next time and have a good rest of your day everyone thanks thanks everyone