Status pages

Public status pages for your services or each client: components linked to monitors, automatic incidents, incident updates, planned maintenance and email subscribers.

A status page is a public web page that tells your clients what is working, what is not, and what is planned. Open them from Ticketing β†’ Status Pages in the sidebar. They come with the Ticketing module. Make one for your own services, or one for each client.

Creating a page

Click New status page, give it a name and, if you like, a web address (lower-case letters, numbers and dashes). The page starts as a draft: add components, then turn on Published in Settings. The public address is shown in Settings with a copy button.

Components

Components are the services on the page, for example Website, Client portal or Email.

  • Put components in groups and change their order with the arrows.
  • Link a monitor and the component follows it: up is Operational, slow is Degraded, down is Major outage. The page shows the monitor's uptime bars for the history length you choose (30, 60 or 90 days).
  • Set a status by hand (Operational, Degraded, Partial outage, Major outage or Maintenance) for anything the monitors cannot see. A component with a manual status is left alone by automatic incidents until you clear it.

The overall banner at the top shows the worst status of any component.

Incidents

Open an incident from the Incidents tab with a title, impact, the components affected and a first update. Post updates as it moves through Investigating, Identified, Monitoring and Resolved. Every update is shown on the page in a timeline and can be emailed to subscribers.

With Automatic incidents on (Settings), an incident opens on the page by itself when a linked monitor goes down and is resolved when it recovers.

Planned maintenance

Schedule maintenance from the Maintenance tab with a start and end time and the components affected. It starts and finishes on time by itself, subscribers get a reminder a day before, and outages on linked monitors during the window are marked as maintenance rather than alerting.

Subscribers

With Email subscribers on, visitors can enter an email address on the page. They get an email to confirm first; nothing is sent until they do. Every email has a link to stop, and sign-ups that are never confirmed are removed. The Subscribers tab lists everyone and lets you remove anyone.

The subscribe form gives the same answer whether or not an address is already signed up, so nobody can find out who is subscribed. Subscriber addresses are stored encrypted.

Settings

  • Name, description, logo, colour and support link. Leave logo and colour blank to use your company branding.
  • Client β€” the CRM company the page is for.
  • Published, Email subscribers, Automatic incidents and Show uptime bars.
  • History β€” 30, 60 or 90 days of bars.

The public page refreshes every minute and shows current incidents, planned maintenance, every component and the last 14 days of incidents.

Was this article helpful?

Status pages β€” Service Desk & Ticketing | Plenix Cloud Docs