Memfault Metric Best Practices

At the end of each heartbeat interval, reset the counters and information for almost all metrics. Each metric should accumulate counts only throughout the duration of the interval, report the value at the end of the interval, and then start a new count.
Use all lowercase metric names, and use underscores between words.
Namespace each metric (eg wifi_ prefixing all WiFi-related metrics)
Metric names can be long, but we recommend keeping them below below 32 characters for readability.

Firmware Stability Metrics

Crash-Free Hours

We recommend using Memfault Issues to understand the stability of your devices & firmware

Core Device Operational Metrics

Functionality

Every IoT device performs one or more core functions. These core functions can either fail or succeed. Memfault highly recommends tracking the number of attempts, successes, and failures of each of these core functions.

For a smart lock manufacturer, these might include:

of unlock attempts per interval
of unlock attempts per interval that resulted in successfully unlocking
of unlock attempts that resulted in a failure to unlock

Same as the above three, but for locking

Memfault Metric Best Practices

Firmware Stability Metrics

Core Device Operational Metrics

Functionality

of unlock attempts per interval

of unlock attempts per interval that resulted in successfully unlocking

of unlock attempts that resulted in a failure to unlock