How do an alert and a status report differ?
A monitor can record a failure and affect a linked status page component, such as “File uploads.” A written status report is a separate update you publish. Use it to tell visitors what they can still do and when you expect to post more information. You can write a report even for a problem the monitor did not see.
Who keeps the status page running when the app is down?
With hosted OpenStatus the provider runs the service. If you host the status page yourself, keep it somewhere that can still answer when your app is unavailable. The documented status-page-only installation leaves out automated monitoring. It is suitable when checks are run separately and someone can write the incident updates.
The hosted Hobby plan lists one monitor, one status page with three components and a 10-minute minimum check interval. Paid tiers list password protection and plan or add-on terms for other access controls.
Which records can you take off the status page?
The status page’s JSON feed describes published components, reports and maintenance. JSON is a text format for named fields and values. It represents what the page publishes, so keep your monitor setup, alert routes and important internal records separately.
Turning off search indexing tells search engines to leave the page out. It does not limit who can open the address. Check access settings before publishing internal material.
What would visitors see if uploads stopped but the site stayed open?
On paper, draw an app with separate “Website” and “File uploads” components. Use no monitor, endpoint or real status page.
- Draw the monitor resultShow file uploads failing while the website still works. Label which component can reflect that check.
- Draft a visitor updateSay what action is affected and when you would update readers. Keep internal alert text private and check that the imagined status host still answers during the outage.