Skip to content

Add disabled central config as a caveat to lambda docs #3504

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 23, 2024
Merged

Add disabled central config as a caveat to lambda docs #3504

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/setup-aws-lambda.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,8 @@ Errors related to traced spans will be sent as well.
==== Caveats
* System and custom metrics are not collected for Lambda functions. This is both because most of those are irrelevant
and because the interval-based event sending model is not suitable for FaaS environments.
* Central Configuration is disabled, which means that the APM agent configuration cannot be changed without redefining
the lambda environment variables or APM agent settings.
* Cold starts can be significantly slower when the agent is installed. If this is an issue, following are ways to deal with slow code
starts:
** If the only issue with slower cold starts is Lambda timing out, consider increasing the configured timeout.
Expand Down