Sentry

A direct booking site is a revenue channel with an availability requirement. When it throws errors at checkout, the cost is measured in bookings that did not happen, and nobody complains — they just go somewhere else.

Sentry is what tells you. The gap is attention: error dashboards are checked when someone remembers or when something has already gone badly wrong.

Connecting Sentry makes the state of your own software something you can ask about rather than somewhere you have to go. It is aimed at whoever maintains that software, which in a property company is usually one or two people with a lot of other responsibilities — exactly the people least likely to be watching a dashboard.

The pairing worth making is with your issue tracker. An error that recurs across many sessions is not a monitoring event, it is work — and moving it from one to the other is where most error dashboards quietly fail.

Once Sentry is connected, ProhostAI works with your issues and error data in plain language.

Read

• Search issues Find errors by project, frequency or recency. "What is failing most on the booking site this week?"
• Check an error’s detail See how often something is happening and who it affects.

Create & update

• Triage issues Assign, resolve or ignore issues as decisions are made.
• Raise work elsewhere Turn a recurring error into a ticket in your issue tracker.

Sentry connects through OAuth against your organisation, so ProhostAI never sees your password.

1. Open ProhostAI and go to Settings → Connections.
2. Search for Sentry and select Connect.
3. Sign in to Sentry and approve the permissions.
4. Ask what errors are most frequent to confirm it works.

• Access follows the connected account’s organisation and project permissions.
• Frequency matters more than novelty — an error affecting many checkouts is worth more attention than a rare exotic one.
• This serves whoever maintains your own software rather than your operations team.