Status pages

What a status page shows

A status page is a shareable view of selected RMON checks. Use it to show colleagues, customers, or an operations team whether published services are available without giving them access to the RMON interface.

The page shows an overall condition, each selected check's name and uptime, recent states, and an optional response chart. The group and check type may also be visible.

A status page URL is public to anyone who can open it. Do not treat the slug as a password and do not publish confidential check names or descriptions.

Create a page

1. Open Monitoring → Status pages.
2. Click + Create status page.
3. Enter a clear Name, such as Customer services.
4. Enter a unique Slug. Use lowercase letters, numbers, and single hyphens; for example, customer-services.
5. Click Next.
6. Add an optional Description that explains the scope of the page.
7. Move the checks you want to publish from All checks to Added checks with the + button. Use − to remove a check.
8. Optionally add custom styles, then save the page.

Select only checks that are meaningful to the intended audience. A customer page usually needs customer-facing services, while an internal operations page may include dependencies and regional checks.

Open and share

After saving, the status-page list shows the page name, description, overall condition, and public path. Click the page row to open it in a new tab.

1. Open the public page while signed out or in a private browser window.
2. Check the title, description, service names, groups, and current states.
3. Open an available response chart and confirm that its contents are appropriate for the audience.
4. Copy the displayed page URL and share it with the intended users.

All Systems Operational means all checks on the page are currently healthy. Not all Systems Operational means at least one published check requires attention. Each check's color and uptime provide more detail.

Edit or delete a page

• Use the Edit icon to change the name, slug, description, selected checks, or custom styles.
• If you change the slug, previously shared links will no longer point to the new page address. Share the new URL with users.
• Use the Delete icon to permanently remove a page after confirming that nobody still depends on it.
• Review the selected checks whenever services are renamed, replaced, disabled, or moved between audiences.

Deleting a status page does not delete the checks displayed on it. Removing a check from a page also leaves the original check unchanged.

Publication checklist

• Use audience-friendly service names and descriptions.
• Do not expose internal hostnames, IP addresses, customer identifiers, incident notes, credentials, or private group names.
• Assume that the URL can be forwarded or indexed; a hard-to-guess slug is not access control.
• Publish the smallest useful set of checks.
• Verify custom styles in a private browser window and on mobile before sharing the page.
• Review the public page after every structural change to its checks.

For the wider installation baseline, see the Security checklist.

Troubleshooting

• The slug is rejected: use lowercase letters, numbers, and single hyphens, and make sure the slug is not already in use.
• A service is missing: edit the page and confirm that the check is listed under Added checks.
• A page shows an unexpected incident: open the corresponding check in RMON and review its latest result and location.
• The page has no useful data: confirm that its checks are enabled and have already produced results.
• The design is broken: remove or simplify the custom styles, save, and reload the public page.
• An old link stopped working: check whether the page slug was changed or the page was deleted.