Mock Lambda Test Tool - Set Logging Level

[mleziva]

Hi, how do I set the logging level for the mock test tool. I see when it loads it in my windows CMD window:

AWS .NET Core 6.0 Mock Lambda Test Tool (0.13.0)
Log level loaded: Information

I would like to set the level to debug instead of information.

[ashishdhingra]

@mleziva Thanks for opening discussion. Please refer to Lambda function logging in C#. The environment variable AWS_LAMBDA_HANDLER_LOG_LEVEL could be used to to set logging levels. If you need Lambda JSON event and response to be written to the CloudWatch Log stream, you may use environment variable LAMBDA_NET_SERIALIZER_DEBUG set to true.

From https://github.com/aws/aws-lambda-dotnet/tree/master/Tools/LambdaTestTool,

• For development time environment variables, you would need to set this in launchSettings.json. To do this, open the launchSettings.json file from under the Properties folder in the Solution Explorer. Then add the environmentVariables JSON property:

{
  "profiles": {
    "Mock Lambda Test Tool": {
      "commandName": "Executable",
      "commandLineArgs": "--port 5050",
      "workingDirectory": ".\\bin\\$(Configuration)\\net6.0",
      "executablePath": "%USERPROFILE%\\.dotnet\\tools\\dotnet-lambda-test-tool-6.0.exe",
      "environmentVariables": {
        "AWS_LAMBDA_HANDLER_LOG_LEVEL": "Debug",
        "LAMBDA_NET_SERIALIZER_DEBUG": "true"
      }
    }
  }
}

• For deployment time environment variables, you could set it as semi-colon ; separated escaped list of name-value pairs as value for environment-variables property as shown below:

{
  "Information": [
    "This file provides default values for the deployment wizard inside Visual Studio and the AWS Lambda commands added to the .NET Core CLI.",
    "To learn more about the Lambda commands with the .NET Core CLI execute the following command at the command line in the project root directory.",
    "dotnet lambda help",
    "All the command line options for the Lambda command can be specified in this file."
  ],
  "profile": "default",
  "region": "us-east-1",
  "configuration": "Release",
  "function-architecture": "x86_64",
  "function-runtime": "dotnet6",
  "function-memory-size": 256,
  "function-timeout": 30,
  "function-handler": "<<some-handler>>",
  "environment-variables": "\"AWS_LAMBDA_HANDLER_LOG_LEVEL\"=\"Debug\";\"LAMBDA_NET_SERIALIZER_DEBUG\"=\"true\""
}

Please let me know if this works for you.

Thanks,
Ashish

[mleziva]

Hi Ashish, thanks for the quick reply. Unfortunately, that did not work for my local debugging environment.

The output in the cmd window still returns the below

Log level loaded: Information

I can see the Log Output in the test function window is also only returning informational logging, not debug level

Here is my launchsettings.json

{
  "profiles": {
    "Mock Lambda Test Tool": {
      "commandName": "Executable",
      "commandLineArgs": "--port 5050",
      "workingDirectory": ".\\bin\\$(Configuration)\\net6.0",
      "executablePath": "%USERPROFILE%\\.dotnet\\tools\\dotnet-lambda-test-tool-6.0.exe",
      "environmentVariables": {
        "AWS_LAMBDA_HANDLER_LOG_LEVEL": "Debug"
      }
    }
  }
}

[ashishdhingra]

Hi Ashish, thanks for the quick reply. Unfortunately, that did not work for my local debugging environment.

The output in the cmd window still returns the below

Log level loaded: Information

@mleziva Somehow, I do not see the line Log level loaded: Information in command window when I launch the test tool. Please share the below details:

• Environment details (like OS, etc.)
• Project Details
  • Simple Lambda function or Serverless project, etc.
  • Target .NET version
  • Sample code solution
• Are you using context.Logger.LogDebug() to emit debugging statements?

Also Lambda function logging in C# states that the environment variable AWS_LAMBDA_HANDLER_LOG_LEVEL controls logging level to CloudWatch, so unsure if it will work for local test tool debugging.

Thanks,
Ashish

[mleziva]

Hi Ashish,

Thanks for pointing me in the right direction. I didn't realize the log level loaded output was part of this project, not the Mock Lambda Test Tool. This project is using Microsoft.Extensions.Logging and was setting the default log level in appsettings.json. I just needed to update what was specified there and now I see that debug logs are appearing as required.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.