This section describes a Forge preview feature. Preview features are deemed stable; however, they remain under active development and may be subject to shorter deprecation windows. Preview features are suitable for early adopters in production environments.
We release preview features so partners and developers can study, test, and integrate them prior to General Availability (GA). For more information, see Forge release phases: EAP, Preview, and GA.
Atlassian will continue to offer free use of the Forge platform through 2025. Starting 1 January 2026, Forge will transition to a consumption-based pricing model, featuring a generous free tier. Developers can monitor their app's resource consumption using Forge usage metric in preparation for the pricing changes in 2026.
Forge usage metric helps you understand and identify issues with resource consumption in a Forge app. They provide insights into services, such as compute, storage, and logs. When monitoring usage metrics, we recommend using filters to refine the results.
Currently, usage metrics are available for the last 60 days.
To view usage metrics:
Access the developer console.
Select the Forge app that you want to view metrics for.
Select Usage in the left menu. Note that the daily data refresh occurs at 12:00 UTC.
Select your profile icon and toggle Display local timezone to convert the daily data refresh from 12:00 UTC to your timezone.
Compute, previously known as Function as a Service (FaaS), is measured in GB-seconds. This usage metric applies to compute functions used in any environment and represents the amount of computing resources your app consumes over time.
Compute functions are measured by the duration your function runs and the amount of memory it consumes during that period. Currently for all Lambda functions, the memory allocation is fixed at 0.5 GB.
1 2Compute in GB-sec = (Lambda Execution Time in seconds * 0.5) GB seconds
Storage metrics are measured in GB. These usage metrics apply to the use of Forge hosted storage in any environment. in any environment.
Storage writes are measured by the amount of data your app stores in key-value or entity storage. This metric tracks how much data your app writes to the Forge storage backend.
1 2Storage writes in GB = Total Data Written to Storage in GB
Storage reads are measured by the amount of data your app retrieves from key-value or entity storage. This metric tracks how much data your app reads from the Forge storage backend.
1 2Storage reads in GB = Total Data Read from Storage in GB
Total storage measures the size of your app data by combining the raw byte size of the data with a per-item storage overhead, which varies based on the features you have enabled. This metric includes the sum of all storage writes and is relevant to both key-value and entity storage.
1 2Storage total in GB = Total Storage writes in GB
Log metrics are measured in GB. This usage metric represents the amount of logging performed by your app over a period of time.
Log writes are measured by the amount of data generated from your app's log statements using console.log() or similar methods. The metric includes the size of the log messages and any metadata. Metadata may include timestamps, log levels, and additional contexts such as stack traces or request IDs.
1 2Log writes in GB = Total Data Written to Logs in GB
Use the date filter to refine your usage metrics. The date filter narrows down the usage metrics based on your chosen time interval. Choose from a range of predefined values, such as the Last month, or choose a more specific date interval using the Custom option.
You can also bookmark the URL on your browser to access usage metrics based on specific filtering criteria for quick access. This is useful for repeated checks of the same metrics, saving time and effort in reapplying preferred filters.
You must use data in accordance with the privacy rights that you've obtained from your user. For more information, see the Atlassian Developer Terms and Forge Terms.
Rate this page: