Okay, in the last lecture we briefly talked about lambda and its working style and functionality. In this lecture, we are going to know more about one of the properties called context and context. It gets you every detail context, it's as simple context in which context in on what context Islam is running. So, context gives you a little bit more details about this lambda is running out, we are also going to add a weight keyword with the response this time and this is an same request. And now we are going to examine context. Briefly, context gives you a couple of more information about context this lambda is running with so you can get to know more about law group name.
This is this has to do with a two cloudwatch logs stream you can get to know AWS request ID and this request ID is you know, independent and specific to a particular request itself so you can dig down and you can get all the details you need. You can also get to know the invoke ID, Aaron etc, etc. As you know, AWS resources have their specific and separate area. Now we are going to examine the logs and logs we can find cloud watch feature of AWS a couple of different options under cloud watch, you can see events, logs metrics, you can drill down in your time, and you can see all the details about cloud watch and everything. You can see metrics and the metrics actually gives you all the details about All resources, you can find more information about your specific lambda functions here. logs gives you information about locks, specific log sense and log specific direct quest ID that we saw, sometimes back.
And you can really turn all those details in the locks itself. Of course, you can go to different cloud watch functionalities and resource wise like lambda API gateway dynamodb. So what we are going to examine more is kind of a specific lot. So let's go to cloud watch again. And what we want to examine this time is we want to examine a specific lock on this occasion. So let's let's go to locks and of course with All AWS request ID come in with every context.
So if you go and examine this ad inventory logs, you will will actually see all the logs by request ID. So eight E, find a four, they're all independent request ID with the specific lambda. And the same ID the same request ID you will get to see and if you are capturing all those details, somewhere, you can get to know everything. You don't have to capture all the details because cloud watch does all the heavy lifting for us. So here is the request ID is coming up. And that is all about cloud watch.
Event lambda. Another thing