May 2021
Heartbeat Metric Improvements
One of Memfault's most capable features is Metrics. With Metrics, you can determine how specific metrics on a single device correlate with each other to root cause performance and power regressions, or aggregate them on a Fleet level and determine whether the health of your Fleet of devices is improving over time!
We're announcing new features today which should help make our metrics feature more usable.
First, users can now view all the Metric names that have been received from Heartbeat events in the Settings → Metrics page. This allows for easy auditing of metric names and configurations.

If you find any that are stale or shouldn't be tracked anymore, you can archive them.
When Edit is clicked, users can configure the valid ranges for the metric, which will improve the displayed charts by normalizing the Y-axis to possible values. An example of where this could be useful is battery life, where the min and max values are 0-100.
Users can also specify a single value for Memfault to ignore, such as
0xffffffff
, which can represent the absence of a value.

These new features will enable developers and customer support representatives to more easily dig into the health of a single device and the entire Fleet.
That's not all though! We've made more improvements to symbol file uploading, bugreport filtering, and the archiving of software versions.