Lambda log and CloudWatch PutLogEvents limit
I know
- Lambda calls
PutLogEventsto log messages internally. - CloudWatch has a limit on
PutLogEvents.
PutLogEvents: 5 requests per second per log stream.
I want to know
- Could Lambda log stream also be throttled by
PutLogEvents? - If so, how to know if a Lambda log stream is throttled or not?
Any error message in the log stream?
- When does Lambda call
PutLogEvents?
for example,
- at the end of a Lambda function, it calls
PutLogEventsonce. - when flushing buffer(stdout), it calls
PutLogEventsall the time.
amazon-web-services aws-lambda amazon-cloudwatch
asked Nov 23 '18 at 17:37
SangminKimSangminKim
2,41452361
add a comment |
I know
- Lambda calls
PutLogEventsto log messages internally. - CloudWatch has a limit on
PutLogEvents.
PutLogEvents: 5 requests per second per log stream.
I want to know
- Could Lambda log stream also be throttled by
PutLogEvents? - If so, how to know if a Lambda log stream is throttled or not?
Any error message in the log stream?
- When does Lambda call
PutLogEvents?
for example,
- at the end of a Lambda function, it calls
PutLogEventsonce. - when flushing buffer(stdout), it calls
PutLogEventsall the time.
amazon-web-services aws-lambda amazon-cloudwatch
asked Nov 23 '18 at 17:37
SangminKimSangminKim
2,41452361
I suppose that AWS Lambda internally doesn't call PutLogEvents more than the rate limit allows (so if you have more than 5 concurrent invocations some logs will be written together). Each request is up to 1MB, so you have up to 5MB/sec which is much.
– Ronyis
Nov 23 '18 at 18:21
add a comment |
I know
- Lambda calls
PutLogEventsto log messages internally. - CloudWatch has a limit on
PutLogEvents.
PutLogEvents: 5 requests per second per log stream.
I want to know
- Could Lambda log stream also be throttled by
PutLogEvents? - If so, how to know if a Lambda log stream is throttled or not?
Any error message in the log stream?
- When does Lambda call
PutLogEvents?
for example,
- at the end of a Lambda function, it calls
PutLogEventsonce. - when flushing buffer(stdout), it calls
PutLogEventsall the time.
amazon-web-services aws-lambda amazon-cloudwatch
asked Nov 23 '18 at 17:37
SangminKimSangminKim
2,41452361
I know
- Lambda calls
PutLogEventsto log messages internally. - CloudWatch has a limit on
PutLogEvents.
PutLogEvents: 5 requests per second per log stream.
I want to know
- Could Lambda log stream also be throttled by
PutLogEvents? - If so, how to know if a Lambda log stream is throttled or not?
Any error message in the log stream?
- When does Lambda call
PutLogEvents?
for example,
- at the end of a Lambda function, it calls
PutLogEventsonce. - when flushing buffer(stdout), it calls
PutLogEventsall the time.
amazon-web-services aws-lambda amazon-cloudwatch
amazon-web-services aws-lambda amazon-cloudwatch
asked Nov 23 '18 at 17:37
SangminKimSangminKim
2,41452361
asked Nov 23 '18 at 17:37
SangminKimSangminKim
2,41452361
edited Nov 23 '18 at 17:43
SangminKim
asked Nov 23 '18 at 17:37
SangminKimSangminKim
2,41452361
asked Nov 23 '18 at 17:37
SangminKimSangminKim
2,41452361
asked Nov 23 '18 at 17:37
SangminKimSangminKim
2,41452361
2,41452361
I suppose that AWS Lambda internally doesn't call PutLogEvents more than the rate limit allows (so if you have more than 5 concurrent invocations some logs will be written together). Each request is up to 1MB, so you have up to 5MB/sec which is much.
– Ronyis
Nov 23 '18 at 18:21
add a comment |
I suppose that AWS Lambda internally doesn't call PutLogEvents more than the rate limit allows (so if you have more than 5 concurrent invocations some logs will be written together). Each request is up to 1MB, so you have up to 5MB/sec which is much.
– Ronyis
Nov 23 '18 at 18:21
I suppose that AWS Lambda internally doesn't call PutLogEvents more than the rate limit allows (so if you have more than 5 concurrent invocations some logs will be written together). Each request is up to 1MB, so you have up to 5MB/sec which is much.
– Ronyis
Nov 23 '18 at 18:21
I suppose that AWS Lambda internally doesn't call PutLogEvents more than the rate limit allows (so if you have more than 5 concurrent invocations some logs will be written together). Each request is up to 1MB, so you have up to 5MB/sec which is much.
– Ronyis
Nov 23 '18 at 18:21
add a comment |
1 Answer
1
active
oldest
votes
Let's brake my answer in 2 parts:
Part 1: Check answers here about your worries about being throttled from inside your lambda. Unless you're actually calling the SDK method I concur with the answers here and tell you that let Amazon handle their internal stuff. I hope this covers items 1 and 2 of your question.
Now for item 3:
AFAIK the lambda runtime sends logs:
- When your lambda starts.
- When your lambda ends (or get's interrupted by an exception).
- Timeout.
- If you explicitely use any of the logging functions provided in the runtime (according to a coworker of mine: it is safe to assume that everyting you send to
stdoutwill be logged). - If you use AWS SDK inside your lambda to access other AWS services.
answered Nov 23 '18 at 18:41
yorodmyorodm
2,172717
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450957%2flambda-log-and-cloudwatch-putlogevents-limit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Let's brake my answer in 2 parts:
Part 1: Check answers here about your worries about being throttled from inside your lambda. Unless you're actually calling the SDK method I concur with the answers here and tell you that let Amazon handle their internal stuff. I hope this covers items 1 and 2 of your question.
Now for item 3:
AFAIK the lambda runtime sends logs:
- When your lambda starts.
- When your lambda ends (or get's interrupted by an exception).
- Timeout.
- If you explicitely use any of the logging functions provided in the runtime (according to a coworker of mine: it is safe to assume that everyting you send to
stdoutwill be logged). - If you use AWS SDK inside your lambda to access other AWS services.
answered Nov 23 '18 at 18:41
yorodmyorodm
2,172717
add a comment |
Let's brake my answer in 2 parts:
Part 1: Check answers here about your worries about being throttled from inside your lambda. Unless you're actually calling the SDK method I concur with the answers here and tell you that let Amazon handle their internal stuff. I hope this covers items 1 and 2 of your question.
Now for item 3:
AFAIK the lambda runtime sends logs:
- When your lambda starts.
- When your lambda ends (or get's interrupted by an exception).
- Timeout.
- If you explicitely use any of the logging functions provided in the runtime (according to a coworker of mine: it is safe to assume that everyting you send to
stdoutwill be logged). - If you use AWS SDK inside your lambda to access other AWS services.
answered Nov 23 '18 at 18:41
yorodmyorodm
2,172717
add a comment |
Let's brake my answer in 2 parts:
Part 1: Check answers here about your worries about being throttled from inside your lambda. Unless you're actually calling the SDK method I concur with the answers here and tell you that let Amazon handle their internal stuff. I hope this covers items 1 and 2 of your question.
Now for item 3:
AFAIK the lambda runtime sends logs:
- When your lambda starts.
- When your lambda ends (or get's interrupted by an exception).
- Timeout.
- If you explicitely use any of the logging functions provided in the runtime (according to a coworker of mine: it is safe to assume that everyting you send to
stdoutwill be logged). - If you use AWS SDK inside your lambda to access other AWS services.
answered Nov 23 '18 at 18:41
yorodmyorodm
2,172717
Let's brake my answer in 2 parts:
Part 1: Check answers here about your worries about being throttled from inside your lambda. Unless you're actually calling the SDK method I concur with the answers here and tell you that let Amazon handle their internal stuff. I hope this covers items 1 and 2 of your question.
Now for item 3:
AFAIK the lambda runtime sends logs:
- When your lambda starts.
- When your lambda ends (or get's interrupted by an exception).
- Timeout.
- If you explicitely use any of the logging functions provided in the runtime (according to a coworker of mine: it is safe to assume that everyting you send to
stdoutwill be logged). - If you use AWS SDK inside your lambda to access other AWS services.
answered Nov 23 '18 at 18:41
yorodmyorodm
2,172717
answered Nov 23 '18 at 18:41
yorodmyorodm
2,172717
answered Nov 23 '18 at 18:41
yorodmyorodm
2,172717
answered Nov 23 '18 at 18:41
yorodmyorodm
2,172717
2,172717
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450957%2flambda-log-and-cloudwatch-putlogevents-limit%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I suppose that AWS Lambda internally doesn't call PutLogEvents more than the rate limit allows (so if you have more than 5 concurrent invocations some logs will be written together). Each request is up to 1MB, so you have up to 5MB/sec which is much.
– Ronyis
Nov 23 '18 at 18:21