Currently, we run several lambda functions in AWS. We have recently deployed a new function that is web-facing. This function needs to serve a high volume of end users thus requiring the use of provisioned concurrency. I have configured provisioned concurrency however can not see the following metrics. - ProvisionedConcurrentExecutions - ProvisionedConcurrencyUtilization - UnreservedConcurrentExecutions - ProvisionedConcurrencyInvocations - ProvisionedConcurrencySpilloverInvocations I can confirm I have provisioned concurrency enabled and can see concurrent invocations via the `ConcurrentExecutions` metric.

Lambda concurrency metrics not showing in cloud-watch

Currently, we run several lambda functions in AWS. We have recently deployed a new function that is web-facing. This function needs to serve a high volume of end users thus requiring the use of provisioned concurrency. I have configured provisioned concurrency however can not see the following metrics.

ProvisionedConcurrentExecutions
ProvisionedConcurrencyUtilization
UnreservedConcurrentExecutions
ProvisionedConcurrencyInvocations
ProvisionedConcurrencySpilloverInvocations

I can confirm I have provisioned concurrency enabled and can see concurrent invocations via the ConcurrentExecutions metric.

주제

서버리스 컴퓨팅 관리 및 거버넌스

태그

서버리스 AWS Lambda 아마존 CloudWatch

언어

English

user-4564135734

질문됨 일 년 전482회 조회

1개 답변

최신
최다 투표
가장 많은 댓글

이 답변이 도움이 되었나요?커뮤니티가 여러분의 지식을 활용할 수 있도록 정답을 찬성하세요.

Provisioned Concurrency works on specific function alias. Are you actually invoking the specific alias? Or are you invoking Latest? You should point your API to the specific alias.

전문가

Uri

답변함 일 년 전

user-4564135734
일 년 전
So we are currently using a function URL. Then assigning provisioned concurrency to a function version. This should use our latest published version. I belive $LATEST should call the latest function version for example 10 or 20 or 30.

Lambda concurrency metrics not showing in cloud-watch

관련 콘텐츠