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
- Who it's for
- Multi-site services
Multi-site services
A team serving multiple sites can use probe location and site code to keep the location of an interruption clear. Availability checks record where a probe ran and whether it succeeded. Service outages record the site, reference, start and restoration times. The incident connects those observations to an assigned responder, while the service impact record describes whether the monitored service is delayed or unavailable.
How Server Monitoring is set up for you
Location evidence
Compare checks from different probe locations before describing the scope of an interruption.
Outage record
Use the site code and outage reference to track each observed service interruption.
Owner review
Have the service owner assess the impact and confirm the restoration evidence.
Maintenance context
Keep the maintenance window's site, time and timezone alongside planned work.
A team serving multiple sites can use probe location and site code to keep the location of an interruption clear. Availability checks record where a probe ran and whether it succeeded. Service outages record the site, reference, start and restoration times. The incident connects those observations to an assigned responder, while the service impact record describes whether the monitored service is delayed or unavailable.
Begin with one service checked from two locations. Link the service to its assets and name an owner and responder. Record a failed check at one location while the other still succeeds. Open an incident, then create an outage record for the affected site. The service owner assesses whether the impact is a delay or an unavailable service. After a later successful check at that site, record restoration and resolve the incident. Review the chronology to ensure the unaffected location was not described as interrupted.
Next, rehearse a planned maintenance window for the same site. Agree how the team communicates the planned interval and how it distinguishes maintenance from an unplanned outage. Keep the recorded observations visible so the next shift can understand what happened at each location.
Features to start with
Outages and impact
Record interruption and restoration times with the incident and affected service impact.
Service health
Review availability checks and server resource samples against the service and asset they describe.
Incident response
Track the assigned responder, investigation updates and response events from opening through closure.
Roles on the team
- Monitoring Operator
- Reviews checks and samples and starts an incident when a service needs attention.
- Incident Responder
- Acknowledges, investigates and documents assigned incidents.
- Service Owner
- Reviews service impact and recovery evidence for the services they own.
- Release Operator
- Schedules approved changes and records deployments and rollback checks.
Set up Server Monitoring your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.