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!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk on November 6 at 11AM PT, and empower your SOC to reach new heights! Duration: ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...