Snapshots and sharing
Snapshots and sharing
Freeze a dashboard at a moment in time and hand it to someone without an account.
A snapshot captures the rendered results, not the queries. It keeps working after retention drops the underlying events, which is exactly what a post-incident review needs.
cURL
curl -X POST https://api.logstreem.com/v1/dashboards/dsh_4a81e0c3f6a5b2d1e0c9/snapshots \
-H "Authorization: Bearer $LOGSTREEM_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name": "INC-2317 checkout outage",
"time_range": { "start": "2026-09-05T17:40:00Z", "end": "2026-09-05T19:10:00Z" },
"visibility": "link",
"expires_at": "2026-12-05T00:00:00Z"
}'visibility | Who can open it |
|---|---|
private | Organisation members only |
link | Anyone with the URL — unguessable, not secret |
public | Anyone, and indexable. Use for status pages only |
Snapshots embed the data
A snapshot contains the rendered rows, so a
link snapshot of a dashboard showing user identifiers hands those identifiers to anyone with the URL. Set expires_at, and check what the charts actually contain before sharing.