Creating a trigger for budgets that invokes a Serverless Containers container
Create a trigger for budgets that invokes a Serverless Containers container when threshold values are exceeded.
Before you begin
To create a trigger, you need:
-
A container that the trigger will invoke. If you don't have a container:
-
(optional) A Dead Letter Queue where messages that could not be processed by a container will be redirected. If you don't have a queue, create one.
-
Service account with rights to invoke the 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.
- A budget which, when exceeded, a trigger is fired. If you don't have a budget, 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 Serverless Containers.
-
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.
- In the Launched resource field, select Container.
-
Under Budget settings, select your billing account and budget. You can select All budgets.
-
Under Container settings, select a container 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 delay for the container to 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 for 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 invokes a container, run the command:
yc serverless trigger create billing-budget \
--name <trigger_name> \
--billing-account-id <billing_account_ID> \
--budget-id <budget_ID> \
--invoke-container-id <container_ID> \
--invoke-container-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-container-id: Container ID.--invoke-container-service-account-id: Service account with rights to invoke the container.--retry-attempts: Time to retry invoking the container 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: a1sfe084v4**********
folder_id: b1g88tflru**********
created_at: "2019-12-04T08:45:31.131391Z"
name: budget-trigger
rule:
billing-budget:
billing-account-id: dn2char50j**********
budget-id: dn2jnshmdl**********
invoke_container:
container_id: d4eofc7n0m**********
service_account_id: aje3932acd**********
retry_settings:
retry_attempts: "1"
interval: 10s
dead_letter_queue:
queue-id: yrn:yc:ymq:ru-central1:aoek49ghmk**********:dlq
service-account-id: aje3932acd**********
status: ACTIVE
You can create a trigger for budgets using the API create method.
Checking the result
Make sure the trigger is working properly. To do this, view container logs that show information about invocations.