App parts and heartbeats

​

The Engine room

• One row per part: a server instance that sends heartbeats, or a job from your app map with its name.
• How often it reports, like “every 5 min” or “every hour”.
• The last sign, like “last sign 2 min ago”, or “never reported”.
• Twelve dots for the last 12 hours. A dot is empty if the part sent nothing in that hour.
• A mark only when a part is late or silent.
• At the top: how many parts are running, for example “3 of 4 running”.

​

Late and silent

​

A heartbeat is no proof of the whole app

• Missing heartbeats are a monitoring gap, not an outage.
• A confirmed outage needs a failed reachability check.

​

When a part goes silent

• One part goes silent while the rest still sends: you get one email and a banner. It ends when the part sends again.
• The whole app goes silent: a case opens, “Your app stopped sending heartbeats”. It closes by itself with the next heartbeat.
• A scheduled job misses two periods: a case opens, for example “Job has not reported for 2 periods”. It closes when the job reports again. This runs in production only.

​

How scheduled jobs report

everydeck.heartbeat(3600, { job: "nightly_import" });

select cron.schedule('nightly_import', '0 3 * * *',
  $$ select everydeck_outbox.run_job('nightly_import', $job$ call import_listings() $job$) $$);

​

Schedules outside your app

• the secret EVERYDECK_SERVER_KEY,
• the variable EVERYDECK_URL.

- name: everydeck check-in
  if: always()
  continue-on-error: true
  env:
    EVERYDECK_URL: ${{ vars.EVERYDECK_URL }}
    EVERYDECK_SERVER_KEY: ${{ secrets.EVERYDECK_SERVER_KEY }}
    STATUS: ${{ job.status == 'success' && 'ok' || 'error' }}
  run: 'curl -fsS --max-time 10 -X POST "$EVERYDECK_URL/v1/jobs/nightly_import/check-in?status=$STATUS" -H "authorization: Bearer $EVERYDECK_SERVER_KEY"'

​

When you remove everydeck

​

What there is not

• No history longer than 12 hours.
• No parts without an SDK heartbeat.
• A failed job run opens no case of its own. Only a silent job does.