Amazon lambda does not show python logs

Question

My API(Python) is deployed on Amazon Lambda. The problem is when I request my API I get the internal server error. I can tail the Lambda logs but I don't see the actual error or stack trace where the code crashed. When I tail the logs I just get the following output.

START RequestId: 62341bgd-6231-11e8-8c5b-25793532a32u Version: $LATEST
END RequestId: 62341b0d-6231-1128-8r5b-2b793032a3ed
REPORT RequestId: 6234te0b-6rte-aaa8-au5a-21t93132r3rt  Duration: 0.46 ms

How can I see the actual stack trace of my python api for debugging?

cannot, did you have any logging operation ? Which app taking watchdog job ? — dsgdfg
– dsgdfg, Commented Jun 13, 2018 at 11:11

FelixEnescu · Accepted Answer · 2018-06-13 12:35:32Z

3

Lambda always tries to write the Python stack trace to CloudWatch. Make sure your function has the required permissions:

    {
        "Effect": "Allow",
        "Action": [
            "logs:CreateLogStream",
            "logs:PutLogEvents"
        ],
        "Resource": "arn:aws:logs:eu-west-1:123456789012:*"
    },
    {
        "Effect": "Allow",
        "Action": "logs:CreateLogGroup",
        "Resource": "*"
    }

answered Jun 13, 2018 at 12:35

FelixEnescu

5,2122 gold badges35 silver badges34 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

singh30 · Accepted Answer · 2018-06-14 16:59:53Z

2

If you are using Lambda_basic_execution role, simple print in python will show logs in cloudwatch.

answered Jun 14, 2018 at 16:59

singh30

1,51318 silver badges22 bronze badges

2 Comments

Steve Over a year ago

That definitely does work with print statements, but why wouldn't log.info for instance work the same way?

hlesnt395 Over a year ago

I see this is a bit old thread. But just leaving a comment here, as I encountered the same problem yet using Python 3.9. When using Lambda, you have to use logger.setLevel(logging.INFO). It does not work with logging.basicConfig(level=logging.INFO)

Naeem · Accepted Answer · 2021-08-16 19:18:13Z

1

my logs were enabled but still it didnt printed anything, it also didnt show added log in CloudWatch. but when I commented a print statement which was trying to print too much data from dynamo db, it started working again so maybe somewhere else in your code you used print to print huge data so disable it

you cant print too much data or it will neither print anything in test nor will it add log in CloudWatch

edited Aug 16, 2021 at 19:18

answered Aug 16, 2021 at 19:07

Naeem

691 silver badge7 bronze badges

Comments

hlesnt395 · Accepted Answer · 2022-07-26 09:22:04Z

1

I see this is a bit old question. But just leaving a comment here, as I encountered the same problem yet using Python 3.9. And this how I solved the problem. When using Lambda, use:

logger = logging.getLogger()
logger.setLevel(logging.INFO)

It does not work when using:

logger = logging.getLogger()
logging.basicConfig(level=logging.INFO)

answered Jul 26, 2022 at 9:22

hlesnt395

8231 gold badge17 silver badges37 bronze badges

1 Comment

leafmeal Sep 9 at 20:04

This worked for me, but only when copying it exactly. Originally I tried logging.getLogger(__name__) but this did not work.

Kyrylo Kravets · Accepted Answer · 2023-10-17 08:21:37Z

1

You may use built-in logger in case your logging does not require customization. This approach allows you to get messages logged to CloudWatch every single time.

def lambda_handler(event, context):
    ...
    context.log("Hello world")

answered Oct 17, 2023 at 8:21

Kyrylo Kravets

5636 silver badges12 bronze badges

Comments

Hassan Abbas · Accepted Answer · 2018-06-15 09:37:26Z

0

Initial Investigation:

By default lambda function created log group in CloudWatch by the name of my API. For example, /aws/lambda/my_api_name which shows the output something like this.

START RequestId: 62341bgd-6231-11e8-8c5b-25793532a32u Version: $LATEST
END RequestId: 62341b0d-6231-1128-8r5b-2b793032a3ed
REPORT RequestId: 6234te0b-6rte-aaa8-au5a-21t93132r3rt  Duration: 0.46 ms

Problem Resolution:

I created a service role for my cloud watch(Default policy for all the rights for the cloudWatch already provided by AWS) and then put this role into my API. I followed this approach. However, another step could be combine the newly created execution logs with the default one so we have one log group to tail.

answered Jun 15, 2018 at 9:37

Hassan Abbas

1,3161 gold badge22 silver badges50 bronze badges

Collectives™ on Stack Overflow

Amazon lambda does not show python logs

6 Answers 6

Comments

2 Comments

Comments

1 Comment

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

Comments

2 Comments

Comments

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related