Health desk
See current customer impact and the next recovery action.
See current customer impact and the next recovery action.
What this feature is for
Health desk is the live operating surface for uptime, incidents, real-user speed, deployments, threats, and background work. It helps an operator decide what matters now. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
At least one monitored endpoint or connected signal; health becomes more useful as the app’s critical paths are represented.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Start with the impact summary, open the source evidence, assign an owner, and verify the fix through the same signal that detected the issue.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
The desk links impact to monitors, incidents, deployments, and provider evidence so a status color never has to stand alone. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
If health is quiet but customers report a problem, add the missing path or journey. If it is noisy, remove duplicate signals before muting the whole surface.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Use Health with Uptime monitors, Incidents & fixes, Alert delivery, and Activity. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.
