feat: add aws_event and aws_context to each log if the configuration …

…enable it

packages/infra/aws/log-request/ServerlessLogRequest.ts

@@ -50,7 +50,6 @@ export class ServerlessLogRequest {
 
     if (logEnd) {
       if ($ctx.response.statusCode >= 400) {
-        console.log("===>", $ctx.error)
         $ctx.logger.error({
           event: "request.end",
           status: $ctx.response.statusCode,
@@ -118,7 +117,9 @@ export class ServerlessLogRequest {
       headers: request.headers,
       body: request.body,
       query: request.query,
-      params: request.params
+      params: request.params,
+      aws_event: ctx.event,
+      aws_context: ctx.context
     }
   }
 

packages/lambda/src/auth/handler.ts

@@ -7,6 +7,10 @@ import { PlatformServerless } from "@tsed/platform-serverless"
 // shared configuration
 const config = {
   envs: process.env,
+  logger: {
+    level: "info" as never,
+    requestFields: ["reqId", "method", "url", "duration", "route", "aws_event", "aws_context"]
+  },
   auth: {
     // Not applicable here because lambda are packaged and deployed on AWS.
     // For this reason, we can't use the file system to store data (prefer S3, DynamoDB, etc.)

packages/lambda/src/timeslots/handler.ts

@@ -11,7 +11,8 @@ const config = {
   envs: process.env,
   lambda: [TimeslotsController],
   logger: {
-    level: "info" as never
+    level: "info" as never,
+    requestFields: ["reqId", "method", "url", "duration", "route", "aws_event", "aws_context"]
   },
   timeslots: {
     // Not applicable here because lambda are packaged and deployed on AWS.