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.

Overall System Status

At the top of the page, a prominent status card shows the current overall system state:

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

The card also shows when the status was last updated.

Service Details

Below the overall status, each individual service is displayed in its own card with:

• 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

Auto-Refresh

The status page includes two refresh mechanisms:

• Auto-refresh — when enabled (default), the page polls for updates every 30 seconds. Toggle the auto-refresh button to turn this on or off.
• Manual refresh — click the Refresh button at any time to fetch the latest status immediately. The refresh icon animates while loading.

Tip

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

Monitored Services

The status page displays all services registered with the EQMS backend status endpoint. Typical services include:

• 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.

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.