System Status

The System Status page provides real-time health monitoring of all EQMS services and components. It is a public page that does not require authentication, making it accessible to all users including during login issues.

---

Check overall system status

1. Navigate to /status in the browser address bar (no login required).

2. At the top of the page, review the overall system status card:

   Status	Indicator	Meaning
   Operational	Green	All services are running normally
   Degraded	Yellow	Some services are experiencing issues
   Down	Red	Critical services are unavailable

3. Note when the status was last updated.

---

Review individual service health

1. Below the overall status, review each service card showing:
   • Service name and status icon
   • Status badge (Operational, Degraded, or Down)
   • Status message describing the current state
   • Response time in milliseconds (when available)
   • Additional details such as database connections, queue depth, or other service-specific metrics

Typical monitored services

• API Server — the main backend application
• Database — PostgreSQL database connectivity
• File Storage — document and attachment storage
• Search Index — full-text search engine
• Email Service — outbound email delivery
• Background Workers — asynchronous task processing

Note

The list of monitored services depends on your deployment configuration. Contact your system administrator if a service you expect to see is not listed.

---

Refresh status data

Use auto-refresh

1. Auto-refresh is enabled by default, polling for updates every 30 seconds.
2. Select the auto-refresh toggle button to turn auto-refresh on or off.

Refresh manually

1. Select the Refresh button at any time to fetch the latest status immediately.
2. The refresh icon animates while loading.

Tip

Leave auto-refresh enabled when monitoring an ongoing incident. The page updates automatically without requiring manual action.

---

When to use the status page

• Before reporting issues — check if a known service disruption is affecting the feature you are trying to use.
• During incidents — monitor service recovery in real time.
• After deployments — verify all services are healthy following a system update.
• Proactive monitoring — bookmark the page for periodic health checks.

The status page URL can be shared with anyone since it does not require login.

---

Practical example: Checking system health before an audit

Scenario: A QA Manager has a notified body audit starting tomorrow morning. They want to verify all EQMS services are operational so the auditor can access documents, signatures, and reports without interruption.

1. Navigate to /status in the browser (no login required).
2. Check the overall system status card. It shows Operational (green) — all services are running.
3. Review each service individually:
   • API Server: Operational, response time 45 ms.
   • Database: Operational, 12 active connections.
   • File Storage: Operational — critical for the auditor to download documents and evidence attachments.
   • Search Index: Operational, response time 28 ms — the auditor will use search to locate specific records.
   • Email Service: Operational — needed if the auditor requests documents to be sent via the external upload portal.
   • Background Workers: Operational, queue depth 0 — report generation and exports will process without delay.
4. Enable auto-refresh and leave the status page open in a browser tab. It will poll every 30 seconds and update automatically.
5. The next morning, check the status page one final time before the auditor arrives. All services remain green.
6. Share the /status URL with the auditor so they can independently verify system availability if they experience any issues during the audit.

If any service had shown Degraded or Down status, the QA Manager would have had time to contact the system administrator the evening before to resolve the issue, avoiding disruption during the audit itself.