How to query usage data from Functions

This guide explains how to query data from the Consumption dataset and check Functions' compute time and invocations using the GraphiQL Playground.

View as Markdown

The workloadConsumptionMetrics dataset lets you get real-time aggregated data related to consumption and usage of Azion products, including Functions.

The information can be accessed through the GraphQL API, allowing you to transfer this data to a third-party platform, and enabling you to further analyze and review. Additionally, the data is available for up to 24 months.

This guide explains how to query Functions’ compute time and invocations metrics using the GraphiQL Playground.

Querying Functions’ usage data

To query Functions’ compute time and invocations, proceed as follows:

  1. Access the GraphiQL Playground by going to the following link: https://api.azion.com/v4/consumption/graphql.
    • You must be logged in to your Azion account. Otherwise, you’ll receive an error message.
  2. Send a query following this format:
query {
workloadConsumptionMetrics(
filter: {
tsRange: {
begin: "2025-02-01T00:00:00",
end: "2025-03-01T00:00:00",
}
productId: 1531930033
metricNameIn: ["invocations", "compute_time"]
}
aggregate: {
sum: accounted
}
limit: 10000
groupBy: [clientId, workloadId, productId, metricName, region]
) {
clientId
workloadId
productId
metricName
region
total: sum
}
}

Where:

FieldDescription
filterDefines the criteria used to filter the data returned by the query.
tsRangeA subfield of filter. Specifies a time range for filtering data. It includes begin and end fields to define the start and end timestamps. Format: "YYYY-MM-DDTHH:mm:ss"; example: "2024-04-11T00:00:00".
sum: accountedAs a subfield of aggregate, calculates the total accounted usage for events matching the query’s filters and groups.
limitSpecifies the maximum number of results to return. System maximum: 10000.
groupBySpecifies the fields by which the query results should be grouped. Example: [clientId, metricName].
productIdUnique identifier of the product being used. In this case, 1531930033 for Functions.
metricNameName of the calculated metric for analytics. Example: invocations or compute_time.

This example retrieves data for the total number of invocations or compute time used by Functions. The results are grouped by clientId and workloadId. To learn more about the available fields, check the Consumption GraphQL API Fields documentation.

  1. You’ll receive a JSON response similar to this:
{
"data": {
"workloadConsumptionMetrics": [
{
"clientId": "12345a",
"workloadId": 1234567890,
"productId": 1531930033,
"metricName": "invocations",
"region": "United States",
"Total": 816931
},
{
"clientId": "67890a",
"workloadId": 1987654321,
"productId": 1531930033,
"metricName": "invocations",
"region": "Europe",
"Total": 33134
},
{
"clientId": "111111b",
"workloadId": 1231231230,
"productId": 1531930033,
"metricName": "compute_time",
"region": "All Other Regions",
"Total": 436363.41
}
]
}
}

Where:

FieldDescription
clientIdClient unique identifier on Azion. Example: 8437r.
workloadIdIdentifier for the workload associated with the usage. Example: 4829301746.
productIdUnique identifier of the product being used. In this case, 1531930033 for Functions.
metricNameName of the measured metric for analytics. Example: invocations or compute_time.
regionGeographical region where the usage was recorded. Example: Europe.
totalThis field is the result of a sum.
When querying compute_time: total execution time for Functions, measured in seconds. Example: 436363.41.
When querying invocations: total number of function invocations. Example: 33134.

To know more about the available fields, check the Consumption GraphQL API Fields documentation.