Skip to content

Exporting Your Data

Incidents & Maintenance 8 min read
On this page

Uptimia gives you three shapes of export:

  • A filtered CSV of a whole list
  • A self-contained PDF or HTML document for one incident or one check
  • A public link to that same document, which anyone can open without signing in

For recurring emailed summaries, see Scheduled Reports instead.

What You Can Export #

ScreenCSV of the filtered listOne item as a filePublic link
Incidents → HistoryExport CSVDownload PDF, Download HTMLCreate public link
Incidents → Active—Download PDF, Download HTMLCreate public link
Logs (Monitoring Logs)Export CSVDownload PDF, Download HTMLCreate Public Link
Reports—Export PDF, Export HTML, Export CSVCreate Public Link

The Active view has no CSV button, because a CSV export needs a date window and Active is a live view. Use its History → link to reach the exportable list.

Exporting Incidents #

All 12 monitor families open incidents: Uptime, Transaction, API, Heartbeat, Server, Speed, Real User, SSL, Domain, DNS, Security and Blacklist. An unfiltered export spans every one of those families except Real User. RUM incidents are included only when you select RUM monitors in the Specific monitors pill.

The Filtered CSV #

  1. Go to Incidents → History.
  2. Set the date-range picker. For a subset, also set the Specific monitors pill, a checkbox menu grouped by monitor type.
  3. Click Export CSV.

The date range and the Specific monitors pill are the only filters the file obeys. The search box, the All / Ongoing / Resolved chips and the All types dropdown narrow what you see on screen, not what you download.

The Incident History page in Uptimia with the Export CSV button in the header, the four incident KPI tiles, and the date-range picker leading the filter row beneath them.Enlarge

The file is named UptimiaIncidents.csv and carries 15 columns: Name, Type, Alerts sent, Error, Start Time, End Time, Duration, Alerts accepted, Alerts failed, Alerts skipped, Opened by, Closed by manual incident, Availability impact, Counted seconds, Impact reason. Timestamps render in your account's time zone, and the two time headers name it. A long date range downloads in full.

  • Alerts accepted, Alerts failed and Alerts skipped come from the delivery record and read 0 for an incident with no tracked delivery.
  • Opened by names the person who opened a manual incident and is empty for an automatic one. Closed by manual incident reads Yes for an automatic incident that a manual incident closed.
  • Availability impact is full, none or partial. Counted seconds is how much of the incident counts as downtime, while Duration stays the recorded length. Impact reason is the reason given when the incident was set not to count in full.

The file matches the History list, so it leaves out incidents belonging to a currently paused monitor. Pausing hides that monitor's past incidents from the account-wide views and from this file. A member limited to specific monitor groups exports only the monitors in their scope.

One Incident as a Document #

Open an incident from Incidents → History or Incidents → Active to see its full page; a grouped incident opens its group page instead. The page header carries an Export dropdown:

  • Download PDF: Root-Cause-Analysis.pdf
  • Download HTML: Root-Cause-Analysis.html
  • Download alert deliveries (CSV): one row per recipient for each alert sent for the incident
  • Create public link: publishes the same HTML at a public URL

Create public link appears only for members who can manage monitoring: Owner, Admin and Editor. A Read-only member sees the first three items only. It is also missing when the incident's availability impact is set to none, because nothing is left to publish.

Each working public link shows under the page header with Copy and Revoke buttons, for the same three roles. See Public Links and How Long They Last below.

A resolved incident page with its public link shown under the header, next to Copy and Revoke buttons.Enlarge
The Export dropdown open in a resolved incident's page header, showing Download PDF, Download HTML, Download alert deliveries (CSV) and Create public link beside Open monitor and Post status update.Enlarge

Exporting Monitoring Logs #

The check log holds one row per check per probe: the monitor, the probe, the status, the time and the response time. It lives on the Logs item in the sidebar.

The Filtered CSV #

Set the search box, the All checks or Failed only tab, the type, monitor and location dropdowns, and the date range, then click Export CSV. The file is UptimiaLogs.csv with 6 columns: Name, Type, Location, Time, Status, Duration. One export returns at most 100,000 rows. Narrow the date range or the monitor filter if your filters match more than that.

The Logs page with its summary line of checks, failures and monitors down now, the All checks and Failed only tabs, the search box and type, monitor, location and date filters beside the Export CSV button, and the five-column table of individual checks.Enlarge

One Check as a Document #

Click a row to open the check-detail slide-over, then use its Export dropdown: Download PDF, Download HTML, Create Public Link. Both files are named Monitoring-Log. The menu at the end of the row (the three dots) offers Download PDF and Download HTML as a shortcut, without the public-link item.

The check detail slide-over with its Export dropdown open, showing Download PDF, Download HTML and Create Public Link for one failed check.Enlarge

11 of the 12 families produce exportable check documents: Uptime, SSL, Domain, Security, Speed, Transaction, Heartbeat, Server, API, DNS and Blacklist. Real User monitors collect no check rows at all, so they have no entry in the Logs page's All types filter and no export.

Family-Specific Behavior #

FamilyWhat to expect
ServerRaw samples are kept for 24 hours and then rolled up into hourly averages. Exporting a sample older than that returns "Log entry not found". That is normal for this family, and only this family.
HeartbeatHeartbeat pings appear only when heartbeat is the only type in the monitor filter. They never show up in a mixed view or a mixed CSV. Every heartbeat document redacts the ping URL to its last 4 characters. It has to: the ping URL is the monitor's only credential, and the public-link version needs no login.
BlacklistThe per-list table lists the zones that answered listed, informational or unreadable, plus any zone that published a positive reputation code (shown as whitelisted). Clean answers are counted in the sweep summary but not listed one by one, so an export cannot prove which zones were clean.
DNSOne row per sweep. Each sweep runs from a single probe, and that probe rotates through the monitor's location pool. Both the row and the document name the probe that ran the sweep. The sweep summary carries queries, nameservers answered, open changes, health issues and query errors.
SecurityOne row per scan. The CSV Status column carries the same word as the Logs page: Infected, the number of open issues (for example 2 issues), Unknown, No issues, Clean or Not checked.
Real UserNo check log, therefore no export. Use a scheduled report for RUM summaries.

A public link publishes a static HTML copy of one incident or one check at an address anyone can open: no sign-in, no password, no view limit.

Incident and check-log public links have no expiry date, and the 30-day cleanup that clears report snapshots never touches them. The URL is unguessable, a random 32-character hash.

Incident links can be revoked. On the incident page, click Revoke next to the link and confirm. Anyone who opens the URL then gets a page-not-found error. You cannot undo a revoke, but you can create a new link afterwards. Revoking needs the Owner, Admin or Editor role, like creating a link.

An incident link also stops working when:

  • you delete the incident, or delete its monitor
  • Uptimia deletes the incident because it is older than your plan keeps incidents
  • you set its availability impact to none or partial. Setting it back to full does not restore the link, so create a new one. A new link for a partial incident shows only the counted stretch, with no evidence or alert events.

Warning: Check-log public links cannot be revoked, and neither can incident links created before links were recorded (these do not appear under the incident header). Deleting the monitor does not remove them either. Treat such a link as permanently published, and send a PDF instead when the recipient does not need a live URL. If you need one taken down, contact support with the full URL.

Report public links are HTML snapshots, and a daily cleanup deletes any snapshot older than 30 days. A report link stops working after that; a downloaded PDF, HTML or CSV does not. Scheduled Reports covers report exports in full.

How Far Back an Export Can Reach #

Your plan sets the readable history window: 7 days on Free, 30 on the trial, 90 on Basic, 365 on Professional, 730 on Enterprise. Data and Log Retention lists those numbers and explains how upgrading changes them.

Charts and exports behave differently, which is why two screens can disagree:

  • Ask an Uptime, Speed or Security history chart for a date earlier than your plan allows, and it moves the start date forward to your plan's earliest date. You get the shorter window with no error. The other families' monitor pages do not move your start date, so they can show rows older than your plan's window.
  • CSV exports never move your start date. They return every row still stored in the range you asked for. On a short-window plan that can be more than an Uptime, Speed or Security monitor page shows you.

Uptimia eventually deletes old rows, but never sooner than your plan's window. Export before the data ages out and keep the file.

Choosing a Format #

You want toUse
Analyze in a spreadsheet, or re-import elsewhereCSV from the list view
Hand one incident to a customer or an auditorDownload PDF
Attach one check result to a ticketDownload HTML
Let someone without an account read it in a browserA public link (you can revoke an incident link; a check link is permanent)
Automate a nightly pullThe Uptimia API

Was this helpful?

Your answer helps the team improve this article.

Still need help?

Uptimia Bot answers right away and passes you to the team when it can't.

Source: https://help.uptimia.com/help/a/exporting-your-data