These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Server Monitoring
- Data model
The tables behind Server Monitoring
Server Monitoring ships with 53 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 53
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Service health
Services link to Assets and availability checks; server samples link to Assets.
Response
Incidents link to Services, Assets and People, with incident updates and response events recording the chronology.
Impact
Service outages and service impacts link to Incidents.
Change
Changes link to Services; change reviews and rollback checks link to Changes; Deployments link to Services.
Operations context
On call shifts link to Services and People; Runbooks link to Services and People; asset service links connect Assets and Services.
Every table, by feature
- Service health6
- Incident response6
- Outages and impact5
- On-call operations6
- Changes and deployments7
- Assets and runbooks7
- Shared and settings32
- Services
Services records for IT service and asset operations.
Linked to People - Assets
Assets records for IT service and asset operations.
Linked to Services - Availability checks
Availability Checks records for IT service and asset operations.
Linked to Services - Server samples
Server Samples records for IT service and asset operations.
Linked to Assets - Maintenance windows
Approved maintenance windows during which a monitored service is intentionally unavailable.
Linked to Incidents - Integration receipts
Integration Receipts records for IT service and asset operations.
- Incidents
Incidents records for IT service and asset operations.
Linked to Services, Assets, People - Incident updates
Incident Updates records for IT service and asset operations.
Linked to Incidents, People - Response events
Response Events records for IT service and asset operations.
Linked to Incidents, People - People
People records for IT service and asset operations.
Linked to Users - Services
Services records for IT service and asset operations.
Linked to People - Assets
Assets records for IT service and asset operations.
Linked to Services
- Service outages
Recorded outages of monitored services with start and restoration timestamps.
Linked to Incidents - Service impacts
Business impact recorded against a monitored service during an incident.
Linked to Incidents, People - Incidents
Incidents records for IT service and asset operations.
Linked to Services, Assets, People - Availability checks
Availability Checks records for IT service and asset operations.
Linked to Services - Maintenance windows
Approved maintenance windows during which a monitored service is intentionally unavailable.
Linked to Incidents
- On call shifts
On Call Shifts records for IT service and asset operations.
Linked to Services, People - Incidents
Incidents records for IT service and asset operations.
Linked to Services, Assets, People - Response events
Response Events records for IT service and asset operations.
Linked to Incidents, People - Incident updates
Incident Updates records for IT service and asset operations.
Linked to Incidents, People - People
People records for IT service and asset operations.
Linked to Users - Services
Services records for IT service and asset operations.
Linked to People
- Changes
Changes records for IT service and asset operations.
Linked to Services - Change reviews
Change review decisions recorded by the reviewing board.
Linked to Changes, People - Deployments
Deployments records for IT service and asset operations.
Linked to Services - Rollback checks
Rollback Checks records for IT service and asset operations.
Linked to Changes - Maintenance windows
Approved maintenance windows during which a monitored service is intentionally unavailable.
Linked to Incidents - Availability checks
Availability Checks records for IT service and asset operations.
Linked to Services - Server samples
Server Samples records for IT service and asset operations.
Linked to Assets
- Assets
Assets records for IT service and asset operations.
Linked to Services - Asset service links
Asset Service Links records for IT service and asset operations.
Linked to Assets, Services - Monitored devices
Physical and virtual devices under active monitoring.
Linked to Assets - Services
Services records for IT service and asset operations.
Linked to People - Runbooks
Operational runbooks and response procedures for monitored services.
Linked to People, Services - Runbook feedback
Reader feedback recorded against a runbook.
Linked to Runbooks - Server samples
Server Samples records for IT service and asset operations.
Linked to Assets
Keys and references
Each operational record has an Id. Use the service and asset references to connect a health observation with the incident being worked. Keep the person reference for the assigned responder, review decision and on-call shift. An integration receipt has its own provider and external event identifier; those fields help trace an incoming event separately from the incident that the team investigates.
Migration order
- People and services. Establish owners and service names before importing operational history.
- Assets and dependencies. Load assets and verify their service links.
- Monitoring observations. Bring in check and sample history with original timestamps.
- Response records. Load incidents, updates, events, outages and service impact in chronological order.
- Changes and procedures. Add review decisions, deployments, rollback checks and runbooks with their references intact.
Set up Server Monitoring your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.