hi everyone thank you so much for taking the time to watch this video that I've prepared today on how to get set up with event management my name is Emily Walker and I'm one of our solution Consultants here at servicenow I've been with the company a little over a year and a half but before joining service now I spent the first 13 years of my career in corporate I.T I'm really excited to share today's content with you especially around the event management side of the house because this is really where a lot of stress can come from outages on our most critical systems and so today I want to talk through how you and your teams can get started with event management which falls under our item it operations management Health side of the house just a friendly reminder that today's presentation may contain forward-looking statements that are based on the beliefs of servicenow and should not be used in making purchasing decisions but with that we will be sticking to what is currently released and I'll be talking through some of the new capabilities that were released in our Tokyo family release as many of you know servicenow does two family releases each year and Tokyo was our most current release in the fall of 2022 so we'll cover some of those exciting features that pertain to event management okay so what are we going to be accomplishing today the first is really how to get started with event management so whether you have made the investment or you're just getting started on your implementation or maybe you got going but ended up getting stuck or maybe some of you are here to learn more about event management before making this investment secondly we'll cover all of the key Concepts and skills needed to be successful with your implementation in the case that some of you are going to be the event admins will also be discussing what are the things that you need to do technically to be able to work with the platform and fill this role successfully and lastly I'll be covering best practices throughout our presentation and share additional resources that will help you in your event management Journey since this video is recorded really the best way to get those resources is to reach out to your servicenow account team so for the agenda today we will start with an overview of event management what it does and what value it can provide to your organizations this section is really for the folks tuning in that are here to learn more and then we'll also talk about the training path that we recommend for anyone who is really going to have an active role in your organization's event management we'll also talk through the configuration both from a manual perspective and using the guided setup during this time I'll also be switching back and forth from the slides to My Demo instance tape things engaging and show you really exactly uh what we're talking about in the slides and how that looks Within servicenow and lastly we will wrap up sharing some additional resources and takeaways from today and again if you would like these resources please make sure that you reach out to your servicenow account team okay so event management what it does let's first start with servicenow's approach to event management and it operations management Health overall event management starts with helping our it operations folks handle that an overwhelming amount of alerts that they are receiving from all of their various monitoring tools and then aggregating that data to really make it more manageable and actionable rather than spending time sorting through data that is not quickly helping them to determine that root cause and really that's so important because quickly determining a root cause helps us restore Services more quickly as well so our Focus here is to number one bring in all of that data from your existing monitoring tools and then two and I think more importantly is aggregate it and make it all manageable and actionable by the time it reaches your operators and this saves us at a tremendous amount of times that our team would normally spend aside frame log data and really trying to make sense of what events have come in from our existing monitoring tools and that's really the goal here is that we want to be able to quickly get to the big picture of what's happening in our environment and have the ability to remediate it the next part of event management is to drive attention to the areas that are most critical we have to prioritize connecting that monitoring data back to the service level and we look at it for when we look at it from this perspective of what's important and what matters most what's the business criticality of these services that we've set up and defined with service mapping you can look at this from both the end user perspective and the customer perspective maybe some of these services are internal to your own employees and maybe some are external to your customers so as you're really getting set up with event management it's important to ask what are these what are the most important services that we have that I need to Monitor and manage what services affect our user experience and our Revenue and really what's the overall status of our most critical Business Services across our organization I'm going to go ahead and build this slide out here understanding uh what all of this data is and means is really one part of the equation but the other part of the equation is being able to take action as these events arise and the best way you can provide action is through our automated workflows maybe something like explaining disk space or restarting a virtual machine we really want these workflows at the fingertips of your operation your operations teams so they can take relevant courses of action to solve the problem at hand having remediation workflows really helps to give our operators for event management the tools that they need for Success within one platform and over time as the operations teams find those automated workflows that best remediate for specific events these workflows really start to prove themselves so from there we can actually start to configure the system to run those workflows automatically and immediately upon alert generation so we no longer have to wait for that humor and interaction anymore we can start to let the system help us by setting up specific alert criteria and we'll look at how to do that here later on in our presentation and then the last piece of this cycle here showcases continuous Improvement so as this knowledge accumulates over time not only is it the operations teams that are learning to leverage the system and these workflows but the system is actually learning from itself it's detecting which remediations and works workflows or most successful and where our teams are learning the system and the system is learning your environment and this is really what helps us lead to more of a proactive and intelligent remediation and more success for your teams on the platform let's stop through ingesting events and pulling in as much data from your environment as we can so as you can see here we work with many great Partners to invest or to ingest this event data into service now and these can be a combination of push and pull connectors that come out of the box with event management but doing this gives us really a way to easily connect all of this data and in turn that helps us so we can get a clear correct thorough vision of really what's happening in our organization from a monitoring perspective so how do we pull this data in we can do this a few different ways uh so the first one is that we can ingest data from your existing third-party monitoring tools into servicenow via these pre-built connectors and a mid server so maybe that scom or solarwinds or xavix we have a large number of out of the box push and pull connectors able um to be used within event management we also have connectors available from the servicenow store as well as third parties so you can create these custom connectors or you can create custom connectors or Additionally you can also use the agent client collector for monitoring which is a servicenow's agent based tool so lots of different options here when it comes to connecting your monitoring data to servicenow's event management solution regardless of which method you choose as this data is coming into your instance it's being normalized so that we can sift out any redundant or unnecessary messages and this helps us have more of that digestible number of events and actionable alerts another great feature here is that these alerts are also bound to their relevant CIS or configuration items that are found in our cmdb this helps us to give more relevant and relationship information from the service level which becomes incredibly important for troubleshooting so if we received an event from a server that's part of a critical Business Service event management is taking that business criticality into account and prioritizing the alert based upon that priority so the relationship information that we get from those CIS is incredibly important and this is really how we're able to pull everything together to deliver the vision of being being able to quickly get to that big picture of what's happening in our environment how critical it is and the ability to remediate it all within one platform Okay so we've talked a little bit about noise reduction already but let's keep driving home the importance of this and this is really such a big benefit when it comes to managing events a lot of customers come to us specifically for the correlation uh features and solution within event management and a lot of times what we hear is that our operators spend numerous amounts of time sifting through events and that's really essentially money lost in time and service outages so when we're talking about core leaving alerts we use four different types of alert correlation and these are what really help us to be able to group uh alerts together and have that noise reduction we understand also that all not all alerts coming in are going to be Standalone alerts a lot of them are going to be part of a larger issue and correlate back to one another so let's talk through the four different types of alert correlations the first one that we have is called temporal analysis and this is the first type of correlation the system uses and you can think of this one as the AI and the Machine learning that we're leveraging in the background to find these patterns that have come in over time and we're looking at historically uh we're looking at them historically and then grouping logically grouping the alerts that are telling those same stories the second one here topological analysis is when the cmdb comes into play so here we're using CI based patterns and you can think causal relationships so for example if a server goes down it would look at all the other CIS out there that rely on that server and create an alert based upon that versus say if there were 15 other Ci's that were dependent on that server creating an alert for each one of those CIS so it looks at the relationships of the CIS and consolidates the alerts together and then the last two on this side um are more on The Human Side here so we have human defined and this is where we're talking about your teams you have a great team and you want to leverage that human expertise from your teams so here you can take that knowledge and input it into the system and have logical groupings based on a specific environment things they've seen over time so the system can really learn from their experience and take that into account and then the last piece that we have here semi-supervised learning this is where we're really just saying that any technique can always be fine-tuned by someone on your team who can identify when an alert may have been added to the wrong group or a group was not recognized so if someone is noticing that the correlation taking place isn't exactly right we can always go in and fine-tune things up a bit and the benefit really of tuning is that it feeds the machine learning to continuously improve for future performance which is great because we're always wanting our instance to gain more intelligence and learn exactly how we want things set up thank you all right let's switch and and talk about some of the resources that we recommend to help you with your event management Journey we highly recommend that you or your event management administrators take some form of event management training through servicenow so whether that is our self-based course our instructor-led course either one I've personally taken the instructor-led two-day course and I found that very helpful it was a combination of instruction and labs and our instructor who was actually also a servicenow employee even gave us some small group work to do together which kept things really engaging and then Interactive the other great part is that we see a lot of our partners and customers in these classes too so I highly recommend taking it if you have the time you can also find um you can find these when you go to our now learning site that's where you can register and it's just now learning.servicenow.com and then search for event management fundamentals we are now going to spend some time talking through the manual configuration steps and then later I will show you uh sub steps for using the guided setup feature so the manual configuration route this really kind of breaks down into six high-level configuration steps that will go through in more detail but it really starts with activating them at management plugin by submitting a request via the now support portal once you have uh once you've activated your event management plugin you really need to make sure that you have a validated mid server installed and active and this step is critical because this is going to be what's pulling that monitoring data back into servicenow so if you have the resources we also recommend dedicating a mid server or midservers for event management we also recommend if possible deploying that mid server on a Windows or Linux typically the windows will gather all of the Ci's uh versus Linux for it can only gather Linux CI so we would kind of recommend in that case where you would need all um configuration items pulled in to look at putting it on a Windows machine and you may actually already have done this step or gone through the mid server setup if your teams are using any other parts of item discovery like uh the agent client collector or Discovery or any other use cases for having a mid server so once you have your plugin activated and your mid server deployed and validated that's really when we can move into step three and this is where we're going to reach back out to your existing monitoring tools and push or pull that data into servicenow and you'll do this through either our out of the box connectors or custom connectors when first starting out we do recommend leveraging the out-of-box connectors if possible you can find these connectors on our product documentation page so if you go to docs docs.servicenow.com and then search event management connectors here's where you'll be able to see exactly what monitoring tools we support out of the box the second point to this slide is to make sure that you really get the right teams involved when you're connecting this event data back um from your monitoring tools because you're going to need those connection parameters and credentials and not only that but maybe the monitoring team has more tools than you actually knew about so it's really important that your teams are capturing everything and working together to really build this out and once you have that event data coming into servicenow via those connectors this is where you really want to start setting up some different rules for what these events and alerts are going to be looking like so the first set of event rules this is basically where we are defining if and when an event should be escalated into an alert on the operator workspace or in our new service operations portal on the service dashboard you would get a chance uh I'll get a chance to show you this when we switch over to the demo portion but our service operations workspace was part of our workspaces releases um later or earlier in the year but with our event management rules there are a couple different ways you can do this such as defining thresholds and you can use CI based alerts this is contributing to really that noise reduction benefit that we keep emphasizing and here again another best practice we do recommend leveraging those out of the box rule event rules to start one more thing that I want to point out here is that from now on as of our Tokyo family release event rules will support executing multiple event rules on the same event this change really came about to help give customers more flexibility for example when we get into the event rules the transform and compose section is where we'll see it shortly but um sometimes include more General parts that you and your teens might want to reuse for other of that roles so this is one of our new Tokyo release features so once we've defined uh what events to generate an alert we want to define the specifics of what alerts actually do and here's where we're really starting to Leverage The workflow automation capabilities of servicenow so maybe actions such as automatically generating an incident for specific alerts or automatically kicking off remediation workflows depending on the criteria of that alert and maybe even without human interaction so just like the event rules alert management rules have some out of the box options to support as you're getting started here's where I'm going to call out another great Tokyo release feature and that is scaling out alert management rules previously before our Tokyo release there was really only one job that could take care of processing alert management roles so if you've got a lot of alert management rules that need to be processed it could end up causing a bit of a backup and cueing so that was addressed in the Tokyo release and now we have the capability to have more multiple jobs that are going to be taking care of that as your alert rules scale efficiently okay and for detailed instructions on rule creation you can also go to our product doc site again docs servicenow.com and search for create or edit an event Rule and create an alert management role and lastly our sixth step alert correlation rules and maintenance rules so so far we've defined what generates an alert and what happens when those alerts are generated but now we need to Define our alert correlation rules which allow you to Define how alerts are related and how they're grouped together into primary and secondary alerts so maybe a good example of this is if you have a server in your organization and it goes offline you don't need to see additional alerts to show that the virtual machines or applications running on those servers are also down instead those additional alerts are secondary alerts and they're grouped under the primary alert we also need to set up maintenance rules which simply set specific CIS if they are in a maintenance status and this is where it helps us to prevent those false alerts or unnecessary alarms in our operations workspace or service operations dashboard if something is resulting from maintenance or versus actually being down and by default an ECI that has an active change window is automatically marked as being in a maintenance mode and this is another great reason of why having it service management teams and our it operations teams working within the service operations workspace and on the same platform so beneficial all right let's jump in to the demo so the first place that I am showing you here is our event management overview dashboard and this module uses performance analytics to present data within this dashboard for you to better visualize and understand your processes and drive that continual Improvement so here we're looking at the event management overview dashboard and this is all out of the box really the only thing I did here um was I moved my widgets around but this dashboard includes uh the capabilities and functions here where you can add new widgets so you can come in here and look for other performance analytics widgets that are available the other options that you have here are you can actually share this out to specific groups and users and roles or you can come in here and kind of customize this and configure this a little bit more so however you want to kind of group these alerts together is completely up to you the other place where all of this data comes together for your operators to use is in our operator workspace and I'll show that just briefly um but where I really want to focus is on our new service operations workspace and specifically the service dashboard so first this is our operator workspace view so if you've ever seen event management prior to the Tokyo release this is most likely what you are looking at but when our workspaces were developed this is our service operations workspace and here is where we really have the ability to have this configurable workspace for not only our operations teams but our service desk teams giving them the ability to collaborate and work together on all of these critical events that come in so you can see the same detail here that we had seen in our operator workspace different UI a little bit more modern and advanced but kind of the same thing here is when we come into our operator workspace we first notice that we have a lot of our services that we have mapped and put into an operational state from service mapping um here and then they have this color coding based upon the severity breakdown so our order status is showing us that we have a critical outage happening um the other thing that we can do here we can group these by uh severity by business criticality location lots of customizable ways to view the data here from this workspace we can also come over here and we can actually filter Services by alert so looking at the most critical alerts first let's go back in to our event management we're going to start really when we're talking about getting this set up the first thing that we're going to do is going to our connector definitions so event management again provides many connectors to either push or pull events from external devices connectors you can find those again from the store as well as those third parties and you can also create those custom connectors but this is the table that lists the connectors that are provided out of the box with event management so I'm going to open up solarwinds and show you this one and these are templates and funnels that establish that connection um the schedules and then the connector instance is where we're actually going to set up um down here sorry the connector instance is where we're actually going to set up and make sure that we have those events being pulled in on a specific schedule okay and so let's first go into our connector instance here and what we have this really helps us to make sure that we are scheduling the frequency of the event and also making that connection so one of the first things that you're going to do before marking this active is going in and setting up your host IP of where you want to connect and then the credentials um so for this one I had to actually go in and make um new a new credentials set you can also come down here and you're going to want to make sure that you give this a mid-server that you've already probably set up within somewhere close to that environment that has that reachable IP once you have that done you can come into test connection and this is pretty quick so it shouldn't take that long I tested this yesterday there we go um so now we really have all of those alert or sorry those events being able to come into our servicenow instance so the next spot that we're going to go once we have our connector definition and our connector instance set up and tested is into our all events so we're going to click into one of these I'm going to do some filtering here for just a minute I'm going to take off um let's go up here and right now I'm looking at events that were created today but I also want to filter out one of the sources I'm going to filter out this em I'm going to say is not em self monitoring um and the EM self monitoring is really our event management self-monitoring tool that helps to let you know if there is something wrong with event management itself um so right now what we're looking at when we come through this window is we have all of our events um the time of the events the source so I have a few different sources here I can group uh by source and I can actually see that I have um our Icom agents or agent client collector um I have some scum I have some be realized uh zabets dynatrace I have all of my sources I'm going to ungroup that though so I can kind of walk through this a little bit more the other part that we're able to see here is our description uh so kind of a high level idea of what could potentially be happening on this the node so which uh configuration item in our cmdb is this event um going back and binding too if it can find it we also have the type here so maybe it's giving you some more information about that specific event that's happening and if we come over here again resource similar to node um just a different way of saying which configuration item we're actually looking at we also have the state of what the state of that event is so has it been processed is it waiting to be processed and then the severity if an alert has already been assigned to it you would actually go in and you could see that alert right here let's go in and we're going to click in on one of these so let's click in on this one and so once an event is processed that basically means that some sort of first level filtering has already been applied and it's compared data to the Raw event to the event rules to determine if that criteria has been met to actually generate an alert so we'll see those event rules shortly but this is really where we're going to be able to see that noise reduction taking place by turning those events into alerts so when we get to that service operations workspace or our operator workspace we aren't seeing every single event we're only seeing those alerts that have been grouped together so I want to call out a few things here again kind of the same um data that we were getting before from that other View but the couple's points um or areas that I want to point out here are the first one is processing notes so here we can really see what logic was taking place and how that became an alert and then the other one to point out is additional information so this is where any raw data that isn't explicitly mapped to a defined field from that third-party tool is stored and this is important because we don't really want to get rid of that data maybe some of it's important and at some point we would want to map that to a field um but we need a place to put it so we put it in this box and this can actually help us to highlight maybe different Trends or patterns and then over time you can start to customize your event rules based on this data so it's important that we keep it all right the other place from here is let's move into our event rules this is where we're actually going to be able to see all of the event rules that are helping us to classify those events to an alert and actually make them available in our operator workspace or service operations workspace we had a lot of these pre-built out of the box rules here and I'm gonna filter this on source with the source being debits all right and with these pre-built rules that are available you're able to tune or activate or turn on for your specific environment as each of them apply the one that we are going to look at right now we're going to take a look at the savix metric CPU and we can click into any one of these and it's the same interface that we would be having um if we were creating our own custom event rule but we're going to stick with the out of the box rules and accordingly My Demo and since decides to come back let's give it a little refresh okay there we go so we have our zabets metric CPU event Rule and here we see the name we see the source and Order um so if you have any of those other event rules they're going to be processed in that order remember higher the number lower the or lower the number higher the priority here with servicenow um and then so we can walk through this wizard here to kind of help us set up this event rule the next spot we're going to go to is event filter and here's where we're qualifying all of the events coming in from zavex which of those events are coming in which should be an alert and here you can also create specific ignore rules as well but the logic we're seeing here is that if an event is dealing with CPU it's probably important enough to be an alert that is seen in our workspaces so you can also add new Expressions so whether those are from a pattern or a rejects over here we're really starting to be able to customize our alerts to cater to what our teams want here the next part is our transform and compose alert output and here is where we have a preview of how that expected raw data looks for the event that we are specifying and how that raw data is mapped to the desired Fields this is very similar to the event form uh that we just looked at and we can actually see here from this other side we can just drag these are these different data points and if we wanted to add anything else okay the next threshold so this is um not active out of the box but here's where we're setting a threshold if we needed uh maybe we only want these um alerts or these events to become alerts if this event is happening within a specific time frame and again these are fully customizable and then the last piece here is binding so we typically recommend leaving this alone as much as possible this is basically the logic that's associating the different data points that you're bringing in with these types of events to the related configuration items in your cmdb okay let's go back and if you look up here at the top this calculated uh calculating groups it turned it over and so what we have here is this smart little Banner at the top telling us that there are some recommended rules that are being recommended based on our environment using machine learning so it's looking at the events and it's seen actually there we go and it's seen what trends and what event data might help us with noise reduction and to help make alert management um even more efficient or event management even more efficient um so this can be a really great starting place if you aren't sure where to start you can use machine learning to help let's switch over into all alerts sorry our alert management rules and here's where we're able to use uh action and automation that um on those events that we have just kind of walked through the event management rules on and this is really the part that we're going to be able to do those remediations and avoid outages much quicker upon the dollar generation so the one we're going to walk through today is create creating an alert on uh sorry an incident on a primary alert so we can come down here create incident on primary critical alert actually we're going to go create incident on primary okay now that we are in our alert management rule for creating an incident on the primary let's walk through a couple of things here um the first one is we're gonna click through and walk through the steps here and again you know automation can sometimes be a little scary at first depending on what it could be doing in our environment so starting small with something like creating an incident um on an alert is really a great starting place here and so we have the name we can see that it's active we can also see any alert executions that have already that this is already run on so we can actually open up flow designer we see here that all of these actions are being done by flow designer so I already have this open uh but what it looks like is we're running through these series of actions and uh progressing to see you know is this alert classification is it a security incident um if it's not okay then we're gonna go ahead and check to see if it's in maintenance mode we're going to look up a record we're gonna follow all of these steps that are part of that automation workflow the other parts that we have here that we can walk through are our alert filter so if we have any alert criteria here's where we can set it and this is similar to the event rules that we saw earlier and then actions here's again kind of exactly I know I showed the flow designer flow a little bit ago but here is uh the actual link to that flow um going back we would just see all the executions that had been already taken place um and so this is where we're really able to create those specific reading remediations using flow designer okay let's switch back in to our presentation give me just a second thank you so now we are gonna go into our guided setup features Within servicenow and the guided setup is a really great option if you're looking to accelerate the setup of event management um these guided setups were a way to really give you kind of a UI that helps you be able to see the value faster and start really taking actions um that are appropriate for implementation here this is a great way if you are not working with a partner or if you're doing self-implementation or maybe you're setting this up in a Dev environment or a sub-production environment to test it out so the guided setup is really a facilitated UI that helps give you the exact steps one by one and really hand holds you through this process and this can be such a big benefit if you are newer to servicenow or maybe have a little less experience on the platform and want some assistance with getting started so during the guided setup um you'll really get to set up using the best practices that are out of the box for all the things that are green here listed on that slide there are a couple of technical prereqs even if you are using the guided setup and this will look pretty familiar from the manual setup steps same first three steps as last time when we were looking on the manual side but that includes activating the event management plug-in installing and configuring your mid server and finally configuring that Event Source connector so we will walk through these um in just a few minutes on my demo instance here on this side we've mentioned a few different times throughout the day that you really want to work with your teams and be collaborative when you're deploying event management even if you've already started to deploy event management it's really never too late to Loop in those other teams and really make this a collaborative effort there are probably teams throughout your organization that can really benefit from event management and maybe they haven't been thought of um so you're going to be really working with your teams to understand what alerts are coming in and what of these alerts or what of these events should be escalated to an alert so making sure that they're aware and making sure that you're working with the right team to get the right access you need so again just really being as collaborative as possible to see the most success as you get up and running with event management okay let's switch in to My Demo instance and here we have our it operations management guided setup and I found that just by typing an item guided and from this first window we're gonna see down here we have our maturity model so we're looking at kind of this pyramid of how itom gets implemented and really starting with more of the discovery side or starting on the itsm side with incident problem change and our cmdb and then from there we're moving into more of that availability and then from there uh the agility side of the house so let's go back up here to continue where we can actually get started and we're gonna see here really how we break down uh the setups per specific solution within itom so first we have our bid server and that's really regardless of if you're doing Discovery or service mapping or event management this is really the starting place of where you want to go is getting those mid servers set up so you can actually come in here and click in these tasks some of this when you click configure will either take you to a product doc site with instructions on how to do it or it will take you actually to the window here within the portal where you can actually do the configurations so let's go back and we're going to go down to event management and we can see when we open this up really we kind of break these into chapters of what work is going to be needing to be done so the first one we have our event sources and properties the next we have event rules and then knowledge tasks and automation so similar to what we walked through on the manual side but here we're just having this more structured in a UI that your teams can work through here in the guided setup the other thing to point out is that you can actually assign specific tasks out to your team members so maybe this isn't one single person that's doing your implementation maybe you have a whole team that's helping through this so you can actually go in and assign out these specific tasks but what we're looking at here under properties um for the event sources we're looking at properties enabling event management the self-event management healing property so you can come in here and actually configure that directly within here and so on connectors if we wanted to add any listeners maybe for a web service on a mid-server or an SNMP trap or email listeners we can do all of that here as well so just clicking through each of these different steps and we are starting to wrap up but before we completely wrap up I want to go over our key takeaways from today so we set up event management and we got those monitoring tools connected whether your teams really choose to do this manually or through that guided setup we've pretty much covered it today and really we've helped to establish those proactive rules that help the noise with noise reduction and automatically remedy eating events and lastly there are some additional resources that will be really beneficial as you go through your event management Journey so first we have our servicenow item Health overview and our event management product documentation and these will be really great for getting started beyond what we've covered today if you want to take a deeper dive here is um the link for aiops and visibility Dummies book and this ebook covers everything from the introduction to AI Ops to use cases and how we can deliver apps with servicenow the next one is we have our white paper for item Health performance and this includes test cases not only for event management but also for health log analytics which is an add-on to our item health or part of our aaps Enterprise package and lastly regardless of which part of the platform you're focused on is our now Community with different forums for each area of the platform and our customer success Center so again if you're watching this recording and you don't have access to click these hyperlinks please make sure that you reach out to your servers now account team and ask them for this slide deck and with that that wraps up today's presentation I hope that all of you have found this information helpful um that was presented and that you were able to gain more of an understanding on really what it takes to be successful with servicenows event management again I'm Emily Walker and thank you for your time today