# Dynatrace does not ingest logs (HTTP 429)

**URL:** <https://community.dynatrace.com/t/dynatrace-does-not-ingest-logs-http-429/42972>\
**Category:** Troubleshooting\
**Tags:** aws, log-monitoring-class, lambda\
**Created:** [December 4, 2023, 12:51pm UTC](https://community.dynatrace.com/t/dynatrace-does-not-ingest-logs-http-429/42972 "2023-12-04T12:51:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![virgi-df](https://avatars.discourse-cdn.com/v4/letter/v/439d5e/32.png) [@virgi-df](https://community.dynatrace.com/u/virgi-df)\
**Post date:** [December 4, 2023, 12:51pm UTC](https://community.dynatrace.com/t/dynatrace-does-not-ingest-logs-http-429/42972/1 "2023-12-04T12:51:37Z")

</div>

**PROBLEM**

After configuring [log collection for AWS Lambda](https://docs.dynatrace.com/docs/shortlink/lambda-log-collection), the log exporter prints errors saying that log ingest is disabled or receives an HTTP 429 status code.

**SOLUTION**

1. Make sure you’re [using Log Monitoring v2](https://docs.dynatrace.com/docs/observe-and-explore/logs/logs-upgrade/logs-upgrade-to-lmc).

2. If you are using Log monitoring v2, check that your log events ingest limit is sufficient.

3. If other troubleshooting methods don’t resolve your issue, you can enable debug logging of the log collector.  
In your Lambda function’s configuration, set the environment variables to the following values.