ARNscopeDocs

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.

A narrated tour of about ninety seconds, with captions: the function list, metrics and cold starts, log search, log streams, Live Tail and an invoke. Sample data.

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.

Each function's invocations and error rate over the last day, and a filter 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.

Invocations, errors, throttles, duration percentiles, concurrency and cold starts, for one time range.

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 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.

The log group's lines, grouped by invocation, with quick filters for errors and cold starts.
One request ID, every line that invocation wrote.

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.

A log stream, read invocation by invocation.

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.

Live Tail across every stream of the function.

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).

Invoke asks first, tails the logs while the function runs, then shows the response.

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