Service Levels: Status pages
Overview
Use this page to create and manage public status pages. A status page is a public web page, served at its own URL, that reports the health of selected services to anonymous visitors without requiring them to sign in to LoadGen. It solves the problem of sharing service health information with customers or stakeholders who should never see the internal Service Levels dashboards.
A status page draws on services that are already defined in Configuration: Service Levels: Services, so those services must exist before you can attach them here. Once a page is published, its URL can be shared or linked from customer communications, and any incidents or maintenance windows you record through its Manage action appear directly on that public page.
This page lists every status page you've defined, showing its title, public URL, how many services it includes, and whether it's currently published. From here you create a new page, edit an existing one's branding and service list, preview what visitors see, open its incidents and maintenance workspace, or delete it.
Key concepts
- status page - A public web page, served at its own URL, that reports the health of selected services to anonymous visitors without requiring them to sign in. (related: Service Levels: Health)
- Published - A toggle on the status page editor that controls whether the page is live at its public URL; turning it off takes the page offline without deleting its configuration.
- Visibility - A setting on the status page editor that controls who can view the published page once it's live. (related: Service Levels: Access Control)
- Services included - The set of Configuration-defined services attached to a status page, each with an optional group label, that determine what the public page reports. (related: Configuration: Service Levels: Services)
When to use it
- You need to give customers or stakeholders a public summary of service health without exposing internal dashboards.
- You're launching a new service and want it rolled into a published status page.
- You need to take a status page temporarily offline by turning off Published, without deleting its configuration.
- An incident or maintenance window needs to be posted publicly through a page's Manage action.
- You want to confirm how many services a page currently reports, or check its live URL.
Before you begin
- At least one service must exist in Configuration: Service Levels: Services before you can add it to a status page.
- Your account needs permission to manage Service Levels status pages, granted in Operations: Permissions.
- If the page should be restricted rather than fully public, confirm the access rule is set up in Service Levels: Access Control.
Common workflows
Create and publish a new status page
Persona: Service Levels admin
- Select New status page in the toolbar.
- Expect: The editor opens with empty Title, Slug, Logo URL, Brand color and Visibility fields, an empty services list, and Published turned off.
- Enter a title in Title and a URL slug such as svc.lg.fulmar in Slug.
- Expect: The fields hold the values that will later appear as the page's title and public URL path in the PAGE column.
- Select the services to include and turn on Published.
- Expect: The services picker lists your chosen services, raising what will become the SERVICES count, and the page is marked to go live once saved.
- Select Save page.
- Expect: The editor closes and a new row appears in the status pages table with the title, slug, services count and a Published state badge.
Verify: The new row shows the title and slug you entered with a Published state, and selecting Preview on that row opens the live anonymous URL showing the services you selected.
Update which services and branding appear on an existing status page
Persona: Service Levels admin
- Select Edit on the row for the page you want to change.
- Expect: The editor opens pre-filled with that page's Title, Slug, Logo URL, Brand color, Visibility and current services.
- Update Brand color or Logo URL, or add or remove services in the services picker.
- Expect: The field you changed reflects the new value; removing a service will lower the SERVICES count once saved.
- Select Save page.
- Expect: The editor closes and the row updates in place, for example the SERVICES count changes to match your new selection.
Verify: The row's SERVICES count and branding match your edits, and reopening Preview shows the updated logo, color and service list on the live page.
Steps
Step 1
Open Status pages under Service Levels.
Expected result: The table lists the status pages you've defined, here a single page named Demo published at /status-pages/demo-loadgen with 1 service and a Published state badge, and a credentials-expiring notice about an expiring API token appears at the top right.
This is the starting view for checking which status pages are published before you create, edit, or manage incidents on one.
- The PAGE column shows the page title with its public URL path beneath it.
- The STATE badge reads Published for the Demo page.
- Row actions Preview, Manage, Edit, Delete sit in the ACTIONS column.
Step 2
Select Refresh in the toolbar.
Expected result: The table reloads, the credentials-expiring notice closes, and the Refresh and New status page buttons become clearly visible in the toolbar.
Refreshing confirms you're viewing the current list and state of status pages before you create or edit one.
- New status page opens the editor to define a new public status page.
-
Refresh re-reads the current list of status pages from the server.
Field reference
| Field | Purpose | Format / Validation | Required | Default |
|---|---|---|---|---|
| Title | Sets the display name shown on the public page and in the PAGE column of this table. Keep it recognizable to customers since it's the only label anonymous visitors see. | Text | Yes | - |
| Slug | Sets the URL path segment that makes the page reachable at /status-pages/{slug}. Changing it later changes the public URL, so treat it as a stable identifier once you've shared the link. | Text, URL-safe | Yes | - |
| Published | Controls whether the page is live at its public URL. Turn it on to make the page reachable by anonymous visitors; turn it off to take the page offline temporarily without deleting it. | Toggle | No | - |
| Logo URL | Points to an image shown in the header of the published page for branding. Leave it empty to use the default header without a logo. | URL | No | - |
| Brand color | Sets the accent color used on the published page. Use a hex code that matches your other customer-facing material so the public page looks consistent with it. | Hex color code | No | - |
| Visibility | Controls who can view the published page once it's live. Choose the option that matches whether the page should be reachable by any visitor or restricted. | Selection | No | - |
| Services included | Selects which Configuration-defined services appear on the status page, with an optional group label per service to organize how they're displayed. Adding more services increases the SERVICES count shown in the table. | Multi-select with optional group text per service | No | - |
Column reference
| Column | What it shows | How to read it |
|---|---|---|
| PAGE | Identifies the status page by its title and shows its public URL path beneath it. | Read the top line as the page's display title and the line below it as the live public URL path once the page is published. |
| SERVICES | Shows how many services are attached to this status page. | A higher number means more services are rolled into this one public page; the count rises or falls as you add or remove services in Edit. |
| STATE | Shows the page's publication state, driven by the Published toggle in the editor. | Published means the page is live at its public URL. This is the only value captured in this environment; a page with Published turned off would not show this badge. |
| ACTIONS | Hosts the row-level controls for this status page. | Each button opens a different operation for that specific row: Preview the live page, Manage its incidents, Edit its settings, or Delete it. |
Controls reference
Refresh
Reloads the status pages table from the server.
When to use: Use it after making changes elsewhere, or to confirm you're seeing the current list before editing or deleting a page.
Side effects: Read-only: re-fetches data and does not change any status page.
New status page
Opens the status page editor with empty Title, Slug, Logo URL, Brand color and Visibility fields, an empty services list, and Published turned off.
When to use: Use it to publish a new public status page for a set of services.
Side effects: Opens the editor only; no status page is created until you select Save page.
Preview
Opens the live public URL for that status page.
When to use: Use it to see exactly what anonymous visitors see, before or after making changes.
Side effects: Read-only: does not change the page or its data.
Manage
Opens the incidents and maintenance workspace for that status page.
When to use: Use it when you need to post an incident update or schedule a maintenance window that should appear on the public page.
Side effects: Opening it is read-only; actions taken inside that workspace can post content visible on the public page.
Edit
Opens the status page editor pre-filled with that page's Title, Slug, Published state, Logo URL, Brand color, Visibility and services.
When to use: Use it to change branding, the services included, the slug, or to publish or unpublish the page.
Side effects: Opens the editor only; changes are not saved until you select Save page.
Delete
Opens a confirmation dialog asking to delete the status page by title and slug, warning that the action cannot be undone.
When to use: Use it to permanently remove a status page you no longer need.
Side effects: Mutating and irreversible once confirmed: the page definition is removed and its public URL stops serving.
Save page
Commits the values entered in the editor, creating a new status page or updating the one being edited.
When to use: Use it after filling in or changing Title, Slug, Published, Logo URL, Brand color, Visibility, or services.
Side effects: Mutating: creates or updates the status page row shown in the table.
Cancel
Closes the editor without saving.
When to use: Use it if you opened New status page or Edit and decide not to apply the changes.
Side effects: Read-only: discards any unsaved edits.
Dismiss
Closes the credentials-expiring notification card.
When to use: Use it to clear the notice from view once you've noted it or handled the credential renewal.
Side effects: Read-only: hides the notice locally and does not renew or change the underlying credential.
Verify the result
After you save a status page, its row appears in the table with the title and slug you set, a SERVICES count matching the services you attached, and a Published state badge if you turned on Published. Selecting Preview opens the public URL and shows the same services and branding you configured. If the row still shows an unpublished state or the wrong service count, reopen Edit, confirm Published is on and the intended services are selected, then Save page again. If a new or edited page doesn't appear in the table at all, select Refresh to reload the list.
Troubleshooting
- Symptom: A status page's STATE still doesn't read Published after you expect it to. Fix: Open Edit on that row, turn on the Published toggle, and select Save page again.
- Symptom: Selecting Preview opens a page with no services or an error. Fix: Open Edit and confirm the Slug is set and at least one service is selected in the services picker, then Save page.
- Symptom: A page you just created or edited doesn't show up, or still shows old values, in the table. Fix: Select Refresh in the toolbar; the table does not update on its own.
- Symptom: You deleted the wrong status page. Fix: There is no undo; the confirmation dialog warns this cannot be undone, so recreate it with New status page and reconfigure its Title, Slug, branding and services.
- Symptom: The Refresh and New status page buttons aren't visible. Fix: Close the credentials-expiring notice with the close (X) control, then renew the token in Configuration: Credential Profiles if it has actually expired.
Related articles
- Prerequisite: Configuration: Service Levels: Services - services must be defined here before you can attach them to a status page
- See also: Service Levels: Health - shows the detailed health data that a published status page summarizes for anonymous visitors
- See also: Service Levels: Access Control - governs who can view a page when Visibility is set to restrict access
- See also: Configuration: Credential Profiles - where you renew the API token referenced in the credentials-expiring notice on this page
- See also: Service Levels: Dashboard - the internal landing page for the Service Levels module that these public pages summarize