ServPulse/Domain: Difference between revisions

From Nasqueron Agora
Ieli (talk | contribs)
No edit summary
Ieli (talk | contribs)
No edit summary
Line 15: Line 15:


;Incidents
;Incidents
:This concept represents any incidents, outages, or disruptions that occur and are reported on the status page.
:An outage, disruption, or degradation reported on the status page. Incidents follow a lifecycle and can affect multiple services.
:'''Attributes:''' title, description, status (e.g., resolved, ongoing), severity
:'''Attributes:''' title, status (investigating, identified, monitoring, resolved), impact (none, minor, major, critical), start_date, update_date, end_date.
:'''Database tables:''' incident, incident_update, incident_service
 
;Incident Update
:A timestamped status change within an incident, forming the incident timeline.
:'''Attributes:''' incident_id, status, message.
:'''Database tables:''' incident_update


;Users
;Users
:This concept represents the users who view or edit the status page.
:This concept represents the users who view or edit the status page.
:'''Attributes:''' name, role, permissions (permissions could also be defined at role level)
:'''Attributes:''' name, role, permissions (permissions could also be defined at role level)

Revision as of 15:27, 17 February 2026

Lexicon

StatusPage
The entity representing the status page itself.
Attributes: title, description, URL
Service
A monitored entity on the status page (server, application, database, API, etc.). Services can be grouped and ordered.
Attributes: name, group, description, url, auto_status, status (operational, degraded, partial, major, maintenance), order.
Database table: service
Metrics
This concept represents the performance metrics or indicators being measured for each component, such as uptime, response time, error rates, and other relevant metrics.
Attributes: name, value, unit, timestamp.
Incidents
An outage, disruption, or degradation reported on the status page. Incidents follow a lifecycle and can affect multiple services.
Attributes: title, status (investigating, identified, monitoring, resolved), impact (none, minor, major, critical), start_date, update_date, end_date.
Database tables: incident, incident_update, incident_service
Incident Update
A timestamped status change within an incident, forming the incident timeline.
Attributes: incident_id, status, message.
Database tables: incident_update
Users
This concept represents the users who view or edit the status page.
Attributes: name, role, permissions (permissions could also be defined at role level)