Contact UsGet started
© 2024 Iron Hive LLC Belgrade

Creating a trigger that will send messages to a Serverless Containers container from a Yandex IoT Core broker topic

Written by
Updated at October 17, 2024

Create a trigger for an Yandex IoT Core broker topic and process message copies using a Serverless Containers container.

Warning

The trigger must be in the same cloud as the broker whose topic it reads messages from.

Getting started

To create a trigger, you need:

  • A container that the trigger will invoke. If you do not have a container:

  • (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.

  • Broker from the topic of which the trigger will collect message copies. If you do not have a broker, create one.

Creating a trigger

Note

The trigger is initiated within 5 minutes of being created.

  1. In the management console, select the folder where you want to create a trigger.

  2. Open Serverless Containers.

  3. In the left-hand panel, select Triggers.

  4. Click Create trigger.

  5. Under Basic settings:

    • Enter a name and description for the trigger.
    • In the Type field, select IoT Core (broker).
    • In the Launched resource field, select Container.

  6. Under IoT Core message settings:

    • In the Broker field, specify the broker.
    • (Optional) In the MQTT topic field, specify an MQTT topic. If no MQTT topic is set, the trigger will fire for all broker topics.

  7. 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.

  8. Under Container settings, select a container and specify a service account to invoke it under.

  9. (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.

  10. Optionally, under Dead Letter Queue settings, select the dead-letter queue and the service account with write permissions for this queue.

  11. 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 iot-broker \
  --name <trigger_name> \
  --broker-id <broker_ID> \
  --mqtt-topic '<MQTT_topic>' \
  --batch-size <message_batch_size> \
  --batch-cutoff <maximum_wait_time> \
  --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.
  • --broker-id: Broker ID.
  • --mqtt-topic: MQTT topic you want to create a trigger for. This is an optional parameter. If this parameter is skipped, the trigger will fire for all broker topics.
  • --batch-size: Size of the message batch from MQTT topics. This is an optional parameter. The values may range from 1 to 10. The default value is 1.
  • --batch-cutoff: Maximum waiting 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.
  • --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: iot-broker-trigger
rule:
  iot_broker_message:
    broker_id: arenou2oj4h2********
    mqtt_topic: topic-for-broker
    batch_settings:
      size: "1"
      cutoff: 0s
    invoke_container:
      container_id: bba5jb38o8h2********
      service_account_id: aje3932acdh2********
      retry_settings:
        retry_attempts: "1"
        interval: 10s
status: ACTIVE

To create a trigger for Yandex IoT Core, 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.

See also

Previous
Device
Next
Creating a trigger for budgets