Hotel Systems Monitoring Agent
Watches the uptime, latency and errors of the booking, reservation and property systems.
- Industry
- Hotel
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- IT Manager
- Code
- ENG-14
It watches the booking engine, the central reservation system interfaces, channel manager rate and availability delivery, property management system links, point-of-sale posting and key encoders at each hotel against their service objectives, tracks error-budget burn and tunes alerts so that they page only on what guests and hotels feel. It writes the reliability report by system and hotel and creates or updates alert rules and dashboards, sending anything that silences a paging alert for approval.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the monitoring system: availability, latency, error rates, channel delivery delays and alert history for the systems and hotels named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to IT Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the monitoring system: it creates or updates alert rules and dashboards. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The service objectives for each hotel system, the alert catalogue, on-call rotas and the definition of a hotel-affecting outage.
Reads from
the monitoring system: availability, latency, error rates, channel delivery delays and alert history for the systems and hotels named.
Acts in
the monitoring system: it creates or updates alert rules and dashboards.
Hands back
An object with period, systems (a list, each with system, availability_percent, objective_percent, budget_left_percent and incidents), worst_properties (a list), channel_delay_breaches, alert_changes (a list, each with alert, change and reason) and actions (a list).
Asks a person when
The change silences, deletes or lowers the severity of a paging alert, or changes a service objective.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Booking engine availability objective (%) | 99.9 | Monthly availability target for direct booking. |
| Rate and availability delivery delay that alerts (minutes) | 5 | Updates not reaching the channel manager in this time raise an alert, as stale inventory causes overbookings. |
| Error-budget burn rate that pages | 14.4 | Burn at or above this pages on-call. |
| Alerts a week that make an alert noisy | 5 | A non-actionable alert firing more than this is tuned. |
| Reliability report cadence | weekly | How often it writes the report. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Judge the booking engine against 99.9 percent and page on-call when error-budget burn reaches 14.4.
- Alert when rate or availability updates take longer than 5 minutes to reach the channel manager.
- Alert on symptoms guests and hotels feel (bookings failing, check-in blocked, keys not encoding, charges not posting), not on internal metrics alone.
- Tune any non-actionable alert firing more than 5 times a week; never silence a paging alert without the IT Manager.
- Write the reliability report weekly, by system and by hotel.
See the Hotel Systems Monitoring Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.