Deploy markers

A dashed line on the strips at the moment of a release, posted from CI.

What a marker is

A version and a moment, drawn as a dashed line with the version on every strip in the dashboard. Hovering a bucket that holds one names it. A marker can carry a link (a release, a commit) and a note, and can be limited to some monitors. Markers are kept for a year.

Posting one from CI

Make a key under Account, API keys, with write access and, if you like, reaching only the page in question. Then, after a release:

curl -X POST https://statoss.com/api/v1/pages/PAGE_ID/deploys \
  -H "Authorization: Bearer sk_..." \
  -H "Content-Type: application/json" \
  -d '{"version": "v2.14.0", "url": "https://github.com/example/api/releases/tag/v2.14.0"}'

The page id comes from GET /api/v1/pages, or from the address bar in the dashboard. In GitHub Actions, put the key in a repository secret and post with github.sha or the tag as the version. The API reference has every field.

On the public page

Markers always show in the dashboard. Under Settings, Appearance, "Draw deploy markers on the public page" shows them to visitors too, versions included.

Deploys close together are drawn as one line: within about 45 minutes on the 24-hour view, five hours on 7 days, three days on 90 days and eleven on the year. The line is the biggest release among them, a major version before a minor one before a patch, and the latest among equals. Pointing at a bar names every deploy in it.