Status Pages

Drumbeats has two kinds of public status pages. Simple status pages show one monitor's health and are created per monitor directly from the monitor settings. Advanced status pages are multi-monitor pages with component groups, branding, incident management, and maintenance windows — built from the Status Pages section of the dashboard.

Use simple pages for a single critical job you want to share with stakeholders. Use advanced pages when you want a unified status view for a product or service, the way customers expect from a public-facing status page.

Simple status pages

A simple status page is a public-facing view of a single monitor — current state, recent incident history, and a brief description. Available for Cron, Heartbeat, and Uptime monitor types.

What you can configure

The status page editor exposes these fields per monitor:

• Display name — what visitors see at the top of the page.
• Description — short context aimed at non-operators.
• Slug — the path segment in the default URL form.
• Vanity slug — globally unique, used in the /s/<vanity-slug> form on paid plans.
• noindex — discourage search-engine indexing.
• show_incidents — toggle whether incident history is visible publicly.
• is_active — publish / unpublish the page without deleting it.

URL formats

Simple status pages render at one of two URL shapes on status.drumbeats.io:

Vanity slugs are first-come-first-served; pick a name that is specific to your product (acme-billing-cron not billing).

Branding

Incident visibility

show_incidents controls whether the public page renders an incident history block. Two common configurations:

• Show — operational transparency. Visitors can see recent outages, durations, and acknowledgement timing. Good for customer-facing status pages where you want to be open about availability.
• Hide — current-state only. The page shows only the current UP / DOWN badge and the description. Good for internal stakeholder pages where the incident trail is not relevant.

Advanced status pages

Advanced status pages are multi-monitor pages you build from the Status Pages section of the dashboard. They group monitors into components, show overall service health, and support public incidents and maintenance windows. Available on Pro and Enterprise plans.

URL format

Advanced pages live at:

status.drumbeats.io/<your-slug>

status.drumbeats.io/<your-slug>

The slug is set when you create the page and can be changed later from the page's Settings tab.

Components and groups

Organise your monitors into logical groups — for example "API", "Database", "Background Jobs". Each component reflects the real-time status of the monitors linked to it, and can be reordered via drag-and-drop. The page shows one overall status banner reflecting the worst state across all components: Operational, Degraded, Partial Outage, Major Outage, or Maintenance.

Incidents

Declare incidents manually (with status, impact, affected components, and timestamped update messages) or let Drumbeats bridge monitor incidents automatically. Incidents appear on the public page in real time and can be marked through the standard investigating → identified → monitoring → resolved flow.

Maintenance windows

Schedule planned maintenance with a title, message, start/end time, and affected components. Upcoming maintenance is shown on the public page so visitors know when to expect disruption.

Branding

• Accent color — sets the brand color used for key UI elements.
• Default theme — auto, light, or dark.
• Logo and favicon — upload PNG, JPEG, or WebP assets to replace the Drumbeats defaults (Pro and Enterprise).

Feeds

Each advanced status page exposes RSS and Atom feeds for passive status updates:

https://api.drumbeats.io/v1/public/pages/<slug>/feed.xml
https://api.drumbeats.io/v1/public/pages/<slug>/feed.atom

https://api.drumbeats.io/v1/public/pages/<slug>/feed.xml
https://api.drumbeats.io/v1/public/pages/<slug>/feed.atom

Settings tab

From the page editor's Settings tab you can change:

• Name — the page title shown at the top.
• Slug — the public URL path segment.
• Description — optional text shown on the public page.
• Published — toggle visibility (unpublished pages return 404).
• Hide from search engines — adds <meta name="robots" content="noindex, nofollow"> when enabled.

Search indexing

Both simple and advanced status pages are indexed by search engines by default — this is intentional, since a public status page is meant to be discoverable. Use noindex (simple) or Hide from search engines (advanced) when the page should be reachable by direct link but not indexed. Drumbeats sets the appropriate meta tag; the page remains publicly accessible.

Good fits and poor fits

Good fits:

• Customer-facing service status pages showing multiple components (use advanced).
• Single critical job shared with stakeholders (use simple).
• Internal stakeholder views of scheduled jobs — "did the nightly invoice run finish?"

Poor fits:

• Highly ephemeral event-driven jobs — not supported on either page type.
• Sensitive internal monitors that should not have any public URL.
• Monitors whose outage would surface internal data via the description or incident details.

Operational guidance

• Keep display names and descriptions understandable to non-operators — "Nightly backup ran" beats "JOB_CRON backup.sh".
• Decide whether incident visibility is appropriate before sharing the link publicly.
• For multi-service products, use an advanced status page so customers see one unified view instead of multiple per-monitor links.
• Vanity slugs are globally unique — changing one breaks existing bookmarks, so pick carefully.

Related guides

• Monitor types — which types support status pages and which do not.
• Incidents — the incident model that drives the public history block.
• Support — general troubleshooting and contact info.