Skip to content
Go to dashboard

7.10Screenshots of failed checks

When a check fails, obsrvly takes a screenshot of the page at that moment. It shows the part of the page a visitor would see without scrolling. Checks that pass get no screenshot.

  • Open the failed check in Recent checks. The screenshot has the caption page at the moment of failure.
  • obsrvly keeps screenshots for 14 days. After that, you see "screenshot no longer available".
  • If the image does not open, you see "screenshot could not be loaded". Try again later.
  • Password fields and fields with a secret are always covered. If a secret could still be seen, obsrvly keeps no screenshot.

When there is no screenshot, the dashboard says "No screenshot:" and one of these reasons:

ReasonWhat it means
"screenshots are not set up."Screenshots are not available for this check.
"no page had loaded."The check failed before any page opened, so there was nothing to capture.
"the page was showing a secret."obsrvly kept no image, to keep the secret hidden.
"the image was too large to keep."The image was too large to store.
"the page could not be captured."obsrvly could not take the image.
"the image could not be stored."obsrvly took the image but could not save it.

Through the API#

This call is a plain GET. Use the IDs of the monitor and of the failed check.

Get a screenshot link
MONITOR="<monitor-id>"
EXECUTION="<execution-id>"
MONITORS=https://www.obsrvly.com/api/gw/result/v1/monitors
curl -s "$MONITORS/$MONITOR/executions/$EXECUTION/screenshot" \
  -H "Authorization: Bearer $OBSRVLY_KEY"
# {"url": "https://...", "expires_at": "..."}
  • The link works for 5 minutes and needs no key. Treat it like a password until it expires.
  • A 404 (no screenshot) means the check passed, the page showed a secret, the screenshot is older than 14 days, or the check is not in your team.

Last updated