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 Amazon CloudWatch

语言

English

user-4564135734

已提问 1 年前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

已回答 1 年前

user-4564135734
1 年前
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

相关内容