IT OPERATIONSIncident management
PostgreSQLNot signed inSign in

OPERATIONS / INCIDENTS

Incident register

Search, filter, and manage incidents loaded from PostgreSQL.

16 records
IncidentTitleApplicationPriorityStatusEnvironmentAssignedDetected
INC-1016testProject PortalLOWNEWTEST—21 Sep 2026, 01:04 UTC
INC-1015Monitoring alert: DATABASE health check failedIdentity ServiceCRITICALNEWPRODUCTION—21 Sep 2026, 01:03 UTC
INC-1014Authentication service health check warningIdentity ServiceHIGHNEWPRODUCTION—20 Sep 2026, 05:32 UTC
INC-1013Portal response time increased after deploymentProject PortalHIGHINVESTIGATINGPRODUCTION—19 Sep 2026, 06:14 UTC
INC-1012Document metadata update delayedDocument Search ServiceLOWNEWPRODUCTION—18 Sep 2026, 11:27 UTC
INC-1001Document search response time increasedDocument Search ServiceHIGHINVESTIGATINGPRODUCTION—18 Sep 2026, 09:12 UTC
INC-1002Project Portal authentication failuresProject PortalCRITICALRESOLVEDPRODUCTION—17 Sep 2026, 14:05 UTC
INC-1011Unexpected session expirationIdentity ServiceMEDIUMINVESTIGATINGPRODUCTION—17 Sep 2026, 05:11 UTC
INC-1010Search index storage usage above thresholdDocument Search ServiceMEDIUMWAITINGPRODUCTION—16 Sep 2026, 08:22 UTC
INC-1009Scheduled document synchronization did not completeProject PortalMEDIUMRESOLVEDPRODUCTION—15 Sep 2026, 03:44 UTC
INC-1008Expired application integration certificateIdentity ServiceCRITICALCLOSEDPRODUCTION—14 Sep 2026, 03:18 UTC
INC-1007Search requests returning HTTP 502Document Search ServiceHIGHRESOLVEDPRODUCTION—13 Sep 2026, 06:06 UTC
INC-1006Large document upload failsProject PortalMEDIUMWAITINGPRODUCTION—12 Sep 2026, 10:38 UTC
INC-1005Users intermittently unable to log inIdentity ServiceHIGHRESOLVEDPRODUCTION—11 Sep 2026, 04:52 UTC
INC-1004Document indexing queue falling behindDocument Search ServiceHIGHINVESTIGATINGPRODUCTION—10 Sep 2026, 07:17 UTC
INC-1003Database connection pool exhaustedProject PortalCRITICALRESOLVEDPRODUCTION—09 Sep 2026, 05:41 UTC
⌘ What is happening?Request lifecycle
  1. Browser requested GET /incidents/
  2. Django queried the incidents table
  3. Django joined each incident with its application
  4. Django returned the result to the template
Database writesNone