Layer Symptom Triage
Layer Symptom Triage
animation
iot
design-patterns
TipTry It: Layer Symptom Triage
For one IoT system you have seen or designed, write a three-row triage note before proposing a fix:
| Symptom | Layer to inspect first | Evidence to collect |
|---|---|---|
| Cloud bill or dashboard latency is rising | L3 edge processing and L4 accumulation | Messages per second forwarded, rollup ratio, query latency, retention policy |
| New device types break existing applications | L5 data abstraction and API contract | Application code that names vendor tables, unit-conversion rules, schema-change history |
| Outages stop local safety or comfort functions | L3 local autonomy and L2 connectivity | Backhaul-disconnect test result, buffered command behavior, local control-loop log |
Only commit to a redesign after each symptom has one measured signal. If the evidence points to different layers, treat the system as hybrid rather than forcing a single pattern.