Where do you see the console.log() calls made inside of AWS Lambda functions? I looked at AWS Cloud Watch event log and didn't see them there. Is there a CLI way to see them?
Add a comment
|
2 Answers
console.log() should definitely end up in the CloudWatch logs for your function. You should be able to find the correct log group in the web console interface for your function under the Monitoring tab - Jump to Logs. Note that you will have a different log stream for each invocation of your function, and there may be a delay between logs being written and logs showing up in a stream, so be patient.
It's possible you do not have the IAM permissions to create log groups or write to log streams. Ashan has provided links on how to fix that.
Additionally, you can use the awslogs tool to list groups/streams, as well as to download or tail groups/streams:
- To list available groups:
awslogs groups - To list available streams in group
app/foo:awslogs streams app/foo - To "tail -f" all streams from a log group
app/foo:awslogs get app/foo ALL --watch
3 Comments
honkskillet
What do you men by "console interface for your function"? Do you mean the web console lamba>functions>myFunction then the section Designer? There is an item "Amazon Cloudwatch Logs" but it isn't clear where I actually see the log calls.
Eric M. Johnson
If you go to lamba>functions>myFunction>Monitoring tab, you will see lots of graphs of your function invocations. There is a link labeled "Jump to Logs" on top of each one which will take you to the CloudWatch Logs group for your function.
dlock
> you will have a different log stream for each invocation this is inaccurate. You have one log stream per container instance
Make sure you the IAM role assigned to the AWS Lambda function has permission to write to CloudWatch Logs. For more information regarding the policy refer Using Identity-Based Policies (IAM Policies)for CloudWatch Logs.
In addition, you should be able to view the CloudWatch log group by clicking on the CloudWatch Logs under Add Triggers in Lambda Console.
1 Comment
honkskillet
When I add CloudWatch Logs, then configure to add a trigger from my lambda function I get the warning: "The log group provided is reserved for the function logs of the destination function. (Service: AWSLogs; Status Code: 400; Error Code: InvalidParameterException; Request ID:1rfq4315-dfeq5"