anyways um pleasure to have you all here my name is Aaron Bennett I'll be uh helping manage the Q&A U please ask questions throughout this presentation um don't be shy about you know um putting a chat in or putting in a Q&A we'll try to answer them in line um with the presentation material if it if it fits well if it's a little bit of a deeper question we'll answer it in the chat or we'll save it uh for you know sort of that um interim period where we're switching to demo or towards the end depending on the you know how how much um it takes to answer the question we'll make sure that all questions get answered for the purpose of um post webinar views so we'll have these uh available for you know sort of curiosity so anyways a quick couple of housekeeping slides before we get into the main content um just Safe Harbor know that we may you know reveal some forward-looking information and uh you'll want to contact your presenters we'll give you an opportunity to get contact with your presenters to validate that information make sure that you're clicking the right apps in the store and that you know any features that you're anticipating to to get with these Integrations that you'll be able to um make sure that those are there so just so you know Safe Harbor um for any other events on service now the live series um please visit our live on service now Community page you can also scan the QR code see what other event EV are coming up we've got knowledge coming up so we've got a lot of content building towards that big event this year also um again like just quickly on the Q&A please please input questions uh into the webinar tools and we'll be sure to answer those um this will be posted to our YouTube channel for um service now Community marketing and it will be posted to the to the event blog so you'll be able to find this after the event and um you know catch up or share which we'd love for you to do so um thanks again everyone as we get into the to the main content for today um starting with juniper Miss and I'll turn it over to uh toas to get us started y thank you Aron so let me share my screen this one okay so um as we saw most of you know about uh but we still have to explain a bit about Juniper and Juniper me so I will not spend too much time on that just to give you the big picture um to start with so Juniper is one of the main um Network infrastructure B we are providing hardware and solution for data centers for service providers for compuse networks and for example for service providers there is more or less half of the internet traffic which is going through Jer devices so we have a pretty nice footprint on this uh the same for data centers for public cloud and private Cloud but in this case we will mainly focus on the compuse networks so compuse networks may be for Enterprise for hospitals for education for retails for all the environment where um relable network is is required and we are providing a full stack solution which means that we are providing the hardware for the wireless for the Wi-Fi for the Lan and for the one sd1 sassy part so all the hardware that will be required to to have um the Enterprise Network up and running and what is the most important here is not really the the boxes of Hardware but it will mainly be uh the management solution that we're providing uh it is based on a Cloud solution and we are using different type of machine learning and AI to automate different part of the process to configure or to monitor uh the network uh we will see that a bit later especially with the service gra connector but one of the main interest here is also everything that we are doing from the MyUI from the management interface we can do it from the from the apis which means that all the configuration all the monitoring part all the alerting can be through apis uh so this is super important to be able to integrate uh Juniper the M solution with the service now solution and we will see that we we did different type of integration um and the first one will be to help to automate the deployment so to configure mist from service now directly and the second one is more the opposite so to send some kind of alarms some alerts from uh from Mist into service now and also to be able to synchronize information regarding the the different type of devices so we currently have two different uh application uh that we're working on the first one is already available on the service no store um it's a free application it doesn't require any additional uh licenses or adding any cost and it is mainly focusing on the d0 and D1 use cases so what we are calling d0 D1 is mainly all the processes that are required to be able to deploy a new network um so to be able to create most of the configuration on the mid side to be able to um to to link the hardware to uh to the configuration and in fact everything that is required to just have to plug the device devices on the network and so the devices will uh will get the configuration and be up and running it's not really important for small customers because I mean they can do that manually from the M dashboard without having to automate this uh but when we are looking at some customers that we are uh that we have at Juniper Mist uh for example service no but also for example Walmart Google and others uh they may have hundred of thousand of devices is deployed on hundreds of sites and having to do that in service now and in in M dashboard uh will add a lot of time uh they will have to enter this information twice and uh they may have some they may make some mistakes when they're copy copy and passing the information so being able to automate all these provision provisioning and deployment uh process from service now is saving a lot of time uh and for example when they want to deploy a new site from um from East they just need to put the information into service no and more most of the time information are already available into into service no and we can ask service now to create all the required configuration um into mist uh so to create the site to create the a template of configuration to uh assign the license to assign the devices uh to um to to the Mist to the Mist account and so they don't have to go on the M dashboard to uh to do anything they just need to uh do the action on the service no side and from there they just need to send someone on site to uh to plug the devices on the network and to check that everything is uh is going up and and and running so this application is already available we will talk a bit more in details about this application just after and the second application is the service gra connector so since most of you already know about service now I don't think I need to explain what is a service gra connector but uh basically it's ingesting the information about the all the devices that are managed by mist and ingesting all this information into the service no cmdb uh so we are doing all the mapping we are doing all the process to the information from E processing them doing the mapping and storing them in in as cmdb uh this one is still in beta and there is another part which is also that we are working on for this one is to be able to um get the different type of alerts from Mist uh so I said just before that we are using machine learning and AI uh to help to Monitor and manage a network and in fact for example we are using this type of uh solution to be able to um detect when something is going wrong on the network it's not only because of a switch is going down but it may be because we learn the behavior of the network and we are detecting detecting that um an application is having less bandwidth than expected uh because um the zoom call is having bad um bad time and we're able to detect to detect this kind of issue and to detect the root cause of the issue and with that uh and with the Serv Conor we can send information into service now automatically open a case or an incident and Link it to the to the network side to the location and to the specific uh Network CIS that are linked to to the issue um so yeah can you go back back toide one second there toas one thing I wanted to add to what toas was saying was that we actually address two different use cases with the automated uh deployment product and the service craft connector uh one is an Enterprise use case which would be simply for like a campus and Branch type of setup so uh things like retail companies or really any Enterprise that has a juniper deployment could take advantage of the automated uh deployment application to push configuration like Tomas was talking about but also on the other side of that we have another set of customers that are Manor service providers so man service providers can also take an advantage of this uh solution as well by using the automated deployment and the service craft connector on behalf of their customers and service now instances there are a handful of different service now products that support both use cases um of course both sitting on top of the service now cmdb thank you toas yeah thank you um and yeah I just saw a question so to the question so is Juniper resource Cloud controller managed by Juniper the cloud so yeah to make it simp simple it's the solution that we are providing to manage a compus network so all the G devices for the for the Wi-Fi for the switches for the one sd1 and so on directly directly in the cloud uh and we are adding some U we are using leveraging machine learning and AI to to help administrators to Monitor and to troot the network uh so it's a Cloud solution uh to manage the Juniper devices great okay thanks Tomas all right let's go over a little bit of the architecture of the solution here so with the Mist platform we've actually integrated a handful of the API endpoints to do various orchestration activities and to pull data into service now so in this diagram here looks a little complicated but what we're effectively doing here is we're pulling in data from Mist let's call it metad data and that's typically about sites in Mist site groups in mist templates and then all of the different um site variables that we have available for each of those so what we're doing is bringing these into the service now platform putting them in a table that we have developed as part of the automated provisioning app and then we're using all of that data when we go to provision configuration to devices whether that be in the form of consuming a new order and provisioning a new site or updating um or decommissioning a current site so if you look specifically here the table that we're actually populating the the service graft connector takes care of and we'll talk about this a little bit later takes care of populating the cmdb side of this but this is really aimed at being able to do order management for instance so if you're a managed service provider we have an order management application in service now you may be familiar with Um this can plug directly into those workflows all of the information here you see that's being collected in service now platform can be applied there as well as for the Enterprise use cases where these can be dragged into workflows or flow designer workflow as a integration Hub action to be able to be used in service catalog items as well so this can kind of fall into both areas depending whether you're an Enterprise or a manag service provider and depending on what service Now Products you have available um for your system oh next slide there thank you okay so taking a look at the setup here right so this is going to be very similar in the same vein as um if you're used to configuring service craft connectors or any other integration into service now we're taking advantage of our connection aliases and credentials so here's a screenshot here of what you're going to be filling in as part of this uh the one piece here I mentioned the manag service provider uh side of it if you look down on the properties there we actually collect the MSP ID which is a concept within Mist for our man service providers or our Mist organization ID which is uh again one for maybe the Enterprise where we have a single organization with many sites underneath that and then of course on the right hand side there what you're seeing is a screenshot of how we bringing the site data into service now and these are lined up by the organization or the MSP ID that we pull from the Miss platform I mentioned go ahead yeah know this one is just um an example of all the action that we have in the in the spoke in the application so currently we have a bit more than 70 different action available with some uh with some sub fls and everything is documented so uh for example if uh if you are going to um to the service no store you can find the J automated provisioning application and so from there it's um what service now used to do so you have installation guide we are also providing the um some some kind of administration guide which is listing uh all the application uh all the actions so uh you can find all information with uh what type of input you need to to pass what kind of output you will uh you will get uh in the response and this for each uh and every action it's the same for the subflows and the data streams so you can get all the information directly from here um and with also yeah in this case T structures so you can get different type of information directly from here I know that we have a lot of probably developers in the audience and I know that you probably get excited when you see a lot of actions like that so to answer some of the questions you might have um yes it's a full service solution right so however uh in our implementation of this it's effectively just a Spoke so if you're familiar with what that is that's basically a set of actions with inputs and outputs that we have documented very thoroughly there um the job of the developer now for everybody in the audience here is to take these actions and Implement them into your service not workflows either ones that you have existing or creating new service catalog items or uh New Order management workflows uh to be able to do the provisioning piece here um through the Miss platform so it's very exciting technology and this is really one of the first times service now has had a really tight integration with a vendor like Juniper to do this type of work so we we really encourage people to around with it we want to hear your feedback yeah and this is what you are seeing on the right it's one of the work for example that we created uh we will show you just um a quick video of an example uh on the next slide but uh it's mainly that we are providing the the tools uh that you can use in the workflows and in the different uh places in service now to automate uh the Mis configuration the Mison deployment and uh and everything from mist so in this example so we created a small workflow uh based on uh the order management system uh which is simulating when um service now is receiving an order so in this case the order has already been created and what oops and what happen is um when the order is approved uh service now will automatically create all the task that are required for for this specific use case and this will call the different uh flows and this will call the different actions so we can see that in this case um the flow is creating a m site so M site is just like a location in the service Noor and it is also assigning the templates to the different parts of the configuration that are required for this site it can be for the for the Wi-Fi for the Lan for the Gateway and so on which means that at this point all the configuration is already ready and available for the site and then we just need to say okay I can deploy the the hardware now and service now will automatically assign the devices to the m assign them to the um to the site and and uh if needed assign the right template and the right configuration uh if something is required and we can see that everything has been automatically created on the Mite so this one is the m UI we can see that the site has been created uh with all the information with the address from service now with the country um the devices have been claimed and assigned to to the site uh the templates uh assigned to the site and so on so uh which means that without having to do anything on the M dashboard we can deploy uh we can totally automate deployment of a new site a new M site from service now um and use the service now workflow service now UI to um to manage all the process and uh yeah so the second application as we say uh is service G Conor really quick uh Tomas we had a question that came through chat around um like decommissioning or de-provisioning so would you want to answer that one now or would you want to take that one later no yeah I can talk I can take this question now uh in fact uh the process will be more or less the same you can uh the decommissioning will mainly be regarding the licenses and the hardware so it's mainly to be able to unassign the licenses so you will be able to assign them to another organization or another customer in case of msps uh and the devices you can unassign them from a site from an organization and assign assign them back to uh to another customer or another site if you want so uh all the action are already available in the spoke so you can automate this process of decommissioning directly from service now without having to go uh on the M on the M dashboard yeah and the one other thing I'll answer on that is on the on the configuration item side in the cmdb uh when that decommission happens if you have the service graph connector that we're about to talk about here uh that's where it's going to reflect the changes back in your cmdb so in this example um let's say for instance we decommissioned a device and it's no longer coming back in the Mist import into the service graph connector what's going to happen is you're going to probably have some configuration for that those CI classes of that Discovery source which would be the Juniper Miss um service craft connector to age out devices that are decommissioned uh because what will happen is devices just will simply not come in or update the CIS anymore so you'll have to have some strategy around that and we'll discuss this a little bit here in the next portion of our webinar yeah and it's the same if you are replacing a device for example if you doing some kind of AR to to replace um faulty Hardware uh in this case there the new hardware will come up in the service G connector and uh you will have to um to use different kind of policy on the cmdb to automatically clean the information okay super all right so what we'll do is we'll talk here about the service graph connector a little bit and the architecture here is very much the same as most other service craft connectors we're simply pulling um an API import from from the Juniper Mist platform of all of the devices and we're taking those devices and mapping them into various classes and I think we I if we talked specifically oh yeah we do talk specifically about the classes here so um what we do is we're we're there's three classes on the service now seem to be that populating we're populating IP switch IP router and Gateway which is a access point wireless access point and um and also the switch Port configuration for those switches and routers as well so there's that on the cmdb side and uh if you are a man service provider we do have the option for you to activate the TNI product which is our Telco Telco Network inventory uh what that then does is as the Mist um platform is being pulled through the service craft connector a TNI entity record is created alongside of it um that will help our U manag service providers be able to organize uh the different devices by their different clients and then be able to put more of a Telco or media Assurance type of spin um on those CIS that are being brought in and for their customers um again the the setup process here is uh very similar to our other service graph connectors we have a guided setup for you to go through um you're going to be inputting some of the same information that you were in the uh the automated provisioning app you'll have a MSP ID or an org ID that we're going to be using to pull from the API and then that's all configured through our um credentials and connection aliases yeah and just the difference between the two application uh in M we have different kind of roles for the administrators and for the API tokens uh for the first application we need a read API token and for this one for the C connector we just need a readon API token and um regarding the alerting so the possibility to automatically open an an inent or case from m it is using uh web books so mist is directly sending the information to service no and service no is processing listening for this type of messages and uh processing information when the message is is received yep and here is an idea here so I mentioned the TNI product uh so what you're seeing on the left there is um actually a screenshot from our uh Telco equipment or Telco inventory product and this is one of the dashboards here and you you can actually see um on the left there you see all of the Telco equipment listed underneath that site I believe which is called live demo um and this is all this is all the classes of all of the devices that are existing for that site and that is all being pulled as part of that TNI entity record that's the conduit between the cmdb and these workbenches and all of these TNI based products and on the right hand side here is simply a screenshot from the cmdb and what you'd expect to see uh when the Juniper service craft connector is implemented the kinds of devices and connections that you would see in service now cmdb yeah so we are automatically doing the relationship between the different devices network devices that are managed by Mist so we are looking at the information for example from from the switches to know which type of device which Mac address is connected to which switch port and we are creating the the dependency view from the from them uh and the same for the routers we are able to do the relationship between the different ERS if there is some kind of VPN connection between them uh so we can have the big picture of the network uh without having to do it manually it is totally automated from uh from the from the ET yep as the uh I mentioned earlier some of the classes that we're populating so what we're doing is taking the interfaces from each of those switches and routers and populating the network adapter table and all of the information about those adapters their IP addresses uh Mac address information uh interface names and then linking those back like you saw with the relationships to the uh routers and switches themselves yeah and um yeah Al this one is not yet published but um it's currently in beta and there is also some um documentation that I'm working on for example to be able to uh Define on to explain uh how the different CI classes are used which type of field we are using from where the information are coming from uh so everything will be documented so you will be able to know exactly what kind of information we we are using from mist and where do we where we are storing them uh into the the cmdb and with which cmdb class we'll take the opport Unity since it's the bottom of the hour and we can sort of transition into a deeper dive if needed um so that those of you if you do have to go uh we can uh follow up with you on any help you'd need uh with either of these Integrations that are available in the service nail store so uh these Solutions the the first is is published and available today that's the catalog solution and uh that one's readily available and If if you'd like a followup with uh toas and Ben um just let us know and we'll do Outreach after the session um we'll also uh touch on a quick question that we had come in as well while we're doing this quick pause also um the service graph connector is um is at the end of its development cycle and is in uh testing by um you know customers including an internal customer here so that one is available for for immediate use if you contact us so that would be we' need to make sure that you're included in that process uh since that's ongoing at this point in time um the connector is due to be released soon I don't know Ben or Tas if you want to comment on ETA um since we are being recorded they TBD on that one yeah soon not a long time from now very soon it soon but but since since it will be soon um please please uh check for a followup so we can reach out and let everyone know when it is available because it will also be published in the service now stored um under our service craft filter so um we'll leave this up for just a moment and see who would like to see more and on what so if we can go any deeper uh today Ben and Tomas I think first um we'll need to cover uh the servers graph in more detail let me give people a few minutes to answer so um while people are still responding to the poll um uh B do you want to um to rewind any of the content around the service graph since it's not available yet maybe we can we can talk about that one in a little more detail yeah you know the the use cases we generally see with service craft connector are usually one of two things we're seeing seeing service management type of use cases so obviously the incident problem change type of stuff right um then we're also seeing event management so toas had mentioned earlier that the uh events that are coming out of the Mist platform are being consumed into service now through a through an API and that can simply translate into something like an incident record or can come through our em event table and be routed according to the customers configuration right um so EI either way is fine and uh we actually have that kind of working today um like I said it's it's an API only integration today like a web hook uh but those are the generally the two use cases we see with the service graph connector but I would be curious from the audience if they um had any other ideas of what they would be using that for um inventory is usually another one so if you're using like more on the asset management side that's not one that I've heard a lot um with this but I mean it's obviously capable of providing information about the Assets in your Enterprise um so definitely curious to hear what uh some of the audience would have to say about using a uh technology like this to integrate Mist into service now all right we'll do here is just end and share these results it does look like there's more curiosity around the service graph connector still some would like to talk a little bit more about the catalog and what's possible there um and we will be sure to follow up with those who indicated that in our in our poll um so we'll we'll pass that connection information back and U um and what you'll hear from us shortly so um I guess toas and Ben anything else that you'd like to cover um in more detail you know maybe toas if you want to go a level deeper on the actions available from the catalog app or if anyone has any questions uh now would be the time to uh get those questions in so we can we can take this in whatever Direction the audience feels is best we also had one question in the Q&A we make sure we get that covered is Juniper missed a resource Cloud controller managed by Juniper in the cloud I think we already answered that one Erin I think we answered that one already yeah okay yeah know if you I mean if we are looking at the a few minutes if we are looking at the different uh action that we have um I will not go through all of them because as I said we have more than 70 different actions um it's all the actions which are requireed to be able to um configure and deploy a new sites uh and to assign the devices so uh for example we can add devices a new device es to the organization based on the Mac address or based on the what weing the claim codes which are specific to each Jer device uh we can assign um we can assign the the devices to a site so we can assign them un assign them from a site or also delay them from the organization um so we can do all this type of action to um to get the the devices the Wi-Fi access point the switches uh the gateways the routers um assigned to a site or and assigned from a site and then also to um to to um um create or assign the template the configuration template and what we are what we plan also in this type of in this type of use case is for example for msps to have some kind of blueprint organization which is one organization they have where they're creating the uh the the the uh where they're creating the templates for for for the customers and for the configuration and to be a to be able to clone the template the templates from the blueprint organization into the customer organization so they can already have some kind of basic configuration available and uh even without having to go on the M dashboard to prepare the template to prepare the uh the basic configuration that can automate all the process and with uh let me just move this one uh with some subflows for example to clone the the gway template so we just need to provide the source organization the destination organization and the template I identifier and um the flow will automatically clone all the required object from The Source organization so from the blueprint organization into the customer organization so this is very useful to be able to keep um some kind of standard configuration across all the all the customers and all the configuration in case of uh some kind of msps but it can be also used for customers to have some some um preparation organization where they are doing some testing some configuration to uh where they're validating everything and once it's validated they can push this type of configuration into the production organization I see we had a question in the chat here said uh use cases like network discovery can be addressed through service craft connector so yes uh yes kind of so um the the network devices themselves yes if you're thinking about the clients behind the network devices we can really only get more limited information on that so we're not actually pulling in all of the client device information right but we are getting all of the network device the access points the gateways the routers and all the switch Port information and bringing it into the cmdb um just not the clients at the end point uh yet right um we have talked about doing some things in that space But the current service graph connector does not have that capability that answers your question yeah yeah and inid it's possible from Mist uh if I'm going if I'm showing you what we can get from the M um apis uh let me just go we can get some information for example regarding the connected devices the where client and so on um it's just that at least for now uh we would prefer to not take this type of information so we can see that in this case we can get uh a list of wire clients so it's all the laptop printers and so on connected to the switches and we can get some information uh especially if you are using 1X authentication in this case we can we can get um we can get the the username for example uh the MAC address and we we it's possible to send this type of information uh to service now it's just that at least for now um for privacy concerns uh we are focusing on the hardware part on the network on the switches access point and so on rather than on the client but in it's possible I think the other thing to talk about here too on the service graph side is that mist doesn't just have Integrations to Juniper equipment correctas there's also third parties that M can bring in as well can we talk about that a little bit yeah absolutely uh good point so we also have some integration with third part solution like C PRS um to be able to let me see yeah we have one here uh so when we have a Cel Point Gateway so it's 4G 5G Gateway is connected to a to a misted device we are able to get this information and we are also able to get information from the um Cloud management solution from c p so it's Cloud to Cloud communication between the McLoud and clont cloud and we can get information regarding the RSI regarding the status of the of the Gateway and so on uh So currently we are not sending this information uh into service now but it's something that is planned uh to be able to get the to synchronize information about the third party uh devices that we are monitoring from Mist yeah and just so everybody knows the the whole thing here is now we not only have access to the network equipment that's directly kind of within the privy of our Enterprise or our man service but now we can also go out and find the real Edge devices so those those credle Point devices that are out on the edge communicating in the uh 4G 5G networks and all of that we can now inventory that into service now um I think traditionally uh those types of devices don't aren't discovered in service now simply because our Discovery products looking in the network inside of a company these are out in uh you know like a carrier Network so but they are absolutely still assets so so this opens up a new use case for us to be able to inventory these Wireless assets into the service out cmdb and run some of the same workflows we do for the equipment that we have on on our sites so we got another question in the chat here um for service graft connector is it purely based on API or is it or do we need SNMP um purely API it's a API connection to the McLoud platform there is no device polling from our side from the service now service craft connector side um I not sure M works is that does there SNP involved in how Miss works or is it all proprietary no we are trying to avoid SNMP so for the switches for the gateways we are supporting SNMP but it's mainly for local monitoring uh in case of cloud monitoring we are using uh in fact it's mainly uh a web soet with which is established from the network device to the McLoud and we are streaming information in both Direction in fact for the stats and for the configuration or for for the action that we want to perform on the on the devices um and um m is exposing all this type of information through API so for example I can get all the switch stats from the API so this is um just one API call to get the startat from all the switches on the site and it's what we are using on the service gra connector we are using this Ty this type of information so it's j um J pillow with all the information regarding the the switches access point gateways and so on there so one more question in the chat here I'll just read it out loud uh do you support l/w devices router switches Discovery through this not referring to end use end user devices um yes yeah um earlier we discussed how we were bringing in the uh data into the IP router table and the IP switch table and the wireless access point table in the cmdb so yes we are bringing in Lan and Wan devices from that perspective um I believe as far as like the actual ports as well Tom I don't remember if we were designating whether the ports were a Wan port or a lan port in our um in the data we were bringing in but we are bringing in the switch Port information for those devices as well yeah and the only thing is we are only synchronizing the information regarding the devices man managed by Mist so for example if you are connecting a non Juniper switch to a juniper switch will just report information regarding the Jer switch uh all the other devices connected to them um are more or less seen as a client uh and it's not possible to know if it's uh some kind of end user device or another switch or another Network device so we are only reporting the devices that are managed uh monitor mostly configured by uh by me so it's for the switches for the gateways and for the routers we are not yet reporting if it's one interface or line interface uh I don't so let me just check on the uh on the IP router let's take this [Music] one um yeah I don't think we are delineating whether it's a Wan port or not I mean you can kind of tell from the IP address maybe but um yeah I don't know if we were actually delting there's some field that we can use for that but if there is we we can definitely add this type of information yeah so for example yeah for switch is we have all the switch Port uh the network adapters if the switch is uh using layer three uh we are also reporting the different IP addresses that are used and um yes the version of firware the serial number the MAC address and all this kind of uh of information right so we'll repeat if there's any other questions or you know directions you'd like to to point our team uh to to dig in on any specific information um we'd love to' love to answer those before we sign off here Ben uh toas turn it over for you for any for any final thoughts or calls to action yeah uh reach out to us if you start to use this in a development environment or you start thinking about some use cases you know we're always interested to enhance the solution so um as you guys um continue to look through this or download the apps from the store uh feel free to reach out uh we definitely want to hear from you yep please please leave a comment oh Tomas anything you wanted to to add yeah I know that's uh um yeah we are still at the beginning of the process so um we are still waiting to get some feedback from different people uh depending on the use cases to to be able to improve the different applications so yeah as been said just feel free to uh to contact us if you have any question any feedback regarding regarding the applications absolutely so yes um yeah LinkedIn talking creating a post on the uh the event blog or in the community um tagging Ben or toas or for myself even we'll definitely uh respond to those and we'll get back um I'd like to thank everyone again for sticking with us uh through the content today um you can find this recording uh once it's been posted it should be a day or two uh to get into the community and onto our YouTube channel and with that um I'd like to thank toas and thank Ben once again um we'll stop the recording at this point and hope everyone has a great week