All Apps and Add-ons

AWS Add-On to Pull in Lambda Memory Utilization

petersonjared
Explorer

We have the AWS Add-On installed and up and running but we are not getting memory utilization for our Lambda execution logs. We get the allocated memory but I am wanting to see if I can get the actual memory so then I could compare it with the allocated memory. For AWS Lambda on our HF(s) we have it set for a row for with these two dimension values:
[{"FunctionName":["."],"Resource":["."]}]
[{"FunctionName":[".*"]}]

With the metrics set to ALL and Metric stats set to: Average, Sum, SampleCount, Maximum, Minimum for both dimensions.

Within AWS's "Insights" with CloudWatch Log Groups you can get this information now and it looks like Splunk syntax to do so. But since I already have the other data and reports in Splunk I'd prefer to be able to do this analysis there.

Thanks for your guidance on this!

AWS Insights query using "maxMemoryUsed" that I'd like to get into Splunk via the AWS Add-On to do the same thing there:
filter @type = "REPORT"
| stats max(@memorySize / 1024 / 1024) as provisonedMemoryMB,
min(@maxMemoryUsed / 1024 / 1024) as smallestMemoryRequestMB,
avg(@maxMemoryUsed / 1024 / 1024) as avgMemoryUsedMB,
max(@maxMemoryUsed / 1024 / 1024) as maxMemoryUsedMB,
provisonedMemoryMB - maxMemoryUsedMB as overProvisionedMB

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...