Configuration: Service Levels: Reports

Configuration: Service Levels: Reports

Overview

Use this page to create and manage per-customer SLA availability reports. A report is a recurring, branded PDF that summarizes a customer's availability over the past month and is delivered by mail to a chosen list of recipients, computed from that customer's uptime checks. It turns raw uptime monitoring data into a recurring artifact you can hand to a customer instead of exporting numbers by hand every month.

Before a report can produce meaningful output, the customer needs uptime checks already running on Uptime Monitoring: Checks and the availability norms it is measured against defined on Configuration: Service Levels: Objectives. Once a report exists and runs on its schedule, its output is the mailed PDF itself, plus a run history you can review from the report's own preview view.

On this page you switch between two tabs: Reports, where you create, open, edit, and delete individual report configurations, and Branding profiles, where you manage the reusable PDF styling that reports apply when they generate.

Key concepts

  • report - A configured, recurring monthly SLA availability PDF for one customer, generated from its uptime checks and mailed to a list of recipients. (related: Uptime Monitoring: Checks)
  • branding profile - A reusable set of PDF styling, such as logo and colors, that a report applies when it generates its output.
  • norms - The availability targets a report measures the customer's uptime checks against before stating whether the period met the goal. (related: Configuration: Service Levels: Objectives)

When to use it

  • You need to hand a customer recurring proof of the availability they experienced, as a monthly PDF instead of a manual export.
  • You are setting up automated mail delivery of SLA availability figures for a new customer.
  • You want consistent, branded PDF output across several customer reports and need to set up the styling once.
  • You are checking whether a customer's report has actually run recently, using the Last run column.
  • A customer's sites, recipients, or schedule changed and the report needs updating to match.

Before you begin

  • The customer has at least one uptime check already configured and running, created on Uptime Monitoring: Checks.
  • The availability norms the report should measure against are defined on Configuration: Service Levels: Objectives.
  • A mail-capable notification account exists on Configuration: Notification Accounts so the PDF can be delivered to recipients.
  • If the report needs specific styling, a branding profile is created on the Branding profiles tab of this page before you create the report.
  • Your account has configuration access to Service Levels; the Configuration area is visible in the left navigation.

Common workflows

Create a new SLA availability report for a customer

Persona: Service Levels administrator

  1. Select New report on the Reports tab.
    • Expect: A creation flow opens, prompting you to choose the customer, its uptime checks and availability norms, a branding profile, and the recipients who should receive the mailed PDF.
  2. Choose the customer, its uptime checks, the availability norms, a branding profile, and the recipient list.
    • Expect: The report is scoped to that customer's monitored sites, measured against the chosen norms, and styled ready to mail to the recipients you added.
  3. Save the report.
    • Expect: The new report appears as a row on the Reports tab, the tab's badge count increases by one, and Last run stays blank until the first scheduled generation completes.

Verify: Confirm the new row shows the correct Customer and Sites, then revisit the page after the schedule's next run to confirm Last run has populated with a date; if it stays blank past the scheduled time, revisit the report's Schedule and its uptime checks.

Steps

Step 1

Open the Service Levels - Reports page under Configuration.

Expected result: The page loads on the Reports tab showing an empty table with columns for Report, Customer, Sites, Schedule, Last run and Actions, and the message "No reports yet. Create one per customer: its uptime checks, norms, branding and recipients."

This is the starting point for setting up the first SLA availability report for a customer.

  • The Reports tab is active by default; its badge and the Branding profiles tab's badge both show 0 until you create a report or profile.
  • Use New report to start creating a report, or Refresh to reload the list from the server. Configuration: Service Levels: Reports - step 1

Tabs on this page

  • Reports - Lists every configured SLA availability report, one row per customer report, and is where you create, open, edit, or delete them.
    • Report, Customer, Sites, Schedule, Last run, and an Actions column with row-level icons.
  • Branding profiles - Holds the reusable PDF styling profiles, such as logo and colors, that reports apply when they generate their output.
    • A badge shows how many branding profiles exist; switch here before creating a report that needs specific styling.

Column reference

Column What it shows How to read it
Report Identifies the specific report configuration, typically named for the customer or the purpose it serves. Use this name to tell apart multiple reports when a customer has more than one, for example separate reports for different site groups.
Customer Shows which customer the report's availability figures belong to. Confirm this matches the customer you intended before trusting the report's figures or recipients.
Sites Shows which or how many monitored sites are included in the report's availability calculation. A higher count means the report aggregates availability across more monitored sites for that customer; check it matches the scope you expect.
Schedule Shows the recurrence on which the report is generated and mailed. Tells you when the next PDF will go out; a schedule far in the future explains why Last run is still empty.
Last run Shows the date of the most recent successful report generation and mail delivery. A blank value means the report has not completed its first scheduled run yet; a recent date confirms delivery is working.
Actions Holds the row-level icons used to open, edit, or delete that report. These icons appear once at least one report exists; use them to open the report's preview and history, change its configuration, or remove it.

Controls reference

Refresh

Reloads the active tab's list from the server.

When to use: After creating, editing, or deleting a report or branding profile elsewhere, or when you suspect the list is out of date.

Side effects: Read-only: re-fetches data and makes no changes.

New report

Opens the flow to create a new SLA availability report.

When to use: When a customer needs a recurring mailed PDF availability report that does not exist yet.

Side effects: Mutating once you complete and save it: it creates a report entry that still needs a customer, its uptime checks, norms, branding profile, and recipients configured.

Open report

Opens the report's preview, send and history view.

When to use: To check how the current PDF looks, send it on demand, or review when it was previously generated and mailed.

Side effects: Read-only unless you trigger a send action from inside that view.

Edit report

Opens the report's configuration for changes.

When to use: When the customer's sites, schedule, norms, branding profile, or recipients need to change.

Side effects: Mutating: saved changes apply starting with the report's next scheduled run.

Delete report

Removes the report configuration.

When to use: When a customer no longer needs this recurring report.

Side effects: Mutating and destructive: opens a Delete report? confirmation first; once confirmed, the report and its schedule stop permanently.

Verify the result

After you complete the creation flow for a report, it appears as a row on the Reports tab showing the Customer, the Sites it covers, and its Schedule. Once the first scheduled generation and mail completes, Last run shows a date; a blank Last run means the first run has not happened yet. The Actions column shows icons to open, edit, or delete that report. If the row never appears after saving, the creation flow was not completed; if it appears but never runs, check its Schedule and confirm the customer's uptime checks are producing data.

Troubleshooting

  • Symptom: The Reports table still shows "No reports yet" after you believe you created one. Fix: Select Refresh to reload the list, and confirm the creation flow was saved rather than just started.
  • Symptom: A report's Last run column stays empty. Fix: Check the report's Schedule for when it is next due, and confirm the customer has at least one active uptime check feeding it data.
  • Symptom: A generated PDF doesn't show the styling you expect. Fix: Switch to the Branding profiles tab and confirm the report references a branding profile with the logo and colors you intended.
  • Symptom: Clicking the delete icon on a report row seems to do nothing. Fix: Confirm the removal in the Delete report? dialog that opens; the report is only removed after you confirm.
  • Symptom: Both tab badges stay at 0 even though the customer already has uptime checks configured. Fix: Badges count reports and branding profiles only, not the underlying uptime checks; select New report to create a report explicitly.
Was this article helpful?
0 out of 0 found this helpful