Creating a trigger for budgets
Create a trigger for budgets that calls a Cloud Functions function or Serverless Containers container when threshold values are exceeded.
Before you start
To create a trigger, you need:
-
A function or a container the trigger will launch.
-
If you don't have a function:
-
If you don't have a container:
-
-
A budget which, when exceeded, a trigger is fired. If you don't have a budget, create one.
-
(optional) A Dead Letter Queue where messages that could not be processed by a function or a container will be redirected. If you don't have a queue, create one.
-
Service accounts with rights to invoke a function or a container and (optionally) write messages to the Dead Letter Queue. You can use the same service account or different ones. If you don't have a service account, create one.
Creating a trigger
Note
The trigger is initiated within 5 minutes of being created.
-
In the management console, select the folder where you wish to create your trigger.
-
Open Cloud Functions.
-
On the left-hand panel, select Triggers.
-
Click Create trigger.
-
Under Basic parameters:
- Enter a name and description for the trigger.
- In the Type field, select Budget.
- Choose what the trigger will launch — a function or a container.
-
Under Budget settings, select your billing account and budget. You can select All budgets.
-
If the trigger launches:
-
A function, select one under Function settings and specify:
- Tag of the function version;
- A service account to be used to invoke the function.
-
A container, select one under Container settings and specify:
- A container revision;
- A service account to be used to invoke the container.
-
-
(optional) Under Repeat request settings:
- In the Interval field, specify the time after which the function or the container will be invoked again if the current attempt fails. Values can be from 10 to 60 seconds. The default is 10 seconds.
- In the Number of attempts field, specify the number of invocation retries before the trigger moves a message to the Dead Letter Queue. Values can be from 1 to 5. The default is 1.
-
(optional) Under Dead Letter Queue settings, select the Dead Letter Queue and the service account with write privileges to this queue.
-
Click Create trigger.
If you don't have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.
To create a trigger that launches a function, run the command:
yc serverless trigger create billing-budget \
--name <trigger name> \
--billing-account-id <billing account ID> \
--budget-id <budget ID> \
--invoke-function-id <function ID> \
--invoke-function-service-account-id <service account ID> \
--retry-attempts 1 \
--retry-interval 10s \
--dlq-queue-id <Dead Letter Queue ID> \
--dlq-service-account-id <service account ID>
Where:
--name: Trigger name.--billing-account-id: Billing account ID.--budget-id: Budget ID.--invoke-function-id: Function ID.--invoke-function-service-account-id: ID of the service account with rights to invoke the function.--retry-attempts: The time after which the function will be invoked again if the current attempt fails. Optional. Values can be from 10 to 60 seconds. The default is 10 seconds.--retry-interval: The number of invocation retries before the trigger moves a message to the Dead Letter Queue. Optional. Values can be from 1 to 5. The default is 1.--dlq-queue-id: Dead Letter Queue ID. Optional.--dlq-service-account-id: Service account with rights to write messages to the Dead Letter Queue. Optional.
Result:
id: a1sfe084v4se4morbu2i
folder_id: b1g88tflru0ek1omtsu0
created_at: "2019-12-04T08:45:31.131391Z"
name: budget-trigger
rule:
billing-budget:
billing-account-id: dn2char50j**********
budget-id: dn2jnshmdlc1********
invoke_function:
function_id: d4eofc7n0m03********
function_tag: $latest
service_account_id: aje3932acd0c********
retry_settings:
retry_attempts: "1"
interval: 10s
dead_letter_queue:
queue-id: yrn:yc:ymq:ru-central1:aoek49ghmknn********:dlq
service-account-id: aje3932acd0c********
status: ACTIVE
You can create a trigger using the API create.
Checking the result
Make sure the trigger is working properly. To do this, view function logs or container logs: they show information about calls.