Oracle Cloud Infrastructure Documentation

Monitoring Memory Usage and Availability for Concurrent Function Execution

Find out how to monitor the usage and availability of memory for concurrent function execution by OCI Functions.

OCI Functions has a limit for the total amount of memory available for concurrent execution of all functions in a region. The limit is named total-concurrency-mb, and specifies the maximum amount of memory that can be allocated for concurrent function execution.

The total-concurrency-mb memory limit has a default value, as shown in Function Limits. The default value might have already been increased in your tenancy, perhaps in response to Support requests that were logged on previous occasions when memory capacity was exceeded.

You can use the Console to see the current value of the total-concurrency-mb memory limit in a region (see Viewing the Current Memory Limit for Concurrent Function Execution).

When the total-concurrency-mb memory limit is reached, HTTP-429 errors are returned in response to function invocations. When you become aware that OCI Functions needs more memory for concurrent function execution, you can submit a request to increase the total-concurrency-mb memory limit (see Requesting a Service Limit Increase).

Instead of waiting for the total-concurrency-mb memory limit to be reached, and then addressing the requirement, you can use Oracle Cloud Infrastructure Monitoring and the AllocatedTotalConcurrency metric to monitor how much of the memory available for concurrent function execution has been allocated. Note that the value of the AllocatedTotalConcurrency metric is the amount of allocated memory. The amount of memory that is actually used for concurrent function execution is always less than, or equal to, the value of the AllocatedTotalConcurrency metric. For more information, see Viewing the Amount of Memory Recently Allocated for Concurrent Function Execution.

You can also use the AllocatedTotalConcurrency metric to create an alarm to notify you if concurrent function execution memory allocation passes a threshold that you define. For more information, see Creating a concurrent function execution memory allocation threshold alarm.

Viewing the Current Memory Limit for Concurrent Function Execution

To view the current memory limit for concurrent function execution:

  1. Open the navigation menu and click Governance & Administration. Under Tenancy Management, click Limits, Quotas and Usage.

  2. Select Functions from the Service list.

  3. Select the region from the Scope list.

  4. Select the root compartment from the Compartment list.

    The total-concurrency-mb limit shows the current memory limit for concurrent function execution.

  5. (Optional) To request additional memory for concurrent function execution, click the the Actions menu (Actions Menu) beside the total-concurrency-mb limit, select Open Support Request, and follow the instructions.

Viewing the Amount of Memory Recently Allocated for Concurrent Function Execution

To view the amount of memory recently allocated for concurrent function execution:

  1. Open the navigation menu and click Observability & Management. Under Monitoring, click Metrics Explorer.

  2. Use the Start time and End time fields to specify a representative time period to analyze.
  3. In the Query 1 panel, create a query as follows:
    1. For Compartment, select the root compartment.
    2. For Metric namespace, select oci_faas.
    3. Select the Advanced mode option and enter one of the following queries in the Query code editor:
      • To show the total amount of memory allocated for concurrent function execution for all the functions in the tenancy at 1 minute intervals, during the time period you specified, enter the following query:
        AllocatedTotalConcurrency[1m].groupBy(resourceId).max().grouping().sum()
      • To show the total amount of memory allocated for concurrent function execution for all the functions in a single application at 1 minute intervals, during the time period you specified, enter the following query:
        AllocatedTotalConcurrency[1m]{resourceId = "<application-OCID>"}.max()

        where <application-OCID> is the OCID of an application. For example:

        AllocatedTotalConcurrency[1m]{resourceId = "ocid1.fnapp.oc1.phx.aaaaaaaaaf______r3ca"}.max()

  4. Click Update Chart.

    The chart updates, and shows the amount of memory that was allocated for concurrent function execution, during the time period you selected.

Creating a concurrent function execution memory allocation threshold alarm

To create an alarm that fires when concurrent function execution memory allocation exceeds a threshold that you define:

  1. Open the navigation menu and click Observability & Management. Under Monitoring, click Alarm Definitions.

  2. Click Create Alarm.
  3. For Alarm name, enter a meaningful name for the alarm. Avoid entering confidential information.
  4. Select the Switch to Advanced Mode option.
  5. In the Metric details area, specify the metric to evaluate for the alarm, as follows:
    1. For Compartment, select the root compartment.
    2. For Metric namespace, select oci_faas.
  6. In the Trigger rule area, specify the condition that must be satisfied for the alarm to fire:
    • Trigger delay minutes: Enter the number of minutes that the condition must be maintained for the alarm to fire.
    • Alarm severity: Select the importance to be given to a notification that the alarm has fired.

    • Query code editor: Enter a query to define a condition that, when satisfied, causes the alarm to fire, as follows:

      • If you want the alarm to fire when memory allocation for concurrent function execution for all the functions in the tenancy exceeds a certain amount, enter the following query:
        AllocatedTotalConcurrency[1m].groupBy(resourceId).max().grouping().sum() > <memory-threshold>

        where <memory-threshold> is an amount of memory (in MiB) to use as the threshold, above which you want the alarm to fire.

        For example, you might want an alarm to fire when the amount of memory allocated for concurrent function execution exceeds 70% of the total memory available for concurrent function execution. If the total memory for concurrent function execution is 60 GB (that is, 61,440 MiB), enter the following query:

        AllocatedTotalConcurrency[1m].groupBy(resourceId).max().grouping().sum() > 43008
      • If you want the alarm to fire when memory allocation for concurrent function execution for all the functions in a single application exceeds a certain amount, enter the following query:
        AllocatedTotalConcurrency[1m]{resourceId = "<application-OCID>"}.max() > <memory-threshold>

        where:

        • <application-OCID> is the OCID of the application
        • <memory-threshold> is an amount of memory (in MiB) to use as the threshold, above which you want the alarm to fire.

        For example, you might want an alarm to fire when the amount of memory allocated for concurrent function execution for all the functions in a single application exceeds 10% of the total memory available for concurrent function execution. If the total memory available for concurrent function execution is 60 GB (that is, 61,440 MiB), enter the following query:

        AllocatedTotalConcurrency[1m]{resourceId = "ocid1.fnapp.oc1.phx.aaaaaaaaaf______r3ca"}.max() > 6144
  7. Select the Switch to Basic Mode option.
  8. In the Define alarm notifications area:
    1. For Destination, specify where notifications are sent when the alarm fires:
      • Destination service: Select Notifications.
      • Compartment: Select the compartment that contains the resources that emit the metrics evaluated by the alarm. The selected compartment is also the storage location of the alarm.
      • Topic: The topic to use for notifications. Each topic supports one or more subscription protocols, such as PagerDuty. If a suitable topic does not already exist, click Create a topic and define a new topic. For reference, see Creating a Basic Alarm.
    2. For Message grouping, select one of the following options:
      • Group notifications across metric streams: Collectively track metric status across all metric streams. Send a message when metric status across all metric streams changes.
      • Split notifications per metric stream: Individually track metric status by metric stream. Send a message when metric status for each metric stream changes. For an example, see Scenario: Split Messages by Metric Stream.
    3. For Message Format, select one of the following options:
      • Send formatted messages: Simplified, user-friendly layout. To view supported subscription protocols and message types for formatted messages (options other than Raw), see Friendly formatting.
      • Send Pretty JSON messages (raw text with line breaks): JSON with new lines and indents.
      • Send raw messages: Raw JSON blob.
    4. To suppress evaluations and notifications for a specified length of time, select Suppress notifications. This option is useful for avoiding alarm notifications during system maintenance periods. Specify a start time, end time, and an optional description. See Best Practices for Your Alarms and Suppressing an Alarm.
    5. To save the alarm without starting to evaluate metric data, clear the Enable this alarm? check box.
  9. Click Save alarm.