The status page will be a designed page displaying the default configured Monitors, their tasks, and the status of those tasks. Any errors being reported will be displayed at the top of the page and the ever-popular red, orange-yellow, green will denote the state of the monitors on the page. Users should be able to click through to find specific logs for a monitored process. Note: More detail should be added to this section as design is agreed upon

Example status pages

These are ideas for design only.

Permissions

The status page should have its own custom permissions that allow users to allow/deny access to the page overall on a user-by-user basis. Access to specific monitors will be controlled by which status page they are assigned to and will not be configurable as a permission. This will allow for simpler caching and maintenance of the status page.

Checklist Items

  1. #3074968: Design Status Page Assigned to: alittledesign
  2. #3087447: Create status page management form
  3. #3087448: Implement status check logic for Status Page Assigned to: merauluka
  4. #3105815: Build backend data support for front end design Assigned to: merauluka
  5. #3083707: Implement Status Page UX Assigned to: merauluka
  6. Create PHP Unit tests for status page
  7. Create functional tests for status page

Comments

merauluka created an issue. See original summary.

merauluka’s picture

Assigned: Unassigned » merauluka
merauluka’s picture

Issue summary: View changes

Added issue tracking.

merauluka’s picture

Issue summary: View changes
merauluka’s picture

Issue summary: View changes

Updated subtask list and links to active issues.

merauluka’s picture

Issue summary: View changes

Updated description with new architecture issue links.

merauluka’s picture

Issue summary: View changes
merauluka’s picture

Status: Active » Fixed

The status page has been created and is functional. This ticket can now be closed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.