Durch die Nutzung von AWS re:Post stimmt du den AWS re:Post Nutzungsbedingungen
AWS re:Postre:Post

Lambda concurrency metrics not showing in cloud-watch

0

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.

Themen
ServerlosKalkulationManagement & Unternehmensführung
Tags
ServerlosAWS LambdaAmazon CloudWatch
Sprache
English
user-4564135734
gefragt vor einem Jahr482 Aufrufe
1 Antwort
0

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.

profile pictureAWS
EXPERTE
Uri
beantwortet vor einem Jahr
  • user-4564135734
    vor einem Jahr

    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.

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen

Relevanter Inhalt