Problem with classic services vs cloud services

[gustavodutra]

Hi everyone, how are you?

When I migrate my AWS Lambda metrics (built-in) to cloud services, Dynatrace doesn't detect all the Lambdas that the built-in metrics do.

Does anyone know what might be causing this? I have 280 Lambdas in my environment (according to built-in metrics), but when I migrate to cloud services, only 163 are detected.

What could be the issue?

I followed this documentation:

https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/cloudwatch-metric...

[gustavodutra]

Someone help me? Please.

[dannemca]

I have no practical experience with this, but reading the doc we see this

• Due to their different implementations, they may detect different numbers of instances. Cloud services show only instances with metrics.

  • https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-with-aws/cloudwatch-metric... 

Could you confirm if all your lambdas are generating metrics and properly configured to send them to Dynatrace?

[gustavodutra]

Yes, in the AWS dashboard it identifies 280 lambdas and in Dynatrace when I switch to cloud services, it only identifies 163.

[dawid_kaszubski]

Hi @gustavodutra , 

@dannemca is right. Cloud Service Lambda shows only active Lambda functions. It means Lambda functions that generate metrics.