📘 Monitoring Tools Reference
These are the tools available to verify whether data is flowing correctly and to investigate an issue when it isn't. The 🎯 Symptom Lookup and 🧩 Diagnostic Funnel journeys both refer back to this page — start here if you're not yet familiar with what each tool shows.
📈 Uptime Metrics
Whether a device sent data as expected, tracked on a daily, monthly, and yearly basis. Devices report data every 5 minutes, so uptime is calculated as the percentage of expected 5-minute intervals in which data was actually received.
Use it to check:
- ✅ Whether a device missed one or more reporting intervals.
- ✅ The uptime percentage for a device over a day/month/year, to spot patterns (e.g. consistently drops offline at a certain time of day).
- ✅ Historical trend — is this a one-off gap or a recurring issue?
When to use it: First stop for "is this device sending data reliably?" — before assuming a sensor or IoT hardware fault.
🌐 Offline Dashboard
Current connectivity status of each device — connected or not, right now.
Use it to check:
- ✅ Whether a device is currently online or offline.
- ✅ The list of all devices currently offline, across a site/zone.
When to use it: Quick, real-time check when someone reports "no data is showing" — confirms whether the device itself is reachable at all.
🚨 Data Integrity Alerts
Automated alerts raised when incoming data looks wrong, even if the device is online and sending data.
Alert types:
| Alert | Meaning | Common causes |
|---|---|---|
🔴 device_status | No data received from the meter. | Meter power supply issues; RS485 communication problems. |
🟠 no_flow | No flow detected — water flow rate is zero or below threshold. | Flow meter fault, closed valve, blocked line, incorrect installation. |
🟡 no_level_variation | Water level remains constant — no variation detected in tank levels. | Level sensor stuck/damaged, tank not actually being used, sensor miscalibration. |
🔵 water_balance_leakage | Water balance discrepancy detected across zones. | Unaccounted water — may indicate real leakage, or a metering/config error. |
When to use it: Use this when the device is online (per the Offline Dashboard) and sending data (per Uptime Metrics), but the data itself looks suspicious — flat, zero, or inconsistent with the rest of the system.
📶 IoT Telemetry
Live, per-device-ID view of connectivity and data transmission — whether the device is connected, and whether it's sending data every 5 minutes as expected.
Use it to check:
- ✅ Live connection status per device ID.
- ✅ Whether data is arriving on schedule, in near real time (more granular/immediate than Uptime Metrics, which is aggregated).
- ⚠️ If data is arriving but not reflecting on the dashboard, this points to a downstream technical issue rather than a device/connectivity problem, for example:
- Reverse flow condition (confirm via 🗄️ Data Validation — check the reverse flow flag on recent records — then fix via 🔄 Unit Reset).
- Device ID not configured correctly.
- Data format issue.
- Other configuration issues.
When to use it: Use this when Uptime Metrics/Offline Dashboard show the device as fine, but data still isn't showing up correctly — it tells you whether the problem is at the device/network level or further down the pipeline.
🗄 Data Validation
The recent raw data received into the database for a device — the actual readings as they landed, including flags such as the reverse flow flag.
Use it to check:
- ✅ What raw values were actually received and stored for a device, interval by interval.
- ✅ Whether a reverse flow flag is set on recent records — a common reason data arrives but doesn't show up correctly on the dashboard.
- ✅ Whether the stored data matches what's expected, independent of how the dashboard is displaying it.
When to use it: Use this alongside IoT Telemetry when data is arriving but not reflecting on the dashboard — Data Validation tells you exactly what was stored, including flags like reverse flow, so you can confirm the cause before taking action.
Fix: If a reverse flow flag (or similar stuck condition) is confirmed, resolve it from the 🔄 Unit Reset tab — see below.
🔄 Unit Reset
An admin action, per unit, to reset the device after confirming a condition such as reverse flow that is blocking data from registering correctly.
Use it to:
- ✅ Reset a unit after confirming a reverse flow condition via Data Validation or the daily reverse-flow alert in Google Chat.
- ✅ Reset a unit after correcting a misconfiguration found during a replacement/service activity.
When to use it: Only after confirming the cause (e.g. via Data Validation or Data Integrity Alerts) — resetting is the fix step, not a diagnostic step. The reset action is recorded in User Logs (unit level).
📝 User Logs
An audit trail of changes made in the system, available at three levels:
- Unit level — changes made to a specific device/meter (e.g. reconfiguration, resets).
- Industry level — changes made at the site/organization level.
- User level — actions taken by a specific user.
Use it to check:
- ✅ What changed recently, and who made the change — especially useful after a replacement/service activity or a configuration update.
- ✅ Whether a recent manual action correlates with when the data issue started.
When to use it: Use this whenever the timing of an issue lines up with a recent change (service visit, config update, replacement) — it's the fastest way to confirm or rule out a human/config cause.
⚡ Quick Reference: Which Tool First?
| Symptom | Start with |
|---|---|
| 🚫 No data at all showing for a device | 🌐 Offline Dashboard → 📈 Uptime Metrics |
| 📉 Data was fine, now intermittent | 📈 Uptime Metrics |
| ⚠️ Device online and sending, but values look wrong | 🚨 Data Integrity Alerts |
| 🤔 Device seems fine everywhere, but dashboard doesn't reflect data | 📶 IoT Telemetry → 🗄️ Data Validation |
| 🔃 Reverse flow suspected (data arrives but doesn't register) | 🗄️ Data Validation → 🔄 Unit Reset |
| 🛠️ Issue started right after a service/replacement/config change | 📝 User Logs |
Work top-to-bottom through this table before escalating — most issues resolve at the first or second tool without needing a full root cause investigation.