Lambda Runtime Tracing

We've actually done a couple of different approaches to this. We started with something that was very close to tracing where, you know, every function invocation had the name and the input arguments and the output arguments. And so when one dot net function in books another dot netfunction in a lambda, then we want a lot of that same information so that we know where time is being spent. So you're like approaching profiling. With a whole lot of events, but you can get super granular information on where time is spent. Yep. I think that's a pretty fair description.