Skip to content
Go to dashboard

3.8Deploy markers

A deploy marker records when you shipped. obsrvly draws it as a line on the response-time charts, so a slowdown or an outage right after a deploy is easy to see.

A marker is for one monitor, or for all of your team's monitors.

  • A marker for one monitor shows on that monitor's chart, and on the overview chart while that monitor is in it (a tag filter can leave it out). It is a solid line.
  • A marker for all monitors shows on every monitor's chart and on the overview chart. It is a dashed line.

Hover over the small flag at the top of a line to see what was deployed and when. If the marker has a link, select it to open the commit, release or build. Markers that are very close together share one line, and the flag shows how many there are.

In the dashboard#

  1. Open the monitor.
  2. Above the response-time chart, select mark deploy.
  3. Type what shipped, for example v1.4.2 or a commit. This is required.
  4. Optionally, add a link that starts with http:// or https://.
  5. Choose this monitor or all monitors.
  6. Select mark. The marker is set to now.

To see the markers of the last 30 days, select deploys next to mark deploy. The list shows this monitor's markers and the ones for all monitors.

Delete a marker#

Only a team owner can delete a marker (14.3).

  1. Open the monitor and select deploys.
  2. Select the bin icon next to the marker.

Members do not see the bin icon. Deleting a monitor also deletes its own markers. Markers for all monitors stay.

From CI, with an API key#

Post a marker from your deploy pipeline with an API key. Chapter 13 shows how to create one and set OBSRVLY_KEY.

Mark a deploy from CI
bash
API=https://www.obsrvly.com/api/gw
curl -s "$API/result/obsrvly.v1.ResultService/CreateDeployMarker" \
  -H "Authorization: Bearer $OBSRVLY_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"label\": \"$GIT_SHA\",
       \"url\": \"https://github.com/acme/app/commit/$GIT_SHA\"}"

The answer is the new marker: {"marker": {"id": "…", "label": "…", "at": "…", …}}.

  • label is required. It is what was deployed. It cannot have a new line.
  • url is optional. It must be an http or https address.
  • monitorId makes it a marker for one monitor. Leave it out to put it on every chart.
  • at is when the deploy happened, in RFC 3339, for example 2026-10-30T09:15:00Z. Leave it out to use now. It can be at most a few minutes in the future.
  • The monitor page's deploys list has the same command with the monitor's ID filled in.

Other calls:

  • ListDeployMarkers lists markers, newest first. Send start and end (RFC 3339) for a range. Without them you get the last 30 days. Add monitorId for one monitor's markers and the ones for all monitors.
  • DeleteDeployMarker with {"id": "<marker-id>"} deletes one. It needs an owner signed in to the dashboard. An API key or a member gets permission_denied ("only a team owner can delete a deploy marker").

If a request is refused, the error message says why, for example label required or url must be an http or https address.

Last updated