Production Pulse · 1 / 8

Start with a heartbeat

Begin Production Pulse with a document, an actor and a heartbeat timer, composed across three small files. Each later lesson extends this same integration.

YOUR TASK

Make this happen

4 steps

Keep the integration identity com.academy.monitor, version 1.0.0 and SDK 2.0.
Add integration_actor_timer.heartbeat to the timers list in actor.cococo.
Add integration_actor_timer.heartbeat with name heartbeat, schedule { every = "5m" } and source "return { alive = true }".
Choose Check solution and pass all local model-schema checks.

THE IDEA BEHIND IT

Build on the working integration

Start with the previous solution. Add the next capability in actor.cococo, timer.cococo. Connect the new components through their parent lists; supplied scripts and contracts remain read-only fixtures.

A document, not a deployment

Virtual resources are typed building blocks. Referencing a timer from actor.timers includes it in the integration document. Nothing is installed by this exercise.

What a heartbeat means

On the platform, the timer runs its source on schedule. This first source returns an alive value; it does not send a signal or prove that an external service is healthy. We will add an outbound signal later.

Compose named components

main.cococo connects the document to integration_actor.monitor. In actor.cococo, connect the named heartbeat timer. Each block is a typed local value: only referenced components become part of the integration, and they do not deploy independently.

Checks cover structure and lesson requirements. Scripts and platform behaviour are not executed.

Actor and Action reference ↗Schema client reference ↗

Read the starter files

main.cococo

integration_document "monitor" {
  integrationId = "com.academy.monitor"
  sdkVersion = "2.0"
  version = "1.0.0"
  description = "A small heartbeat integration"
  actor = integration_actor.monitor
}

actor.cococo

integration_actor "monitor" {
  timers = []
}

timer.cococo

integration_actor_timer "heartbeat" {
  name = "heartbeat"
  # TODO: add schedule — see the task above.
  # TODO: add source — see the task above.
}

Supplied scripts and pinned contracts (read-only)

These fixtures explain the runtime behaviour being composed. They are included in validation but are not executed. The generated API definition is supplied, not an XML authoring task.

scripts/heartbeat.lua

return { alive = true }