Answers · Support telemetry

How much support telemetry is enough without drowning ops?

← All answers

Direct answer

Sample routine health events and raise verbosity only after repeated failures, support opt-in, or a known affected cohort. Aggregate BLE disconnect reasons daily instead of streaming raw logs nonstop. For example, a gateway can send hourly counters by firmware version, then attach a short trace only after three failed sensor reconnects.

Published August 2026 · Last technically reviewed August 2026

Need a second opinion on architecture?

We help connected product teams across BLE, Android, backend, and cloud before expensive rework starts.