Towbar separates a desired configuration, a deployment attempt, and the state observed afterward. Start with the question you need to answer, then check the timestamp and scope of the result. A successful deployment does not guarantee that a workload is healthy now; a missing measurement does not mean zero usage.
A practical investigation
- Open the affected server, app, or resource and check its latest state and observation time.
- Read the most recent deployment or operation result. Open its logs at the failing stage if it did not finish.
- Compare the same time range on the Performance page. Gaps mean Towbar did not receive measurements for that interval.
- If a rule fired, open the incident to see the trigger, graph, and separate delivery results.
- If the control plane itself is unavailable, run
sudo towbar doctor on its host and follow Troubleshooting.
The monitoring concepts page explains the difference between allocation, measured usage, and health. Scout Agent supplies continuous host and container measurements; deployment and server checks still work without it. Last modified on September 26, 2026
