Reports & exports

SutramX gives you reliability data in three forms: a weekly report email, uptime figures on every monitor (also available from the API), and exports you can download for spreadsheets, audits or your own tools.

Weekly reports#

The weekly report is an email summary of the last seven days across every monitor in the workspace. It's included on plans with weekly reports (Growth and Pro). See Plans & limits.

What's in the email#

The subject reads like "Your weekly SutramX report: 99.98% uptime". The email contains:

The report counts degraded checks as failed, and it doesn't exclude maintenance windows. Its uptime can therefore be slightly lower than the figure on each monitor's page. See Uptime math.

Who receives it and when#

• The report goes to the workspace owner's email address. Team members don't receive it.
• It covers the 7 days before it's sent and arrives about once a week. The schedule isn't tied to a fixed weekday.
• After an upgrade to a plan that includes weekly reports, the first one is sent within about a day.
• If sending fails, SutramX retries after 6 hours. After 3 failed attempts in a row, it waits for the next week.
• No reports are sent for a workspace that is scheduled for deletion.

Turn it on or off#

Weekly reports are on by default. To change that:

1. In the sidebar, open Alerts → On-call & escalation.
2. Under Notification Preferences, switch Weekly Reports off or on.

Only the workspace owner can change notification preferences. When the switch is off, each week is recorded as skipped instead of sent.

Preview and history#

Below the switches, Weekly Report Preview and History shows:

• A live preview of the next report: Checks, Failed Checks and Incidents for the last 7 days.
• Last sent and Next scheduled run.
• Recent weekly report history: each week's date range, status and send time. The statuses are sent, skipped, failed (will retry) and dead_letter (gave up for that week). Failed weeks show the error.

Click Refresh to reload the preview.

Uptime reports#

Every monitor's page shows uptime for the Last 24 hours, Last 7 days and Last 30 days. Click Show on Last 365 days to calculate the yearly figure. These figures:

• count degraded checks as up,
• leave out time when the monitor was paused or in a maintenance window, and
• are rounded down to 3 decimals, so 99.9996% never shows as 100%.

For a longer-term view across all monitors, with SLOs and error budgets, use Reliability insights. To share uptime publicly, publish a status page.

Get uptime from the API#

Use an API key (see REST API) to build your own uptime or SLA reports:

# Summary for the last 90 days (days: 1 up to your plan's uptime history, default 30)
curl -H "Authorization: Bearer $SUTRAMX_API_KEY" \
  "https://api.sutramx.com/stats/<monitor-id>/stats?days=90"

# Daily uptime for the last 90 days (days: 1 up to your plan's uptime history, default 90)
curl -H "Authorization: Bearer $SUTRAMX_API_KEY" \
  "https://api.sutramx.com/stats/<monitor-id>/uptime-history?days=90&tzOffsetMinutes=-330"

The summary returns uptime_percentage, total_checks, successful_checks, failed_checks and avg_response_time_ms. The daily history returns one entry per day that has checks:

[
  { "date": "2026-09-30", "uptime": 100, "checks": 1440 },
  { "date": "2026-10-01", "uptime": 99.861, "checks": 1440 }
]

tzOffsetMinutes sets where each day starts. It uses the JavaScript convention (UTC minus local time, so India is -330 and New York in summer is 240) and accepts −840 to 840. You can pass an IANA timeZone instead, for example timeZone=America/New_York, which also handles daylight saving time. Uptime history goes back 365 days on Starter and 730 days on Growth and Pro. A range with no checks has null uptime rather than 100.

Export incidents#

1. Open Incidents in the sidebar.
2. Set any filters you want: status, monitor, date range or search.
3. Click Export CSV or Export JSON.

The file (incidents-YYYY-MM-DD.csv or .json) contains the incidents matching your filters, newest first, up to 5,000 per export. For a longer history, narrow the date range and export in parts.

CSV columns:

id, monitor_name, monitor_url, started_at, resolved_at, duration_seconds, status,
alert_suppressed, suppression_reason, is_flapping, confirmed_from, acknowledged_at,
acknowledged_by, resolved_manually, postmortem

status is ongoing or resolved. confirmed_from lists the confirming regions separated by ; . The JSON export contains exported_at and an incidents array with the same records in more detail.

Through the API:

curl -H "Authorization: Bearer $SUTRAMX_API_KEY" \
  "https://api.sutramx.com/incidents/export?format=csv&status=resolved&from=2026-09-01T00:00:00Z&to=2026-10-01T00:00:00Z" \
  -o incidents.csv

status accepts all, ongoing, resolved, suppressed or acknowledged. You can also pass monitor_id and q (search).

Export check history#

Each monitor's page has a Check history section:

1. Optionally filter by Location (probe region) and Result: Problems only, All results, Up, Degraded or Down.
2. Click Export CSV.

The file <monitor-name>-checks.csv contains the most recent 50,000 checks matching the filters, oldest first:

checked_at,region,status,status_code,response_time_ms,error_type,error_message
2026-10-01T09:00:00.123456Z,fra1,up,200,182,,
2026-10-01T09:01:00.098311Z,usa-az-probe,down,503,,status_code,HTTP 503

Text cells that start with =, +, - or @ get a leading ' so spreadsheet apps don't run them as formulas.

To export a specific time range, call the API with ISO 8601 from and to:

curl -H "Authorization: Bearer $SUTRAMX_API_KEY" \
  "https://api.sutramx.com/monitors/<monitor-id>/checks.csv?from=2026-09-01T00:00:00Z&to=2026-09-08T00:00:00Z&status=down" \
  -o checks.csv

If more than 50,000 checks match, the response has the header X-Export-Truncated: true. Split the range into smaller pieces. Each user can run up to 20 check exports per 15 minutes.

Export workspace data#

The workspace owner can download a JSON copy of the whole workspace: profile, team and pending invites, monitors, monitor groups, status pages, maintenance windows, SLOs, dependencies, alert recipients, integrations (types only), incidents with their timelines, daily uptime history, recent raw checks (up to 50,000) and the audit log.

1. Open Team members in the sidebar and find Export workspace data, or go to Account → Settings and find Danger zone.
2. Click Export data.
3. On the Team members page, click Download export when it appears. From Account settings, the download starts on its own.

The download link is valid for 1 hour. Passwords, API keys, tokens, two-factor secrets and integration credentials are never included. Secret-looking fields and request header values show [redacted]. All timestamps are UTC. Each export is recorded in the workspace activity log as Exported workspace data. You can run up to 5 exports per hour.

Other downloads#

• Website health reports have an Issues CSV download for each crawl. See Website health.
• Postmortems and incident timelines are on each incident's page. See Incidents.

Common questions#

Why doesn't the weekly report match my monitor page uptime? The report counts degraded checks as failures and includes maintenance time. The monitor page doesn't.

Can team members get the weekly report? Not today. It's sent to the workspace owner only.

I'm on Free. Can I still export? Yes. Incident, check history and workspace exports work on every plan. Weekly report emails need a plan that includes them.