ServPulse/Domain - Revision history

Ieli at 15:37, 17 February 2026

2026-02-17T15:37:45Z

← Older revision		Revision as of 15:37, 17 February 2026
Line 11:		Line 11:
	:'''Database table:''' service		:'''Database table:''' service

	;~~Metrics~~		;Metric
	:Performance data recorded per service, either by the health check service (automatic) or via the API (manual).		:Performance data recorded per service, either by the health check service (automatic) or via the API (manual).
	:'''Attributes:''' service_id, uptime (decimal 0-100), response_time (integer, ms), error_rate (decimal 0-100), recorded_at.		:'''Attributes:''' service_id, uptime (decimal 0-100), response_time (integer, ms), error_rate (decimal 0-100), recorded_at.
	:'''Database ~~tables~~:''' metric (indexed on service_id + recorded_at)		:'''Database table:''' metric (indexed on service_id + recorded_at)
	:'''Endpoint:''' GET /api/metrics (latest per service), GET /api/metrics/service/:id?days=30 (raw), GET /api/metrics/service/:id/daily?days=30 (aggregated)		:'''Endpoint:''' GET /api/metrics (latest per service), GET /api/metrics/service/:id?days=30 (raw), GET /api/metrics/service/:id/daily?days=30 (aggregated)

	;~~Incidents~~		;Incident
	:An outage, disruption, or degradation reported on the status page. Incidents follow a lifecycle and can affect multiple services.		: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.		:'''Attributes:''' title, status (investigating, identified, monitoring, resolved), impact (none, minor, major, critical), start_date, update_date, end_date.
Line 25:		Line 25:
	:A timestamped status change within an incident, forming the incident timeline.		:A timestamped status change within an incident, forming the incident timeline.
	:'''Attributes:''' incident_id, status, message.		:'''Attributes:''' incident_id, status, message.
	:'''Database ~~tables~~:''' incident_update		:'''Database table:''' incident_update

	;~~Users~~		;Authentication
	:Admin access is controlled by JWT tokens signed with JWT_SECRET. There is no user table, no user accounts, and no permissions system. A single admin role exists. Tokens are generated via CLI and pasted into the login page.		:Admin access is controlled by JWT tokens signed with JWT_SECRET. There is no user table, no user accounts, and no permissions system. A single admin role exists. Tokens are generated via CLI and pasted into the login page.
	:'''Token payload:''' { role: 'admin' }		:'''Token payload:''' { role: 'admin' }
	:'''Endpoint:''' POST /api/auth/verify		:'''Endpoint:''' POST /api/auth/verify

			;Maintenance
			:A scheduled maintenance window that can affect multiple services.
			:'''Attributes:''' title, description, scheduled_start, scheduled_end, status (scheduled, in_progress, completed).
			:'''Database tables:''' maintenance, maintenance_service

			;Subscriber
			:A user subscribed to status update notifications, either by email or webhook. Email subscribers must confirm via a token link before receiving notifications.
			:'''Attributes:''' email (or webhook_url), type (email, webhook), confirmed, confirm_token, unsubscribe_token.
			:'''Database table:''' subscriber (with partial unique indexes on email and webhook_url)

			;Group
			:A label used to visually organize services on the status page. Stored as a string field on the service table (not a separate entity). Services with the same group value are displayed together under a shared heading. Services without a group appear under "Uncategorized".

Ieli at 15:32, 17 February 2026

2026-02-17T15:32:56Z

← Older revision		Revision as of 15:32, 17 February 2026
Line 12:		Line 12:

	;Metrics		;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~~.		:Performance data recorded per service, either by the health check service (automatic) or via the API (manual).
	:'''~~Attributes~~:''' ~~name~~, ~~value~~, ~~unit, timestamp.~~		:'''Attributes:''' service_id, uptime (decimal 0-100), response_time (integer, ms), error_rate (decimal 0-100), recorded_at.
			:'''Database tables:''' metric (indexed on service_id + recorded_at)
			:'''Endpoint:''' GET /api/metrics (latest per service), GET /api/metrics/service/:id?days=30 (raw), GET /api/metrics/service/:id/daily?days=30 (aggregated)

	;Incidents		;Incidents

Ieli at 15:31, 17 February 2026

2026-02-17T15:31:11Z

← Older revision		Revision as of 15:31, 17 February 2026
Line 26:		Line 26:

	;Users		;Users
	:~~This concept represents~~ the ~~users who view or edit the status~~ page.		:Admin access is controlled by JWT tokens signed with JWT_SECRET. There is no user table, no user accounts, and no permissions system. A single admin role exists. Tokens are generated via CLI and pasted into the login page.
	:'''~~Attributes~~:''' ~~name,~~ role~~, permissions (permissions could also be defined at role level)~~		:'''Token payload:''' { role: 'admin' }
			:'''Endpoint:''' POST /api/auth/verify

Ieli at 15:29, 17 February 2026

2026-02-17T15:29:06Z

← Older revision		Revision as of 15:29, 17 February 2026
Line 1:		Line 1:
	== Lexicon ==		== Lexicon ==

	;~~StatusPage~~		;Configuration
	:~~The entity representing~~ the ~~status page itself~~.		:Application-level settings stored in config/app.json and served via the config API.
	:'''Attributes:''' title, ~~description~~, URL		:'''Attributes:''' navbar.title, navbar.buttons_left (array of {name, link}), footer.line1 (text with %link1%/%link2% placeholders, labels, URLs), footer.line2 (text with %link% placeholder, label, URL).
			:'''Endpoint:''' GET /api/config/getAll (public), PUT /api/config (admin)

	;Service		;Service

Ieli at 15:27, 17 February 2026

2026-02-17T15:27:38Z

← Older revision		Revision as of 15:27, 17 February 2026
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)

Ieli at 15:23, 17 February 2026

2026-02-17T15:23:58Z

← Older revision		Revision as of 15:23, 17 February 2026
Line 5:		Line 5:
	:'''Attributes:''' title, description, URL		:'''Attributes:''' title, description, URL

	;~~Component~~		;Service
	:~~This concept represents the various components or elements being~~ monitored on the status page, ~~such as servers~~, ~~services~~, ~~applications, databases~~, and ~~other relevant entities~~.		:A monitored entity on the status page (server, application, database, API, etc.). Services can be grouped and ordered.
	:'''Attributes:''' name, description, status (~~e.g.~~, up, ~~down~~, ~~degraded~~).		:'''Attributes:''' name, group, description, url, auto_status, status (operational, degraded, partial, major, maintenance), order.
			:'''Database table:''' service

	;Metrics		;Metrics

Dereckson: Created page with "== Lexicon == ;StatusPage :The entity representing the status page itself. :'''Attributes:''' title, description, URL ;Component :This concept represents the various components or elements being monitored on the status page, such as servers, services, applications, databases, and other relevant entities. :'''Attributes:''' name, description, status (e.g., up, down, degraded). ;Metrics :This concept represents the performance metrics or indicators being measured for ea..."

2025-10-23T23:46:52Z

Created page with "== Lexicon == ;StatusPage :The entity representing the status page itself. :'''Attributes:''' title, description, URL ;Component :This concept represents the various components or elements being monitored on the status page, such as servers, services, applications, databases, and other relevant entities. :'''Attributes:''' name, description, status (e.g., up, down, degraded). ;Metrics :This concept represents the performance metrics or indicators being measured for ea..."

New page

== Lexicon ==

;StatusPage
:The entity representing the status page itself.
:'''Attributes:''' title, description, URL

;Component
:This concept represents the various components or elements being monitored on the status page, such as servers, services, applications, databases, and other relevant entities.
:'''Attributes:''' name, description, status (e.g., up, down, degraded).

;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
:This concept represents any incidents, outages, or disruptions that occur and are reported on the status page.
:'''Attributes:''' title, description, status (e.g., resolved, ongoing), severity

;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)