App metrics show you how your Forge app is currently performing across all sites.
This page explains how to view and filter the metrics for your app, including specific data about your
app's invocation errors.
Timeout: The function has not been successful within a
Unhandled exception: The function threw an uncaught exception. This category may
include exceeding other platform limits such as
To learn more about why the exception was thrown, view your app logs
by selecting Logs in the left hand menu.
For more information, see
View app logs and installations.
Invocation time: The time it takes for each function under the handler field in the app manifest.yml file to successfully complete an invocation. The chart shows the distribution of invocation time as a histogram across different time buckets. The time is measured from inside the AWS lambda, and doesn't include cold start, but it includes the time it took for the lambda initialization phase to complete.
Each metric is displayed as both a chart and a value. The value,
displayed at the top of the screen, represents the overall or total value for that metric
and includes any applied filters.
Use these filters to refine your metrics:
All sites: Narrows down the metrics based on the sites that your app is
installed onto, for example, <your-site>.atlassian.net. You can select multiple sites.
Environment: Narrows down the metrics for a specific app environment
for your app.
Date: Narrows down the metrics based on your chosen time interval. Choose from a range of
predefined values, such as the Last 24 hours, or choose a more specific time interval using
the Custom option.
Each metric can also be grouped by app version or function, by selecting the Group by dropdown next to a chart.
Metrics are only shown for sites with at least one invocation in the past 14 days.
All dates are in Coordinated Universal Time (UTC).
Each chart's data resolution depends on the time interval you've selected. For example
'Last 24 hours' shows data at a 30 minute resolution, and 'Last hour' shows data at a
1 minute resolution.
Metrics may not always be accurate because undelivered metrics
data isn’t back-filled and data sampling might be used for some metrics.
You can bookmark the URL on your browser to access metrics based on specific filtering
criteria for quick access.
To learn more about your app's invocation errors, select the chart title, or select the More actions (⋯) menu
on the chart and View details.
The following screen appears, showing site-specific information about your app's invocation errors.
In this view, you can search, filter, and sort the data to identify errors across specific sites and installations.
You can also group the chart by version and error type, by selecting the Group chart by dropdown above the chart.
Metrics are shown according to the selected time range.
The data displayed in the chart will be filtered according to the sites selected in the table.
By default, the table is sorted by error count, but you can sort by any column.
To learn more about your app's invocation time, select the chart title, or select the More actions (⋯) menu on the chart and View details.
The following screen appears, showing function-specific information about your app's invocation time.
In this view, you can search, filter, and group the data to see invocation time across specific functions, environments, and time periods.
To group the chart by function or version, select the Group chart by dropdown above the chart. Note, this will only reflect in the chart data, not in the table data.
Metrics are shown according to the selected time range and the selected deployment environment.
By default, the table is sorted in descending order of invocation time, meaning functions with the longest invocation time will appear at the top. However, you can sort by any column.