Name: Unveiling New Capabilities of Proactive Digital Experience Management Enterprise
Uploaded: 2024-10-16T16:17:37.565Z
Duration: 45 min 4 s
Description: Unveiling New Capabilities of Proactive Digital Experience Management Enterprise

Transcript for "Unveiling New Capabilities of Proactive Digital Experience Management Enterprise": Us today. We'll be chatting about the new capabilities that proactive digital experience management enterprise will be providing you. Now before we begin, let's give about 30 seconds for the rest of the folks to join us. Thank you so much for everyone that's here. I'm Priyanka Bani, Product Management Director here at Netskope. Joining me is Thierry Nerevans, my teammate, and between us, we drive proactive digital experience management as a product line here at Netskope. Before we get started, a few housekeeping rules. The recording of this session will be sent out to you after the webinar and Q and A and docs are available in the tabs on the right of your screen. Now, proactive digital experience management. With the transformation to the modern workplace, sites, employees, SaaS apps, Cloud hosting, these are now extremely highly distributed and they're interconnected by Internet based networks. Now, this new perimeter really drives the adoption of Secure Service Edge, SD WAN, and Zero Startup Trust strategies. This, for all the benefits that it brings, it also adds a new layer for IT to build out and manage. Now infrastructure and operations teams are used to having complete visibility across their infrastructure, which is very vital to be able to monitor and optimize the performance of mission critical and business critical applications. Traditional monitoring tools have struggled to see in this new reality, in this new transformed network essentially, where encryption and SASE makes traffic analysis and real user monitoring quite impractical actually. With dynamic hosting and hybrid workforce, this really means that flow analysis sees only a fraction of the network activity. Now, as a result of this, modern IT infrastructure looks like a really fuzzy gray cloud, essentially a black box that keeps changing. Now this lack of clarity really prevents IT from quickly identifying and resolving issues. It puts user experience and productivity at a very high risk. A new approach is needed to regain that visibility and control that teams truly require. To overcome this visibility gap, infrastructure and operations teams are turning to digital experience monitoring, or DEM, solutions. Now Gartner has predicted that by 2026, 90% of organizations plan to have DEM as part of their repertoire. Now, DEM is designed specifically to monitor the modern IT reality. However, these solutions monitor using an outside in approach. They're unable to gain insight into SaaS infrastructure or its underlying components. While VM is the right approach to regain visibility, SaaS still remains a great cloud for stand alone VM solutions. Now add to this the fact that a lot of organizations want to consolidate tools. Now adding more vendors and tools simply increases the operational and technical debt. The solution to both of these problems is a SaaS integrated DEM, one that provides transparent end to end visibility inside and beyond SASE. Only a SASE integrated DEM solution delivers a cost effective method that simplifies deployment and tools while providing that unified visibility that fosters collaboration across security, IT, and network operations teams. Now, Netskope's proactive digital experience management offers complete oversight across the Netskope platform, user experience, and all the underlying factors that can impact it. The first in this set is PDAM Standard. Now PDAM Standard provides complete reporting and alerting for your Netskope real estate. It leverages telemetry from new edge private cloud and Netskope endpoint clients, providing detailed metrics that give you a view into the platform status and utilization across all user sites and applications. The next year, Pedram Professional extends that visibility to the digital experience of every user from any location that the user is operating from to any of the business critical applications that they use. It integrates real user and synthetic monitoring to gain that granular visibility into every step, all the way from the user's device to the application. Now, Pedram Professional was designed to empower New Edge, providing actionable insights that enable it to proactively optimize performance and user experience automatically. The newest addition to this is Freedom Enterprise. Now, Freedom Enterprise is built to add on more capabilities that offer expert level insights and analytics for security, network, and IT operations teams. It provides the capability to monitor on ramp, application performance, and user experience for users as well as sites when they're connecting to NetScope. Now that may be via SD WAN solutions, SASE gateways, or even private connectivity. Now, PDAM really delivers this effective insight for network and infrastructure and operations teams with in-depth contextual device to application visibility. It combines multiple data sources and monitoring methods to provide an accurate view of the real user experience. Now starting with the context that it collects by way of collecting data from the Netskope client, New Edge, and security proxies to provide zero touch real user monitoring and experience scoring for SaaS and web applications, including custom applications. Now the user context really, you know, it brings it all together by including device health, Wi Fi performance, location, user activity, and risk profile. And it enables the granular visibility into the first mile performance from new edge to SaaS web or private applications. In addition to that, the data collected from the site via our new component, enterprise stations, it includes network performance across any SD WAN solution, private connectivity, GRV, or IPSec tunnels. This advanced granular telemetry collected from the applications, application usage breakdowns, trends, server errors, response times, all of this comes together to provide information about service performances. Now it does this using our innovative smart monitoring methodology, which augments RUM with synthetic monitoring for a complete assessment, providing hop by hop performance along the entire network path spanning Wi Fi and LAN. It also includes NetScope on ramp, ISPs, SD WAN tunnels, and first mile application connectivity. What's unique to NetScope PDAM is that it leverages New Edge to monitor the NetScope platform itself for full transparency. Now as a result, timing Netskope reports the overall contribution of all services used in Nu Edge when processing the traffic. And thus, it provides a per user per application visibility for complete context and efficient troubleshooting. Now AI powered incident prioritization and alerts report these user experience issues, performance degradation, incidents, and events that are detected by beta, making sure that all teams and their tools stay in sync for close collaboration. Now let's take a look, a closer look, at user monitoring in PDAM Enterprise. For user level visibility, Netskope PDAM uses the Netskope client for monitoring. You'll note no additional agent is needed to be installed on the user's device to facilitate this monitoring. Now using Netskope client, PDM provides user level visibility by combining the context of the user's activity with each critical component, the endpoint, the user's using, the onramp path to connect to NetScope, the PoP that they're connected to when the activity is initiated, and the path they use to connect from the, PoP all the way to the application. Every single component that impacts the user's experience. Now in addition to these components, PDM simulates the user's activity by the use of a synthetic app approach that runs all the way from the user's device to the monitored destination and back to the NS client to account for end to end performance metrics like time taken for the 1st byte or time taken for the last byte of the response to a write. Now these granular metrics obtained by using both real user monitoring and synthetic monitoring capabilities provide the most complete and accurate assessment of the user's experience. Now, let's take a look at the new site monitoring capability that Freedom Enterprise provides. Here we introduce the Enterprise Station. This is a container based software that you can deploy in your sites to assess the user experience for any of your monitored applications, basically your business critical applications. It gives you a clear picture of the experience users operating out of the site have when using any of these business critical applications. And it does this by providing visibility into the onramp method, the POC that the users are connected to, as well as the path that's used to connect from the NETSCO POC onwards to the application. The elegance of this solution is that it simulates the connectivity method used by your users depending on your setup and your environment. It can show you the experience your users would have had if they were sitting in the office and connecting using DNS client, as well as the experience they would have when connecting to their applications using an SD WAN solution or natively managed IPsec or even GRD tunnels. Now enterprise stations use the intelligence of the Nuance services to constantly monitor the actual parts, the most optimal parts that are used by users to connect to NetScope while essentially monitoring the efficiency of these steering methods. Now with that, let me pass the control over to Keri to walk you through a demo of Freedom Enterprise. Thank you very much, Priyanka, for this presentation. In order to highlight the main product capabilities that Priyanka talked about, I would like to show you how the Netskope DAM solution can address 3 major use cases. The first one will be about the Service Desk getting a call from an end user complaining about a bad performing application. So in this case, as a Service Desk Agent, my main objective is to quickly find out the root cause of the donation so that I can route the support ticket further to the right expert team. In other words, I do want to determine whether the degradation comes from the device itself, from the connectivity between the device and the New Edge Cloud Infrastructure, from the New Edge Cloud Infrastructure itself, or from the application itself. In the second use case, I will play the role of a network operation team member who is interested in monitoring the New Edge Cloud connectivity performance. So for this use case, I do want to understand how the corporate sites as well as remote users are being connected to the New Edge Cloud. I do want to be able to quickly And in And in the final use case, I will change my viewing angle. So instead of being focused on an end user or being focused on the new Edge Cloud connectivity performance, this time I will be more focusing on an application itself. I do want to understand how this application is being delivered to my end users and corporate sites. And in case of any degradation, again, I would like to have all telemetry at disposal to find out the root cause. Okay. So let's start with the first use case which is about a service desk agent getting a call from an end user complaining about a bad performing application. Let's take Salesforce as an example. The first thing the service desk agent will do is navigate to the user overview dashboard. This overview dashboard shows the location of the end users as well as their end user experience. So for example, if I mouse over this region, I see that in California I have 516 users having a good experience while 6 have a fair experience when connecting to the different applications we are monitoring. Now I could have obviously filtered on this specific location to get into more details and identify these end users having a fair experience. But in my case, I know that a specific user is complaining. So I can also go directly into the filter and filter on this specific user who is complaining. I get the summary for this user having an average experience of 56, belonging to these user groups, using a corporate device which is managed by my corporate organization and using 12 applications. Okay. So now let's click on the plus sign to have more information. To start, at the top you have some information about the end user device itself. So like the operating system, the type of model, the CPU, the memory, the last location seen for these end user devices in terms of IP addressing but also in terms of geolocation. But more importantly, you have an end user device score, which is in my case good. So it means that during the last 2 days, the average performance from a scoring standpoint for this device was good. This score is processed based on multiple factors like system telemetry, CPU usage, RAM usage, IOPS, and so on. But not only to that, they are also based on the local connectivity performance, typically the Wi Fi local connectivity. So in my case, I conclude that during the last 2 days, I didn't have major average issues from an end user device standpoint. I will double check that but this is already a good indication. Here below you have the list of applications that have been used by this user during the selected time frame and seeing that I am more focused on Salesforce in my case, I just have to click on Salesforce to get it here highlighted and then all the dashboards will be updated automatically. So here below I have the evolution of a time of the end user experience score that let me determine whether the end user is complaining about a sudden degradation of the overall application performance or if the overall behaviour is always the same. And I see that from an end user experience standpoint for the last 2 days, the application was not performing so good but I cannot say that this application is really degrading. Okay. So now the question is what is the main performance driver for this application? Is it the device itself? Is it the local connectivity? Is it the New Edge Cloud Infrastructure? Is it the connectivity between the New Edge Cloud Infrastructure and the final servers that are delivering the app? Or is it about the servers themselves? This is what, as a service agent ldesk, I do want to quickly identify in order to route the support ticket to the right expert teams if needed. So I already told you that from a device standpoint, I do not expect to see much but let's have a look. So here I have a tab called device performance health metric which provides evolution of a time of the CPU usage, the memory usage, the disk usage. By the way I can go into all the details on a per process basis. So if I see a not normal increase of the memory usage for example, I can just click here and have a view process based. So I can see whether I have multiple Chrome browser open at the same time which consume much more memory for example. Typically, this kind of cases we see at customers. So I have memory, disk usage, network throughput, disk IOPS, battery life. So you see here, typically, this user is using a laptop, which is, you know not connected on the power all the time. So you see how the battery evolves over time as well as the Wi Fi strengths. So I see here that this user is connected on a very strong Wi Fi local network. Okay, I do not see any network or device abnormal events. So again my conclusion is that this end user device is not the main driver of the performance of this application. So the next step is to know more about the connectivity between the end user device and the New Edge cloud infrastructure. And for that I have a tab called Connectivity to Netskope New Edge. So if I click on that, I have all the information I need in terms of tunnel latency. So here I see that the evolution of the time of the network latency connecting this end user device to New Edge Cloud is quite good. It resides within 10 to 20 milliseconds which is quite good. My conclusion is that connecting this end user device to the new Edge Cloud is not what is driving the overall end user experience. Alright, so the next step is seeing that I do not have any connectivity issue, the next step is to know more about the new edge cloud infrastructure itself. So do I have a NetScope PoPs performing badly at that time? This is the kind of information we openly provide in our DAM solution. So you have it under the NetScope metrics tab. Here you have the evolution of a time of what we call the processing time. So processing time has to do with the time it takes for the New Edge Cloud infrastructure to process the traffic. Obviously, for this kind of traffic, speaking about Salesforce, you probably have configured some real time protection policies like data leakage or threat prevention. So it means that at DNS proxy level, we will have to inspect the payload of this traffic. And inspecting the payload and applying some DLP policies on this kind of traffic will take time. And this time is provided here. So you have the evolution of a time of the processing time and you have also from a network performance standpoint, the transit time. So the time it takes for the NS proxy to forward the network flows in and out. And you see here again that speaking about selecting, for example, this specific time frame, you see that the processing time is not the main performance driver because I have here a peak, for example, of 35 milliseconds. So which will definitely not really drive the overall performance because here again, if I select this processing time of 35 milliseconds, you see that it did not in fact, you know, impact the overall end user experience at that time. Alright so it's not about the device, it's not about the connectivity to New Edge Cloud, it's not about the New Edge Cloud itself, so perhaps this is about the networking layer between the New Edge Cloud and the app or the application itself. So to determine that I have a last tab which is application metrics. So if I go into applications metric, this is where I will see the evolution over time of the network performance metrics like TCP connection time, SSL endshakes, and the number of redirections that may occur between the new edge cloud infrastructure, so the Netskope proxy, and then the servers that is delivering the app. And you see that in fact here from a network connectivity standpoint, we are about 2, 3, 4, 5 or even 8 milliseconds sometimes. But this is definitely not what is driving the overall performance. But looking at the server response time you see that the server response time is about one second. So if you take the overall time from the end user device connected to a local Wi Fi network connecting to New Edge Cloud Infrastructure, taking into account the transit time with the New Edge Cloud Infrastructure, as well as the time it takes for the server to process the data, then it's clear now that the performance is mainly driven by the server response time itself. Okay. So this concludes the first step, the first demo which was about a service desk getting a call from an end user and trying to figure out what the main performance drivers are for this specific app. Let's now switch to the second use case which is about getting a look at the overall corporate sites connectivity performance to the new edge cloud infrastructure. For that I navigate to the main advanced diagnostic dashboard and I select the sites view. By default all the data are being provided for the last one day. So if I want to analyze more data I can go for example to the last 7 days. You can go up to the last 30 days if you are interested in. Here above you have the summary. So we have about 2,000 end users being monitored, connected on 90 different PoPs for an average connectivity performance on 20 3 milliseconds and an average end to end application performance of 611 milliseconds. Then I have here below a map representation of the location of these end users with the connectivity performance in terms of coloring. So blue means low latency, purple means higher latency. So that I can immediately see if certain regions in the world are being impacted by that new edge cloud infrastructure connectivity performance. I can also make the distinction between corporate sites and remote users often requested by customers. So in this case, if I switch to the sites, I see that I'm monitoring currently 3 corporate sites while I'm monitoring a lot more remote users that are obviously spread all over the world. You have then this kind of information in a table providing by default the list of corporate sites. So you see that we have a corporate site in Bangalore, Santa Clara, in Lewis and we have a bunch of remote users. In fact I have the number of users connected from corporate sites versus working remotely here. And you have the overall average POP connectivity performance as well as the packet loss between these sites and the New Edge PoPs. If I do want to understand a little bit more about how the Bangalore is being connected to the New Edge cloud infrastructure because here I see that from an average POP connectivity standpoint this is the worst performing one. I can simply click on the Bangalore side because here I see that Bangalore side is connected on 10 New Edge POP. Okay so by just clicking on Bangalore, I navigate to a more detailed view providing the list of all POPs my end users are connected to. So I see that mainly my end users are connected to 2 New Edge POP. But what here I'm interested in having a look at is the evolution of the time of this connectivity performance. And I see here that I have had some peaks of degradation. So if now I am interested in knowing more about what happened during this degradation, I can directly select this peak of network latency degradation from the widget. And you see that automatically all the data that are provided in the dashboards are updated so that I can immediately identify the PoPs to which the connectivity was degraded. So my conclusion could be that the New Edge cloud infrastructure has a problem because connecting here in my case 4 users to this nmaa2 NetScope Hub was quite degraded from a network connectivity standpoint. So my conclusion could be that this specific NetScope Hub has a problem. But the problem can also come from the local connectivity of end users or from a local ISP that is performing badly at that time. So in order to double check that, what I can do is focus my attention on this specific New Edge POP and then instead of looking at this POP in the context of the Bengalis site, just remove the filter to see whether other end users were also connected to the same NetScope POP. And this is the case here. You see that I have my corporate sites having a bad performance connecting to this NetScope POP. While I have some remote users, I have in fact 11 remote users connecting to the same POP without suffering from any kind of network connectivity degradation. So my conclusion here is that this problem does not come from the POP itself. It comes from the connectivity between the Bangalore site to the New Edge POP. So this is what now I do want to troubleshoot. So just by clicking on this, I can go and navigate to the last dashboard which is past performance which provides again the evolution of the time of the network and latency connecting this Bangalore site to this NetScope POP. But now more importantly, I discover automatically all the corresponding network path during this time frame. So I can identify each and every ISP I'm traversing. And I can also quickly identify where I have most of the delay occurring. So focusing on this peak or even on this peak because I have a bigger peak here connecting to this to this POP. So I can even go and select another peak, use it as a global range to understand exactly what happened at that time in terms of network paths being taken and in terms of delays being introduced in the path. So here you see the corresponding network path. But more importantly, you see that connecting to this Airtel ISP took from my end user device 2 48 milliseconds. So connecting to the first node which corresponds to my local ISP was really degraded and what drove in fact the overall connectivity performance to my New Edge PoP. So you see that I have an average of 250 milliseconds and in fact connecting to this new edge POP ended up being really degraded from the first hop standpoint. So in this case, the problem is either coming from this specific node from the ISP or from the local connectivity of end users to the network. So in this case, you can fall back on the user overview dashboard again, have a look at the corresponding WiFi strengths for example to assess the local connectivity of the end user devices on their network. The last use case I would like to showcase is about a more application focus analysis. So here my viewing angle will not be to start with an overview of my different corporate sites connecting to the New Edge cloud infrastructure. It will be about having a look at the different applications and understand how these applications are being delivered to my end users. So for that I can navigate to the applications dashboard. I have about 5 minutes left to quickly showcase more application centric analysis. For that, I navigate to the application main dashboard which provides an overview of all applications that I am currently monitoring as well as the main performance metrics in terms of availability of the application, the time to first byte, the server response time, as well as the number of users and site from which these applications' performance are being assessed, as well as the number of servers that are delivering the services. So you see funny to notice here that when taking Salesforce as an example you see that the server response time is nearly you know, the same as the time to first byte which is a confirmation that the overall end to end application performance is mainly driven by the server response time. Here above, by default, you have the map showing the location of the end users, showing also in the color code the application availability. So again, 100% availability here in my case so everything is green. But what is interesting in this map is that I can also switch from a more end user centric view to a more server centric view. So I can switch and here, instead of showing the location of the users, showing the location of the servers that are delivering the app. Now if I do want to have more information about a specific app, I can just click on the app name and now I navigate to a really more much more detailed view providing a lot of telemetry. First of all, the availability over time. So here I do not have any kind of problem so it's not quite interesting. But here in case of any kind of problem accessing the application, you would get all the details here. So problems can come from the server side getting 500 internal server response codes for example, but can also be related to network related issues like a TCP connection timeout or a problem during the TLS handshake process. So you would get all the details here in this widget. Then I have the overall end to end performance metrics available here as a summary. So having all the network related performance metrics between the corporate side and the end users to the NetScope PoPs in terms of DNS connection time and TLS. You have also the telemetry within the NetScope PoP itself in terms of how long it takes for the NetScope PoP to forward the network flow in and out. Into so this is what we provide in terms of transit time. And then you have also the metrics between the NetScope PoPs and the application. Connection time, TLS, server response time, as well as end to end performance metrics including the payload, the hold duration, a lot of great stuff. Now all these metrics are being delivered in context. So it means that I can distinguish between the different site, the remote users. I can also have a more country specific view and ask myself some questions like what about the worst performing country when it comes to connecting to New Edge Cloud. So here I can just sort this colon site 2 pop connection to have this information. Or I can have a more time to 1st byte so end to end performance metric related to worst performer. So in this case by sorting on the TTFB column, I see that India was the worst performer. Now I can go and ask myself a lot more questions like okay who are the servers that are delivering the service for Indian users? By selecting the country here, I have all the servers and you see that some of them are located in the US and some of them are located in India. So now if I do want to see what about the transactions that are being delivered by these servers I can just activate your URL and I have access to the transactions themselves. Going a little bit further I can see whether I have had some degradation over time. So for example, here I see that I had some site to pop degradation due to a bad DNS resolution time. If I do want to identify the server, I can just select it here in the time series. I can select it and boom you have it. So now I know that resolving this URL for this server took 2 seconds at that time. And you can ask yourself additional questions like did this affect the overall end to end performance? So here while keeping an eye on this peak, I can go to this tab end to end to see what about the TTF b. And select for example the TTF b. And you see that in fact having the DNS resolution being degraded at that time did not really from an average perspective did not really impact the overall end to end performance for this specific app. So you see how I can ask myself a lot of questions while remaining within this dashboard. And with that, it concludes the 3 use cases I do want to showcase. And I give the floor back to Priyanka to wrap up the session. Thank you very much. Thank you so much Thierry for that wonderful demo. I hope all of you got a chance to see the product in action and can see the value that it can bring for your organizations. Now, P Dev is highly differentiated. Let's talk about the unique capabilities that set it apart from the competitive offerings as well as standalone DEM solutions. The first in the lot is smart monitoring. The combination of real user experience and synthetic monitoring delivers that end to end visibility that precisely captures the end user experience. Next up is Zero Touch monitoring setup. It uses the context of the NETCO platform to reduce the administrative and operational overhead of configuring and managing your monitoring setup. Now from using the app fingerprint through our CCID to identifying the most appropriate destinations to monitor through user traffic analysis, P then truly reduces the time to task and operational costs for our customers. 3rd is site centric visibility. Now flexible monitoring capabilities for both site and user monitoring is enabled by using our innovative enterprise stations. Now these enterprise stations are site based monitoring agents that are managed entirely in the customer premises, which provide a very powerful site centric view that when combined with user monitoring, it delivers a very consistent 3 60 degree perspective of your holistic digital experience. Advanced diagnostics. Now advanced network diagnostics with a single unified view is a tremendous value for our customers. It gives you the ability to monitor and analyze data from the same interface, simplifying the amount of management and administrative overhead that would go into otherwise egressing that traffic and analyzing it. The next step is NetScope processing time. Now, PDM uses New Edge to monitor the time spent in NetScope, which reports the overall contribution of all services that are used in New Edge when processing end users traffic. Now, this is a capability that nobody else can give you, other than Netskope's DEM solution. And finally, proactive remediation. Informed by PDAM, New Edge exercises insight driven control over its device, access on ramps, client and network steering, SaaS infrastructure, and application first mile access to constantly preempt issues, consistently optimize performance, and always deliver a first rate user experience. Now proactive digital experience management. This is an automated process. It starts with high definition monitoring metrics that can be insightfully analyzed in context from location, connectivity, and applications to an individual user's behavior. That's a significant outcome for our customers. It reveals the scope, impact, and the origin of issues to accelerate root cause analysis and troubleshooting efforts. Now combine that with AI and ML based analysis to generate actionable insights to prescribe action for our customers. What that really translates into is the ability to remediate issues and proactively optimize for performance and ensure end user productivity. Finally, closing the loop real time visibility guides and confirms the outcome, ensuring that problems are conclusively resolved. By prompting user actions and extending 360 degree control over devices, SoC, connectivity, NetFlow provides a true digital experience management. This is the universe of what BDM can do. This is what digital experience management needs to be. Now with that, I'd love to take some, questions and answers. And, you know, there are quite a few that we've been answering through this session, but I'd love to answer at least one one of our questions live. I believe one of the questions that we have here is how do you integrate PDEM with existing IT operations, monitoring, and security systems? Now that's a really, really great question. Now what this shows is our customers' desire to operationalize the information that PDAM as a solution provides. Now the way we facilitate this in PDAM is by enabling our alerts framework to give our customers the ability to configure alert rules to identify the events that they choose to be notified about as and when they occur. In addition to that, what it really, where it really translates to enabling that operationalization is we provide our customers with the ability to ingest this alerts payload by using custom webhooks. Now what that enables for you is the ability to ingest this alert payload into downstream systems like ITSM or ticket management systems to ensure that you can constantly trigger the appropriate workflows or the right playbooks to address the incident or the event that has occurred and is identified using the alerts framework. In addition to that, Pdevin is an API first product. All of our capabilities have API endpoints that are available for customers to use to ingest this information and utilize for offline playbooks or workflows. That's how we actually enable our customers to utilize the information, the data that lives in PDEM to be used outside of the product in downstream IDSM or ticket management systems. That concludes our session today about proactive digital experience management enterprise. I hope you guys got a lot of information out of this session. We look forward to hearing from you. If you'd like to have a deeper dive into the product or would like to learn more about this product line, please reach out to us through your account teams. Thank you so much.