Oracle Cloud Infrastructure Documentation

Function Metrics

You can monitor the health, capacity, and performance of functions you've deployed to Oracle Functions by using (Monitoring service) A measurement related to health, capacity, or performance of a given resource. Example: CpuUtilization, The trigger rule and query to evaluate and related configuration, such as notification details to use when the trigger is breached. Alarms passively monitor your cloud resources using metrics in Monitoring., and notifications.

This topic describes the metrics emitted by the metric namespace oci_faas (the Oracle Functions service).

Resources: functions

Overview of the Oracle Functions Service Metrics

Oracle Functions monitors function execution, and collects and reports metrics such as:

  • The number of times a function is invoked.
  • The length of time a function runs for.
  • The number of times a function failed.
  • The number of requests to invoke a function that returned a '429 Too Many Requests' error in the response (known as 'throttled function invocations').


IAM policies: To monitor resources, you must be given the required type of access in a An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources. written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. The policy must give you access to the monitoring services as well as the resources being monitored. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. you should work in. For more information on user authorizations for monitoring, see the Authentication and Authorization section for the related service: Monitoring or Notifications.

For more information about the policy statement required to access metrics emitted by Oracle Functions, see Create a Policy to Give Oracle Functions Users Access to Function-Related Resources.

Available Metrics: oci_faas

The metrics listed in the following tables are automatically available for any functions you create. You do not need to enable monitoring on the resource to get these metrics.

Oracle Functions metrics include the following dimensions:

The An Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). This ID is included as part of the resource's information in both the Console and API. of the application containing functions.
The An Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID). This ID is included as part of the resource's information in both the Console and API. of the function.
The response when a function is invoked (one of Success, Error, or Throttled).
Metric Metric Display Name Unit Description Dimensions
FunctionExecutionDuration Function Duration ms Total function execution duration. Expressed in milliseconds. applicationId


FunctionInvocationCount Function Invocations count Total number of function invocations.




This metric is used in the following default metric charts:

Errors (with responseType = "Error")

Throttles (with responseType = "Throttled")

count Total number of function responses. applicationId



Using the Console

To view default metric charts for a single function
To view default metric charts for all functions in an application
To view default metric charts for all the functions in all the applications in a compartment

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use the following APIs for monitoring: