AWS Lambda
Last updated 16 October 2026
ARNscope puts a Lambda function’s metrics, its logs and Live Tail on one page. The list shows how each function did over the last day; open one for its invocations, errors, duration and cold starts, a search across its log group grouped by invocation, its log streams, and a live tail. Invoking a function is a write, so it asks first.
Functions
Open Lambda in ARNscope and choose the profile and region. The list shows every function with its runtime and version, and on the right its invocations and error rate over the last 24 hours, from CloudWatch metrics. Type in the filter to narrow the list by name.
Select a function to open it. The header shows its description, then a strip with the runtime, memory, timeout, architecture, version, code size and region.
Metrics and cold starts
Insights sits under the header. It shows, for the chosen time range, a tile and a small chart for each of:
| Tile | What it shows |
|---|---|
| Invocations | Total invocations and peak concurrency |
| Errors | Errors and the error rate |
| Throttles | Throttled invocations |
| Duration | p95, with p50, p99 and the average |
| Concurrency | Maximum concurrent executions |
| Cold starts | Count and share of invocations, with the average and maximum init duration |
Invocations, errors, throttles, duration and concurrency come from CloudWatch’s AWS/Lambda metrics. Cold starts come from a Logs Insights query over the function’s REPORT lines; that query scans the log group and is billed per GB, so the line under the tiles says how many records and bytes it scanned. Click Insights to fold the tiles away.
The time range (the last 15 minutes up to 7 days, or a custom range) drives both the metrics and the log search below them.
Log search
Log search reads every stream in the function’s log group for the time range, newest first, and groups the lines by invocation: each group shows its request ID, when it started, its duration, how many lines it wrote, and chips for a cold start, errors or warnings. Expand a group to read its lines; JSON lines can be opened formatted.
- Type a CloudWatch filter pattern, such as
?ERROR ?Exceptionor{ $.level = "error" }, and press Search. - Quick filters set a pattern in one click: Errors, Timeouts (
Task timed out), Cold starts (REPORTlines with an init duration), Throttles / OOM (runtime exits and out-of-memory errors) and Reports (one summary line per invocation). - Paste a Request ID to see every line one invocation wrote, or click Show all lines for this invocation under a group.
A search reads up to 500 events at a time; when more match, Load more reads the next page.
Log streams
Log streams lists the 20 newest streams with the time of their latest invocation. Open one to read it invocation by invocation: pick a request ID from the menu, or filter the lines as you type. The Invocation details panel shows the selected invocation’s request ID, status, start, duration, billed duration and memory, and the log group and stream it came from.
Live Tail
Tail function starts CloudWatch Logs Live Tail across every stream of the function, and new lines arrive as they are written, with a Live chip while it runs and a request ID menu to pick one invocation. Stop tail ends it, and it also stops when you leave the page. The view keeps the newest 2,000 records and drops older ones, and it says when CloudWatch sampled a busy update. Live Tail is billed by CloudWatch per minute.
Invoke
Invoke runs the function for real, so it opens a dialog first. The dialog names the profile and region, says the call is synchronous, warns that the function can change AWS resources or other systems, and takes a JSON payload (up to 6 MB, used once and not saved).
Start tail & invoke starts Live Tail first; the function runs only after CloudWatch confirms the tail is active. The dialog then closes so you can watch the logs, and the response appears above them when the function returns: the status code, the version that ran, any function error, and the payload (shown up to 256 KB).
If your role cannot invoke the function, Invoke is disabled, with the reason from the IAM permission check.
Permissions
| What | Actions |
|---|---|
| List functions | lambda:ListFunctions |
| Metrics and the list’s last-day figures | cloudwatch:GetMetricData |
| Cold starts | logs:StartQuery, logs:GetQueryResults, logs:StopQuery |
| Log search | logs:FilterLogEvents |
| Log streams | logs:DescribeLogStreams, logs:GetLogEvents |
| Live Tail | logs:StartLiveTail, logs:DescribeLogGroups |
| Invoke | lambda:InvokeFunction |
Limitations
- Invoke is synchronous only (
RequestResponse); there is no asynchronous or dry-run invoke, and no choice of version or alias. - ARNscope does not change a function: no code, configuration, environment, alias or concurrency changes.
- Log search shows 500 events per page; Log streams lists the 20 newest streams.
- Cold starts need the function’s
REPORTlines in its log group, and each count runs a billed Logs Insights query. - Live Tail can be sampled by CloudWatch for busy log groups; ARNscope says when it happens.