Each HTTP request that points to a function is counted as one request. Usually, that's a call to your functions, like the API, or the Files service to retrieve a file.

Functions are identified as all requests on a /function/ path. For example like /function/api which is the path for the default Webiny Core API.

When it comes to files. All requests that are on the /files/ path might hit a lambda function. We say "might" because responses from those requests have several layers of caching. They are cached on the CDN and on the user's browser. In case the request is delivered from those caches, the request won't be counted as an API request.

File service also has one more part, which is uploading or deleting files from the storage. When you upload a file, that will partially through a serverless function, the same happens when a file is removed. Files like different image size transformations get automatically purged after 90 days that they have not been accessed. Note that the original image file is never automatically deleted.

Lastly, your usage statistics, and later performance statistic are tracked and automatically processed every 5 minutes by a serverless function. Each processing is calculated as one API request.

Note that if your website doesn't have traffic, the processing for the usage statistics isn't triggered at any point.
Was this article helpful?
Cancel
Thank you!