Endpoints
Service availability
Expose API, portal, tunnel, or integration checks from the same endpoint monitors ops already watches.
Module - Status pages
Turn service issues into customer confidence.
Status pages give customers a live, branded view of the services they depend on, driven by Dataplicity monitors, incidents, and page widgets so support can communicate without retyping operational data.
- Show customer-facing health from service endpoints, heartbeats, user-impact monitors, and incidents.
- Publish incident and maintenance context from the ops workflow while keeping internal detail private.
- Use pages, custom domains, markdown guidance, and history as support and trust evidence.
Customer portalstatus + dashboards
- Customer portal
- Telemetry ingest
- Alert routing
A useful first answer for customers
When something feels wrong, customers need to know whether it is you, them, or a planned change.
- Build separate pages for products, regions, enterprise accounts, or support tiers.
- Show only customer-safe health signals while keeping internal diagnostics in Dataplicity.
- Give support a single link to share before a ticket turns into a status chase.
Heartbeats
Field connectivity
Show whether critical gateways, sites, or appliances are checking in without exposing device consoles.
Impact
Customer-facing state
Translate internal monitor failures into plain-language impact for the audiences affected.
Incident communication that follows ops
Give support and customer success a place to send customers while engineering works the problem.
- Open incidents can appear on the page when customers need visibility.
- Resolved incidents create a timestamped record for follow-up conversations.
- Markdown widgets add temporary guidance, workaround notes, or escalation instructions.
Triage
Decide what customers should see
Start from alerts, monitors, or customer reports, then publish only the safe summary.
Updates
Keep everyone aligned
Post clear progress notes that support, account teams, and customers can all reference.
Resolution
Close the loop
Preserve timestamps, mitigation notes, and recovery evidence for post-incident reviews.
Publish under your brand
Make the page feel like part of your customer experience, not a bolt-on monitoring tool.
- Custom domains put status pages on your own customer-facing URL.
- Public visibility can be controlled per page so drafts and internal views stay hidden.
- Pages can sit beside dashboards, displays, docs, and portals for deeper customer context.
Pages
Audience-specific pages
Create pages for products, regions, customer cohorts, or named accounts instead of one noisy global page.
Domains
Customer-ready URLs
Map pages to a trusted domain such as status.example.com with verification tracked in Dataplicity.
Context
Docs and dashboards
Link status to customer docs or read-only dashboards when a simple green/red answer is not enough.
Fit it into daily customer work
A status page is most useful when it reduces repeated conversations across support, success, and enterprise reviews.
Support
Deflect avoidable tickets
Use the status page as the first support response when customers ask whether a service, site, or integration is healthy.
- Link it from support macros and help-center articles.
- Confirm live monitor state before escalating.
- Add customer-safe workaround notes while the incident is active.
Success
Explain reliability with evidence
Bring uptime history and resolved incidents into account reviews instead of reconstructing what happened from chat logs.
- Review incidents by product or customer-facing surface.
- Show maintenance windows and recovery times.
- Pair with dashboards for deeper operational proof.
Operations
Communicate without leaving ops
Keep the public story attached to the monitors, incidents, and device context your team already uses.
- Use widgets backed by existing monitors.
- Separate internal diagnosis from customer-safe updates.
- Keep a reusable trail for retrospectives and compliance evidence.