Skip to main content

Documentation Index

Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

SLA reporting turns monitored availability into scheduled reports for operations review, customer updates, and service accountability. Reports can cover all hours or a business-hours schedule, and they can be generated daily, weekly, or monthly.

​
Prerequisites

  • You have access to the sites that should appear in the report.
  • You know the SLA target and whether availability should be measured across all hours or business hours.
  • You have a notification group ready if reports should be delivered automatically.

​
Schedule Options

FrequencyBehavior
DailyRuns at 8:00 AM and covers the previous day.
WeeklyRuns on the selected day and covers the past week.
MonthlyRuns on the selected day. If a month is shorter than that day, SDX uses the last day of the month.
Schedules include a timezone, SLA target, selected sites, notification group, and calculation mode.

​
Business Hours

Reports can calculate uptime across all hours or only within a business-hours schedule. Use business hours when service accountability should match staffed operating windows. Use all hours when the service is expected to be continuously available.

​
Create a Report Schedule

  1. Open SLA and select Schedules.
  2. Create a schedule with a clear name.
  3. Select daily, weekly, or monthly frequency.
  4. Choose the sites to include. You can use tag grouping to keep site selection scalable.
  5. Set the SLA target.
  6. Choose all-hours or business-hours calculation.
  7. Optionally show only breached sites.
  8. Optionally ignore power outages when that matches your reporting policy.
  9. Select a notification group if the report should be delivered automatically.
  10. Save the schedule.

​
Generated Reports

Generated SLA reports show the report name, uptime percentage, SLA target, site count, reporting period, and whether the report used all hours or business hours. Reports can be shared with a generated link or downloaded as a PDF. You can also run a schedule on demand when you need a report outside its normal cadence.

​
Advanced Use Cases

Use tag-based site selection for customer, region, or service-tier reports. This keeps reports accurate when sites are added or removed from a group. Use separate schedules for internal operations and customer-facing reports. Internal reports may include every site and every outage, while customer-facing reports may use business hours, breached-site filters, or specific site groups.
SLA reports depend on monitoring history. For live incident response, use Fault Logging and Notifications.