Skip to main content
Version: 2026.8.1

Alerting

Two kinds of "tell me when something happens" need different plumbing. Cobblr can notify you about things that happen inside a workspace. Telling you the box itself is down has to come from outside the box, because a down instance cannot send its own alarm.

  1. Is the instance up? Point an uptime monitor on another machine at https://<your-address>/api/v1/healthz.
  2. Did something happen in a workspace? Wire a Discord or Slack webhook in the app's Notifications.

Is the instance up: watch from outside​

  1. Use the address you actually browse Cobblr at. The stack binds the raw web port to loopback in every HTTPS mode, so :8088 answers another machine only on the plain-HTTP fast path.

    https://<your-address>/api/v1/healthz

  2. Point an uptime monitor at it from somewhere other than the Cobblr box, so a total outage still reaches you. Any uptime service that fetches a URL on an interval and notifies on failure works: a hosted checker, or a small script on a second machine that curls the endpoint and posts to a webhook when it fails.

  3. Or run a cron job on another machine. A minimal version:

    curl -fsS --max-time 10 http://<your-box>:8088/api/v1/healthz > /dev/null \
      || curl -s -X POST -H 'Content-Type: application/json' \
           -d '{"content":"Cobblr health check failed"}' \
           "$DISCORD_WEBHOOK_URL"
  • What it returns: {"ok": true, ...} while the api is serving (see Health and status).
  • Why -f: it makes curl fail on a non-200, so an api that is down (or a box that is unreachable) triggers the notification.
  • Where to send it: a Discord or Slack incoming webhook is the quick target. Any webhook URL works.

Things that happen inside a workspace​

For events Cobblr itself produces, such as an order arriving or stock dropping below its minimum, use Cobblr's own notifications.

  1. Point a Discord or Slack incoming webhook at the matching channel in the app.
  2. Choose which events go there.
  • Per-event, so operational things can go to a channel and the rest can stay in the app.
  • Full setup is in Notifications.
  • Workspace activity only. These are not for whether the server is alive. That is the outside check above.

What does not phone home​

Cobblr sends nothing on its own.

  • No telemetry, no error reporting, and no update check calling out to any service.
  • Every alert described here is one you wire up and point at a destination you control, which is also why the uptime check has to be something you set up rather than something that already exists.