Creating a trigger for Cloud Logging that invokes a Serverless Containers container

Written by

Updated at October 17, 2024

Getting started
Creating a trigger
Checking the result
See also

Create a trigger for Cloud Logging that invokes a Serverless Containers container when entries are added to a log group.

Getting started

To create a trigger, you need:

A container that the trigger will invoke. If you do not have a container:
- Create a container.
- Create a container revision.
(Optional) A Dead Letter Queue where messages that could not be processed by a container will be redirected. If you do not 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 do not have a service account, create one.

A log group that activates the trigger when entries are added there. If you do not have a log group, create one.

Creating a trigger

Note

The trigger is initiated within 5 minutes of being created.

Management console

CLI

Terraform

API

In the management console, select the folder where you want to create a trigger.
Open Serverless Containers.
In the left-hand panel, select Triggers.
Click Create trigger.
Under Basic settings:
- Enter a name and description for the trigger.
- In the Type field, select Cloud Logging.
- In the Launched resource field, select Container.
Under Cloud Logging settings, specify:
- Log group.
- (Optional) Resource types, such as serverless.function for Cloud Functions functions.
- (Optional) IDs of Yandex Cloud or your resources, such as Cloud Functions functions.
- (Optional) Log streams.
- (Optional) Logging levels.
A trigger fires when records that match all the optional settings are added to the specified log group. If an optional setting is not specified, the trigger fires for any value of the setting.
Under Batch message settings, specify:
- Waiting time, s. The values may range from 1 to 60 seconds. The default value is 1 second.
- Batch size. The values may range from 1 to 100. The default value is 1.
The trigger groups messages for a period of time not exceeding the specified timeout and sends them to a container. The number of messages cannot exceed the specified batch size.
Under Container settings, select a container and specify a service account to invoke it under.
(Optional) Under Repeat request settings:
- In the Interval field, specify the time interval to retry invoking the container if the current attempt fails. The values may range from 10 to 60 seconds. The default value 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. The values may range from 1 to 5. The default value is 1.
Optionally, under Dead Letter Queue settings, select the dead-letter queue and the service account with write permissions for this queue.
Click Create trigger.

If you do not 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 this command:

yc serverless trigger create logging \
  --name <trigger_name> \
  --log-group-name <log_group_name> \
  --batch-size <message_batch_size> \
  --batch-cutoff <maximum_wait_time> \
  --resource-ids <resource_ID> \
  --resource-types <resource_type> \
  --stream-names <logging_stream> \
  --log-levels <logging_level> \
  --invoke-container-id <container_ID> \
  --invoke-container-service-account-id <service_account_ID> \
  --retry-attempts <number_of_retry_invocation_attempts> \
  --retry-interval <interval_between_retry_attempts> \
  --dlq-queue-id <dead_letter_queue_ID> \
  --dlq-service-account-id <service_account_ID>

Where:

--name: Trigger name.
--log-group-name: Name of the log group that invokes a container when records are added.

--batch-size: Message batch size. This is an optional parameter. The values may range from 1 to 10. The default value is 1.
--batch-cutoff: Maximum wait time. This is an optional parameter. The values may range from 1 to 60 seconds. The default value is 1 second. The trigger groups messages for a period not exceeding batch-cutoff and sends them to a container. The number of messages cannot exceed batch-size.

--resource-ids: IDs of Yandex Cloud or your resources, such as Cloud Functions functions. This is an optional parameter.
--resource-types: Resource types, such as serverless.function for Cloud Functions functions. This is an optional parameter.
--stream-names: Log streams. This is an optional parameter.
--log-levels: Logging levels. This is an optional parameter.
The trigger fires when the specified log group receives records that match all of the following parameters: resource-ids, resource-types, stream-names, and log-levels. If a parameter is not specified, the trigger fires for any value of the parameter.

--invoke-container-id: Container ID.
--invoke-container-service-account-id: ID of the service account with permissions to invoke the container.
--retry-attempts: Number of invocation retries before the trigger moves a message to the dead-letter queue. This is an optional parameter. The values may range from 1 to 5. The default value is 1.
--retry-interval: Time to retry invoking the container if the current attempt fails. This is an optional parameter. The values may range from 10 to 60 seconds. The default value is 10 seconds.
--dlq-queue-id: Dead-letter queue ID. This is an optional parameter.
--dlq-service-account-id: ID of the service account with write permissions to the dead-letter queue. This is an optional parameter.

Result:

id: a1s5msktijh2********
folder_id: b1gmit33hgh2********
created_at: "2022-10-24T15:19:15.353909857Z"
name: logging-trigger
rule:
  logging:
    log_group_id: e23bidnftlh2********
    resource_type:
      - serverless.functions
    resource_id:
      - d4e1gpsgam78********
    stream_name:
      - test
    levels:
      - INFO
    batch_settings:
      size: "1"
      cutoff: 1s
    invoke_container:
      container_id: bba5jb38o8h2********
      service_account_id: aje03adgd2h2********
      retry_settings:
        retry_attempts: "1"
        interval: 10s
      dead_letter_queue:
        queue-id: yrn:yc:ymq:ru-central1:b1gmit33ngh2********:dlq
        service-account-id: aje3lebfemh2********
status: ACTIVE

Terraform allows you to quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. Configuration files store the infrastructure description in the HashiCorp Configuration Language (HCL). Terraform and its providers are distributed under the Business Source License.

For more information about the provider resources, see the documentation on the Terraform website or the mirror.

If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

If you don't have Terraform, install it and configure the Yandex Cloud provider.

To create a trigger for Cloud Logging:

In the configuration file, describe the trigger parameters:
```
resource "yandex_function_trigger" "my_trigger" {
  name = "<trigger_name>"
  container {
    id                 = "<container_ID>"
    service_account_id = "<service_account_ID>"
    retry_attempts     = "<number_of_retry_invocation_attempts>"
    retry_interval     = "<interval_between_retry_attempts>"
  }
  logging {
    group_id       = "<log_group_ID>"
    resource_types = [ "<resource_type>" ]
    resource_ids   = [ "<resource_ID>" ]
    stream_names   = [ "<logging_stream>" ]
    levels         = [ "logging_level", "logging_level" ]
    batch_cutoff   = "<maximum_wait_time>"
    batch_size     = "<message_batch_size>"
  }
  dlq {
   queue_id           = "<dead_letter_queue_ID>"
   service_account_id = "<service_account_ID>"
 }
}
```
Where:
- name: Trigger name. The name format is as follows:
  - The name must be from 3 to 63 characters long.
  - It may contain lowercase Latin letters, numbers, and hyphens.
  - The first character must be a letter and the last character cannot be a hyphen.
- container-name: Container parameters:
  - id: Container ID.
  - service_account_id: ID of the service account with rights to invoke the container.
  - retry_attempts: Number of invocation retries before the trigger moves a message to the dead letter queue. This is an optional parameter. The values may range from 1 to 5. The default value is 1.
  - retry_intervall: Time to retry invoking the container if the current attempt fails. This is an optional parameter. The values may range from 10 to 60 seconds. The default value is 10 seconds.
- logging: Trigger parameters:
  - group_id: ID of the log group that invokes the container when entries are added there.
  - resource_types: Types of resources, e.g., Cloud Functions functions. This is an optional parameter.
  - resource_ids: IDs of your resources or Yandex Cloud resources, e.g., Cloud Functions functions. This is an optional parameter.
  - stream_names: Log streams. This is an optional parameter.
  - levels: Logging levels. This is an optional parameter.
    
    A trigger fires when records are added to the specified log group that satisfy all of the following parameters: resource_ids, resource_types, stream_names, and levels. If a parameter is not specified, the trigger fires for any value of the parameter.
  - batch_cutoff: Maximum wait time. This is an optional parameter. The values may range from 1 to 60 seconds. The default value is 1 second. The trigger groups messages for a period not exceeding batch_cutoff and sends them to a container. The number of messages cannot exceed batch_size.
  - batch_size: Message batch size. This is an optional parameter. The values may range from 1 to 10. The default value is 1.
- dlq: Dead-letter queue message parameters:
  - queue_id: Dead-letter queue ID. This is an optional parameter.
  - service_account_id: ID of the service account with write permissions to the dead-letter queue. This is an optional parameter.
For more information about resource parameters in Terraform, see the provider documentation.
Create resources:
1. In the terminal, change to the folder where you edited the configuration file.
2. Make sure the configuration file is correct using the command:
```
terraform validate
```
  If the configuration is correct, the following message is returned:
```
Success! The configuration is valid.
```
3. Run the command:
```
terraform plan
```
  The terminal will display a list of resources with parameters. No changes are made at this step. If the configuration contains errors, Terraform will point them out.
4. Apply the configuration changes:
```
terraform apply
```
5. Confirm the changes: type yes in the terminal and press Enter.
Terraform will create all the required resources. You can check the new resources using the management console or this CLI command:
```
yc serverless trigger list
```

To create a trigger for Cloud Logging, use the create REST API method for the Trigger resource or the TriggerService/Create gRPC API call.

Checking the result

Make sure the trigger is working properly. To do this, view container logs that show information about invocations.

Creating a trigger for Cloud Logging that invokes a Serverless Containers container

Getting startedGetting started

Creating a triggerCreating a trigger

Checking the resultChecking the result

See alsoSee also

Was the article helpful?

Getting started

Creating a trigger

Checking the result

See also