Lambda Telemetry Extension
The Lambda Telemetry Extension sends a function’s logs, metrics, and traces to KloudMate. You add a layer to the function and set two environment variables — there’s no code to change, no CloudFormation stack, and no CloudWatch subscription.
When to use it
Section titled “When to use it”KloudMate gives you two ways to monitor Lambda, and they fit different needs.
The AWS account integration connects a whole account when you deploy one CloudFormation stack. From there KloudMate works automatically — it discovers your functions, reads their CloudWatch metrics, and subscribes their log groups for you, with no roles or subscriptions to wire up by hand. Use it to cover an account end to end without touching individual functions.
The Telemetry Extension instruments the functions you choose. It adds traces on top of logs and metrics, and the data arrives within seconds instead of waiting on CloudWatch. Use it where you want richer, faster telemetry.
| AWS account integration | Telemetry Extension | |
|---|---|---|
| Setup | Deploy one CloudFormation stack | Add a layer and two env vars per function |
| Coverage | Every function in the account, automatically | The functions you add it to |
| Signals | Metrics and logs, from CloudWatch | Logs, metrics, and traces |
| Delivery | CloudWatch’s delay (about a minute) | Within seconds |
You can run both — the account integration for broad coverage, the extension where you want traces — with one overlap to watch for.
What you get
Section titled “What you get”- Logs — everything your function writes to stdout/stderr, searchable in Log Explorer.
- Metrics — invocation duration, billed duration, memory used, and cold-start time.
- Traces — one trace per invocation, linked to your AWS X-Ray trace when active tracing is on.