aws-samples / aws-samples/aws-lambda-extensions

[platform.logsDropped] Unable to process 1000 logs for each invocation

Open
#88 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
487
Forks
144
PR merge metrics
No merged PRs in 30d

Description

Hey team!

We're experiencing an issue while dealing with the Telemetry API when the function has 1k logs.

At some point, we're receiving a `platform.logsDropped`, likely because we're not succeeding to process the payload sent in a timely fashion (this is what I've understand from [the doc](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-logs-api.html))

To make it easier [I've attached a PR](https://github.com/aws-samples/aws-lambda-extensions/pull/89) with a full reproducer. If you invoke the function 10-30 times, you'll see a `[dispatcher:Dispatch] LOG DROPPED!` meaning that we have indeed received a `platform.logsDropped`

I've also tried different buffering options (playing with `timeoutMs `, `maxBytes ` and `maxItems `) without any luck.

Thanks!
Max

Contributor guide

Open the contributing guide

Research direction

Start with the attached PR and its full reproducer, then trace the Telemetry API path associated with the `[dispatcher:Dispatch] LOG DROPPED!` message. Invoke the function 10–30 times with the documented buffering options and confirm the result by verifying that `platform.logsDropped` no longer occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.