You can also export data directly from a single device's detail page, making
it easier to pull a single device's history for offline analysis or sharing with
hardware teams.
Issue Chart: Trace Count Over Time cards now support a "Software Version"
group-by option, letting you see trace volume broken down by the versions of
software running across your fleet. This makes it easy to confirm whether a bug
affects a specific release or spans multiple versions.
Added a
Memfault MCUmgr command group for
Zephyr, enabling FOTA via MCUmgr (SMP over BLE) without a secondary interface
Improved nRF Cloud CoAP: data now uploads directly to the /chunks endpoint
without requiring CONFIG_MEMFAULT_HTTP_ENABLE, and supports automatic
project routing via Project Key
Refactored Zephyr HTTP client to use native zsock_ socket functions,
removing the POSIX API compatibility layer requirement
Added optional watchdog interrupt return behavior via
MEMFAULT_FAULT_HANDLER_WATCHDOG_RETURN, and ESP-IDF v6 compatibility
Android: [v5.8.0] - 2026-03-26 and [v5.7.0] - 2026-03-10
Added uptime and boot_id to metrics and reports, with optional
uptime-based timestamp adjustment for more accurate metric aggregation across
reboots
Added Bluetooth disconnect metrics (bluetooth.disconnect,
bluetooth.disconnect_reason, bluetooth.disconnects) collected via statsd
Fixed battery metrics over-writing on unchanged values (reducing up to ~500
MB/day of unnecessary storage) and fixed diskstats bytes-written being
over-reported by 8×
Added automatic sysfs battery metrics when a battery node is present, plus a
new battery_soh_pct State of Health metric, with no extra configuration
needed
Log filter configuration can now be pushed from the server via device
config, allowing log verbosity to be adjusted remotely without changing
on-device settings
Added min/max tracking option for individual metric keys alongside averages
Fixed a crash in journald log collection when encountering empty or malformed
cursor files
Add the --org-token option for authenticating with an Organization Auth
Token (OAT). This is now the recommended way to pass OATs to the CLI.
Previously, the documented approach was to pass the OAT via --password:
A new Linked Devices bar on the Device Detail page makes related devices
permanently visible without expanding the header. For products where a gateway,
companion app, or companion hardware are paired to the primary device, this
surfaces those relationships right where you need them during debugging.
Copying from the Log Explorer now produces clean, tab-separated output
(timestamp, level, message) ready to paste into a spreadsheet or bug report.
Multi-row selection with keyboard shortcuts is also supported, making it faster
to grab exactly the lines you need.
2026-04-07T05:00:04+00:00 INFO Ready for sync with companion app MFLT0000619 661431 1994933 Production 1.1.0 pvt sync_prep:45 2026-04-07T05:00:04+00:00 INFO Ready for sync with companion app MFLT0000612 661431 1994270 Production 1.1.0 pvt sync_prep:45 2026-04-07T05:00:04+00:00 INFO Ready for sync with companion app MFLT0000631 Production 1.1.0 pvt sync_prep:45
A new Linked Devices bar on the Device Detail page shows paired devices at
a glance without expanding the header.
Log Explorer copy now produces clean tab-separated output (timestamp,
level, message); multi-row keyboard selection added.
Organization Auth Tokens can now be created with restricted permission
sets, giving Org Admins finer-grained access control - especially useful for
SSO integrations.
Alerts can now be archived, and the alerts UI can be hidden per-project as
a contract setting.
Charts that previously supported only a single segment now have a segment
selector in the footer, letting you switch the applied comparand without
recreating the chart.
The nRF Cloud Pricing Calculator is now available at
nrfcloud.com/pricing/calculator, using the same logic as invoicing and the
Cost Control Center.
Fix a bug where upload-yocto-symbols and upload-elf-symbols would fail on
Python 3.14 with tarfile.AbsoluteLinkError when extracting tarballs that
contain absolute symlinks (e.g. Yocto's /etc/localtime).
New self-serve customers signing up on app.nrfcloud.com are now
automatically redirected into the Memfault experience after signup,
streamlining onboarding for nRF Cloud customers.
When using
Bulk Device Upload,
CSV device upload error messages are now clearer when specified hardware
versions don't yet exist.
ESP8266 support has been removed from the SDK; Memfault's cloud no longer
processes ESP8266 data. Contact support if
you need migration assistance.
Added Ambiq Apollo4/Apollo510 coredump storage via MRAM, enabled with
CONFIG_MEMFAULT_COREDUMP_STORAGE_AMBIQ_MRAM=y
Added ESP-IDF support for chunked OTA HTTP downloads to reduce RAM usage
(automatically enabled with CONFIG_ESP_HTTPS_OTA_ENABLE_PARTIAL_DOWNLOAD=y)
Added memfault_zephyr_port_http_periodic_upload_enable() to toggle periodic
uploads at runtime, and memfault_zephyr_port_http_periodic_upload_enabled()
to query upload state
The Issue List page now shows trace volume trend charts for each issue,
covering the last 14 days, 8 weeks, or 12 months. You can now spot growing
problems, stable regressions, and recovering issues without opening each one
individually.
Improved Software Version Filtering in Device Search
The software version filter in
Device Search
has been overhauled. It now lives in a dedicated filter panel with support for
AND conditions, regex, semver comparison operators, and "any of" / "not any
of" matching - making it much easier to precisely target device populations
across complex version landscapes.
Added issue trend sparklines on the Issue List page (14 days, 8 weeks, or
12 months), making it easy to spot growing or recovering issues at a glance.
Rebuilt the software version filter in Device Search with a dedicated
panel supporting AND conditions, regex, semver operators, and "any of" / "not
any of" matching.
Sessions can now be archived from Project Settings to hide them from the
Timeline (visible in debug mode only).
The device Timeline now inserts visual gaps in swimlanes at reboot
boundaries, preventing misleading data interpolation across reboots. This
makes it immediately clear when a metric or session span crossed a device
restart, giving you a more accurate picture of device behavior over time.
The Notes field on Releases now uses a rich Markdown editor and viewer.
Teams can format release notes with headers, lists, code blocks, and links -
making it easier to communicate what changed in each build to everyone on the
team.
Added Bluetooth quality metrics: RSSI, SNR, TX power, BLE scan results, and
retransmission counts
Added rich connectivity metrics: IPv4/IPv6 status, Wi-Fi RSSI moving average,
channel hop and roaming counters, Wi-Fi OUI, and Wi-Fi disconnect sessions
Added new heartbeat metrics for batterystats states (camera, video,
flashlight, bluetooth, cellular, screen wake, and more); added USB contaminant
and low memory kill event reporting
Added configurable WTF ignore patterns to suppress known-harmless Android
system log noise
Building on the saved issue search feature shipped in August, you can now
subscribe to daily or weekly email digests for any saved search. Each digest
highlights new and regressed issues in your search results, ranked by fleet
impact - so your team stays informed without having to check the dashboard
manually.
🧪 Custom Device Overview with Embedded Dashboards
The Device Details Overview has experimental support for embedding a
dashboard with the slug device-details, automatically scoped to the individual
device. This unlocks fully custom per-device views - making the device detail
page as informative and tailored as your fleet-level dashboards. Please
Added daily and weekly email digest subscriptions for saved issue
searches, surfacing new, regressed, and top issues by fleet impact.
Device Details Overview tab has experimental support for embedding a custom
dashboard (slug: device-details) scoped to a single device, enabling SQL
Cards and per-device Metric Charts.
Added 9 new built-in BLE connection metrics for Zephyr when CONFIG_BT=y,
including bt_connection_rssi, bt_connected_time_ms, bt_disconnect_count,
and more
Added MEMFAULT_METRICS_SESSION_RESET() API to discard an active session
without emitting a metric report
Added RRAM and MRAM coredump storage backends for Nordic nRF54L and nRF54H
series devices
Improved FileSystem_BytesFree metric to auto-detect mount points from Zephyr
device tree fstab entries; fixed potential WiFi stack overflow on nRF70 during
HTTP uploads
]]><![CDATA[August 2025]]>https://docs.memfault.com/changelog/2025/08/312025-08-31T00:00:00.000ZImproved Linux Support
We've introduced Python crash support and custom trace capture for Linux
devices. These updates close observability gaps where Python apps mix native
code or where failures don't trigger kernel crashes. With full Python stack
traces and structured custom traces integrated directly into Memfault Issues,
you can now capture a broader range of problems, see them grouped fleet-wide,
and get the same alerts and contextual data you rely on for other issues.
Managing issues across large and fragmented fleets just got much easier. You can
now save filtered issue searches, pin your favorites to the sidebar for fast
access, and even subscribe to scheduled email summaries that notify you of
changes in the issues that matter most. This ensures your team gets
higher-signal alerts without the noise.
Enhanced Software Versions page with improved filtering, search, and
version details, making it easier to find and analyze relevant software
releases and active device usage.
Added normalization option for over-time metric charts, allowing device counts
to be displayed as a percentage of active devices for easier comparison across
segments and changing fleet sizes.
You can now tag team members in issue comments, automatically notifying them
by email with a direct link to the comment.
Added support for comparison operators in software version filters
(>, >=, <, <=, !=), making it easier to search, filter, and analyze device
and issue data across version ranges.
Added the ability to save, share, and manage issue searches (with options to
pin personal favorites in the sidebar) for faster access and collaboration.
added a new test command for simulating hangs in ISRs
improved NMI exception capture
fixed a build issue in the nRF-Connect SDK port
📈 Added
Zephyr:
Add a new test command, mflt test isr_hang, which will cause a busy loop
hang inside a k_timer, which normally is executing from an ISR context.
The system will only exit this condition if there is a watchdog or other
higher-priority interrupt capable of preempting the k_timer ISR. The
qemu sample app
is updated to enable a watchdog which generates an NMI exception, caught by
Memfault.
Added a debug print when uploading data using
CONFIG_MEMFAULT_HTTP_PERIODIC_UPLOAD that shows the bytes sent:
[00:09:45.821,000] <dbg> mflt: memfault_platform_log: Uploaded 118 bytes of Memfault data
Only enabled when debug level prints are enabled for Memfault
(CONFIG_MEMFAULT_LOG_LEVEL_DBG=y).
🛠️ Changed
Zephyr:
NMI exceptions are now properly handled. Prior to this change, a coredump
was captured on NMI exceptions but the MSP context was not fully unwound and
the NVIC state was not included in the trace data.
Add a new Kconfig option,
CONFIG_MEMFAULT_COREDUMP_NVIC_INTERRUPTS_TO_COLLECT, which controls the
existing memfault_platform_config.h setting
MEMFAULT_NVIC_INTERRUPTS_TO_COLLECT for Cortex-M targets. The default now
is to collect all NUM_IRQS as defined by Zephyr, which on many platforms
will increase from the previous default of 32. This improves the
out-of-the-box information at the cost of 44 bytes in coredump storage
consumed per additional 32 interrupts. Some example deltas shown below,
including the byte delta in the stored coredump:
Platform
Previous Default
New Default
Byte Delta
nRF52840
32
64 (*48, rounded up to nearest multiple of 32)
+44
nRF91
32
96 (*65 rounded up)
+88
nRF53
32
96 (*69 rounded up)
+88
STM32F407
32
96 (*82 rounded up)
+88
STM32H7B0
32
160 (*155 rounded up)
+176
STM32H563
32
160 (*155 rounded up)
+176
To restore the previous default, set
CONFIG_MEMFAULT_COREDUMP_NVIC_INTERRUPTS_TO_COLLECT=32.
nRF-Connect SDK:
Fix a build issue impacting some nRF54 series chips related to reboot reason
decoding. Thanks to @grochu for providing the
fix in #94 🎉!
This release adds an example recipe for a systemd service that depends on
memfaultd. Additionally it changes the query frequency of eMMC lifetime
metrics.
Added
Added an example service that depends on memfaultd. This is useful for when
you want to run some code after memfaultd has finished starting.
Changed
Changed the read interval for eMMC lifetime values to only happen once an hour
regardless of configuration. The lifetime values will change very
infrequently. Reading them at a lower frequency can help lower CPU utilization
and reduce eMMC controller wakeups without sacrificing any resolution. This
can improve battery life for battery powered devices.
This release adds support for Python based stacktraces, as well as a few minor
changes. Additionally we've made some changes to flash lifetime metrics, and how
they're collected.
Added
Add generic custom trace support
This allows you to send text based backtraces to memfaultd.
They can be sent via the memfaultctl save-trace command
They can also be sent via /v1/trace/save local endpoint
Added Python stack trace support
Python stack traces utilize the above custom backtrace support
By integrating pyfault you can send
backtraces directly from a crashing python process.
Add new virtual memory metrics from /proc/vmstat. These are represented as
the following keys:
memory/vm/swaps_in_per_second
memory/vm/swaps_out_per_second
memory/vm/pages_in_per_second
memory/vm/pages_out_per_second
Added OUI (Organizationally Unique Identifier) collection for network device
identification and troubleshooting
Changed
Changed flash lifetime metrics to use pct_remaining format instead of
previous representation, providing clearer visibility into remaining device
lifespan
Fixed
Fixed MMC lifetime reading where memfaultd would attempt to read lifetime
values from older MMC devices that don't support this feature
Fixed handling of invalid individual lifetime values - they no longer cause
the entire lifetime collection to fail
Fixed overly verbose device info logging that was cluttering log output
Fixed build configuration for macOS by removing
--compress-debug-sections=zlib from cargo config that was causing
compilation issues
Fixed unit test reliability by properly mocking boottime_ms values
]]><![CDATA[July 2025]]>https://docs.memfault.com/changelog/2025/07/312025-07-31T00:00:00.000ZA Summary of Fleet Health Delivered to your Inbox
We have introduced a weekly summary email, sent to all users on an account, that
gives you visibility into the growth and health of your fleet, and your teams
usage of Memfault. This summary will keep you up-to-date without having to
navigate through multiple dashboards or between multiple projects.
The Fleet Health Summary includes key information on changes week over week,
including active devices, top software versions, most popular dashboards and,
critically, Device Vitals. The summary covers your top three projects (by device
count) and each project will be listed separately in the summary email.
Quickly Identify a List of Devices Impacted by Issues
We have added a new filter to
Device Search
-'Impacted by Issues' - that lets users quickly identify a list of devices
impacted by any Issue, a specific Issue or a set of Issues. The filter also
includes the option to further refine your list by the number of traces of the
Issue(s) per device.
This filter adds another powerful tool for helping users gauge impact of issues
across the fleet and quickly identify and investigate devices that have been
impacted.
Introduced a new "Impacted by Issues" device search filter, allowing users to
identify devices based on their issue impact status and view trace counts,
with customizable filtering options for enhanced device management.
Customers can now receive a "Weekly Summary" email highlighting key
organizational events, such as new active devices and popular dashboards, with
customizable content options.
Introduced a new Quotas system and interface, simplifying device entitlement
management with new visibility levels and plans, enhancing understanding of
resource usage through project and organization-level overview pages.
Linux trace signatures now include the running process name. This may result
in a temporary increase in new issue counts for existing projects.
You can now update issue filters directly on an issue chart card without
leaving the page or recreating the chart.
Released a new date picker dropdown with more human-readable relative date
formats for easier date selection.
Added a "Find Impacted Device" button on the issues list page to quickly
navigate to the device list with the impacted issues filter pre-applied.
Added the ability to create, edit, and delete tiles on the Device Detail Page,
including new Markdown and Device Attribute tiles, plus configurable
thresholds for Device Vital tiles with visual status indicators.
Apply a compatibility fix for upcoming Zephyr 4.2.0, fixing the size of the
net_mgmt callback mgmt_event parameter. Thanks to @rlubos for providing
the fix in #91
🎉!
Add support for the ESP32 chip on Zephyr, adding to the existing support for
ESP32-S3 and ESP32 C series chips.
Add support for building the Memfault SDK on the native_sim board. Note
that Memfault does not support reboot tracking or coredumps on this target,
but other features are supported.
Add a MEMFAULT_ENABLE_WARNING(warning) macro complementing the existing
MEMFAULT_DISABLE_WARNING(warning) macro. This macro is only implemented
for GCC + Clang.
Zephyr:
Remove the External Module logic, used to support multiple Zephyr versions,
and instead use the normal Zephyr module Kconfig path specifier. There
should be no user-facing changes from this change. It addresses an issue
with Kconfig symbol linting.
In the
Zephyr QEMU sample app,
add the --param=min-pagesize=0x1000 compiler option, which will catch
dereferences to low memory addresses. This is only for static analysis
purposes and does not affect any behavior.
ESP-IDF:
The heartbeat metrics timer is now enabled by default when
CONFIG_MEMFAULT_DEEP_SLEEP_SUPPORT=y. Version 1.25.0, which added deep
sleep support, had disabled the normal heartbeat metrics timer by default.
The default behavior can be overridden with the Kconfig option
CONFIG_MEMFAULT_METRICS_HEARTBEAT_TIMER_ENABLE.
nRF-Connect SDK:
Replace use of LTE_LC_ON_CFUN with NRF_MODEM_LIB_ON_CFUN for nRF-Connect
SDK v2.8.0+. This deprecated API is scheduled to be removed in the next
nRF-Connect SDK release.
This is a feature release of the Memfault Firmware SDK. The main new feature
released in this version is support for tracking metrics through deep sleep on
ESP32 devices. Full release notes are below.
Add a new choice config CONFIG_MEMFAULT_REBOOT_REASON_GET. By default,
CONFIG_MEMFAULT_REBOOT_REASON_GET_HWINFO=y, which is supported by
imply CONFIG_HWINFO in the overarching MEMFAULT symbol. This default
enables better reboot reasons out-of-the-box via Zephyr's hwinfo module.
The fall-back option is CONFIG_MEMFAULT_REBOOT_REASON_GET_BASIC, which
provides a simple implementation. As before, users can override the default
implementations with CONFIG_MEMFAULT_REBOOT_REASON_GET_CUSTOM=y.
Add a new Kconfig setting, CONFIG_MEMFAULT_ENABLE_REBOOT_DIAG_DUMP, to
print the reboot reason code on system boot, for debugging purposes. This
feature is enabled by default. It can be disabled with
CONFIG_MEMFAULT_ENABLE_REBOOT_DIAG_DUMP=n.
Add a boot_time_ms metric, which tracks how long the system takes to boot
the application. Can be disabled with CONFIG_MEMFAULT_METRICS_BOOT_TIME=n.
Add new builtin Wi-Fi metrics, enabled by default when CONFIG_WIFI=y, and
can be disabled with CONFIG_MEMFAULT_METRICS_WIFI=n:
wifi_beacon_interval
wifi_dtim_interval
wifi_frequency_band
wifi_primary_channel
wifi_security_type
wifi_sta_rssi
wifi_standard_version
wifi_twt_capable
wifi_tx_rate_mbps (Zephyr 4.1.0+ only)
These add on top of the existing Zephyr Wi-Fi metrics:
wifi_ap_oui
wifi_connected_time_ms
wifi_disconnect_count
Add an option to upload logs by default when using
MEMFAULT_HTTP_PERIODIC_UPLOAD, controlled with the Kconfig symbol
MEMFAULT_HTTP_PERIODIC_UPLOAD_LOGS. This can also be controlled at runtime
with the included API
memfault_zephyr_port_http_periodic_upload_logs(bool enable)
Add a new Kconfig option, CONFIG_MEMFAULT_PLATFORM_TIME_SINCE_BOOT_CUSTOM,
to provide a custom implementation of
memfault_platform_get_time_since_boot_ms() in your application. The
default is an implementation using k_uptime_get().
ESP-IDF:
Add a boot_time_ms metric, which tracks how long the system takes to boot
the application. Can be disabled with CONFIG_MEMFAULT_METRICS_BOOT_TIME=n.
Add support for tracking metrics across ESP32 deep sleep cycles, enabled
with the Kconfig CONFIG_MEMFAULT_DEEP_SLEEP_SUPPORT=y. To utilize this
feature, these functions must be called by the application:
memfault_platform_deep_sleep_save_state() Must be called just prior to
entering deep sleep (esp_deep_sleep_start())
memfault_platform_deep_sleep_restore_state() Must be called before
memfault_platform_boot() in the application startup sequence.
This feature includes built-in metrics for tracking deep sleep:
deep_sleep_time_ms - time spent in deep sleep
active_time_ms - time spent out of deep sleep
deep_sleep_wakeup_count - number of times the device woke up from deep
sleep
There are several Kconfig options for controlling the deep sleep feature,
including controlling the heartbeat trigger and HTTP periodic upload. See
menuconfig "Memfault deep sleep support" or
ports/esp_idf/memfault/Kconfig
for details.
Add new metrics tracking flash usage:
flash_spi_erase_bytes
flash_spi_write_bytes
flash_spi_total_size_bytes
Add capture of the ESP-IDF Task Watchdog stuck task list in coredumps. This
is enabled by default if ESP-IDF Task Watchdog is enabled, and can be
disabled with the Kconfig
CONFIG_MEMFAULT_COREDUMP_CAPTURE_TASK_WATCHDOG=n.
CONFIG_MEMFAULT_REBOOT_REASON_GET_CUSTOM is now a choice in the new choice
config CONFIG_MEMFAULT_REBOOT_REASON_GET. As a result, it will be the
default choice if CONFIG_MEMFAULT_NRF_CONNECT_SDK=y instead of being
imply-ed by CONFIG_MEMFAULT_NRF_CONNECT_SDK to work around the
restriction that choice configs cannot be selected. As before, users can
override this behavior with CONFIG_MEMFAULT_REBOOT_REASON_GET_CUSTOM=n.
ESP-IDF:
Rename CONFIG_MEMFAULT_TIME_SINCE_BOOT_CUSTOM ->
CONFIG_MEMFAULT_PLATFORM_TIME_SINCE_BOOT_CUSTOM. A new ESP-IDF port choice
Kconfig CONFIG_MEMFAULT_PLATFORM_TIME_SINCE_BOOT now supports 3 settings
for platform time since boot:
MEMFAULT_PLATFORM_TIME_SINCE_BOOT_ESP_TIMER default, suitable for most
applications
MEMFAULT_PLATFORM_TIME_SINCE_BOOT_DEEP_SLEEP applicable for deep-sleep
applications
MEMFAULT_PLATFORM_TIME_SINCE_BOOT_CUSTOM disable builtin
implementations and implement a custom
memfault_platform_get_time_since_boot_ms()
Renamed the spi_flash_chip_id metric (added in 1.23.0) to
flash_spi_manufacturer_id.
Renamed the wifi_auth_mode metric to wifi_security_type to more
accurately indicate the property being measured.
General:
Add the demo component to the default set of components added to an
Eclipse project when using the
eclipse_patch.py
utility. The default components can be overridden with the --components
argument.
Coredumps no longer include the device serial by default. The uploading
serial (passed to the chunks endpoint) is instead used to identify the
device associated with the coredump. Enabling
#define MEMFAULT_EVENT_INCLUDE_DEVICE_SERIAL 1 in
memfault_platform_config.h will include the device serial in coredumps.
Add a new API, memfault_log_get_unsent_count(), which returns the log
count and size in bytes of unsent logs in the log buffer. This can be used
inside memfault_log_handle_saved_callback() for example to drain the
packetized logs when a certain watermark is reached.
ESP-IDF:
Add a Kconfig option, CONFIG_MEMFAULT_TIME_SINCE_BOOT_CUSTOM, which when
set =n, enables using a custom implementation of
memfault_platform_get_time_since_boot_ms().
Add 2 new metrics for tracking raw network bytes rx / tx. These metrics
track network IO traffic on the default netif:
network_rx_bytes
network_tx_bytes These metrics are enabled by default, and can be
disabled with CONFIG_MEMFAULT_METRICS_NETWORK_IO=n
Rename the thread stack usage measurement variable included in coredumps
when MEMFAULT_COREDUMP_COMPUTE_THREAD_STACK_USAGE is enabled from
high_watermark to stack_unused. This change is to make the
implementation more readable. The Memfault backend is updated to process
both the old and new formats.
FreeRTOS-detected stack overflows (via vApplicationStackOverflowHook) will
now be correctly tagged as Stack Overflow for the trace reason in
Memfault, instead of Assert.
Added support for MEMFAULT_REBOOT_REASON_CLEAR in the
ports/nrf5_sdk/resetreas_reboot_tracking.c
implementation, by default enabled (like other ports). This permits opting
out of the auto-clearing of the NRF_POWER->RESETREAS register, in case the
user needs it after the function runs.
FreeRTOS (including ESP-IDF):
Fix incorrect computation of per-thread stack usage metrics
(MEMFAULT_FREERTOS_COLLECT_THREAD_METRICS). Before this fix, the returned
values had 2 errors:
the value is the unused stack space, not the used stack space
on platforms where sizeof(StackType_t) is not 1 byte, the numerator
when computing percentage is incorrectly scaled down by
sizeof(StackType_t), resulting in significant under-reporting of the
stack usage percentage. Users can apply device and software version
filtering on dashboards to filter out reports from devices that are
running an old version of the SDK.
ESP-IDF:
Fix a potential issue that would cause the wrong implementation of
memfault_platform_time_get_current() to be included in the final link,
when CONFIG_MEMFAULT_SYSTEM_TIME=y is enabled (default).
CONFIG_MEMFAULT_ENABLE_REBOOT_DIAG_DUMP now defaults to y instead of
n, to print out the reboot reason on boot. Disable it with
CONFIG_MEMFAULT_ENABLE_REBOOT_DIAG_DUMP=n.
Added new SDK Setting to upload collected Android Bugreports immediately
outside of the periodic MAR batch task. Added new trace_id and extra_info
fields to BugReportRequests.
Fixed reporting of the new Wi-Fi metrics to visualize on the device timeline
more appropriately. Fixed an error when recording null per second metrics.
sum_matching captures 1 integer, and sums all captured values in the
heartbeat.
distribution_minmeanmax captures 1 double, and generates a min/mean/max
distribution for all captured values in the heartbeat.
string_property captures 1 string, and reports the latest value for that
string.
Added tracking of the metered, temporarily unmetered, and roaming network
capabilities in HRT.
Added a connectivity.metered.latest heartbeat metric for tracking metered
network usage.
Added new disk wear and disk write Device Vital heartbeat metrics. eMMC/UFS
lifetime estimation and version stats are collected from the Health HAL
implementation, falling back to a hardcoded UFS or eMMC filepath if not
implemented. Bytes written each heartbeat is collected by reading the sectors
written value from /proc/diskstats for matching physical devices in
/sys/block multiplied by the sector size to get a value in bytes.
disk_wear.<source>.lifetime_remaining_pct.latest captures the lifetime
remaining estimation for type A flash in increments of 10%. The source can be
one of: "mmc0", "624000.ufshc", or "HealthHAL".
disk_wear.<source>.lifetime_b_remaining_pct.latest captures the lifetime
remaining estimation for type B flash in increments of 10%. The source can be
one of: "mmc0", "624000.ufshc", or "HealthHAL".
disk_wear.pre_eol.latest captures the pre-EOL status of consumed reserved
blocks, as "Normal", "Warning", or "Urgent".
disk_wear.version.latest captures the version as described from the vendor
implementation of the Health HAL.
disk_wear.vdc.bytes_written captures the bytes written for that heartbeat.
Added per-app CPU usage metrics. The CPU usage percentage for each heartbeat
is collected by parsing /proc/<pid>/stat/ for system and user time
(stime + utime) divided by the total usage (sum of all fields from
/proc/stat).
By default, the SDK will only create heartbeat metrics for a defined set of
"interesting" processes. Please reach out to customer support to configure
this set.
Otherwise, the top 10 processes exceeding the 50% CPU usage threshold will
also be recorded. Please reach out to customer support to configure these
thresholds.
Added new general connectivity metrics reported by NetworkCapabilities.
connectivity.roaming captures whether the connected network is roaming. This
metric is only available in HRT, on API 28+.
connectivity.unmetered_temporarily captures whether the connected network
was temporarily unmetered. This metric is only available in HRT, on API 30+.
connectivity.metered.latest captures whether the connected network is
metered.
Added new basic Wi-Fi from the WifiInfo reported by NetworkCapabilities.
connectivity.wifi.frequency captures the Wi-Fi frequency of the associated
link in MHz.
connectivity.wifi.link_speed_mbps captures the current link speed of the
associated link with the highest RSSI in Mbps.
connectivity.wifi.security_type captures the security type of the current
802.11 network connection as a human-readable string.
connectivity.wifi.standard_version captures connection Wi-Fi standard as a
human-readable string.
connectivity.wifi.lost_tx_packets_per_second captures the average rate of
lost transmitted packets, in units of packets per second.
connectivity.wifi.retried_tx_packets_per_second captures the average rate of
transmitted retry packets, in units of packets per second.
connectivity.wifi.successful_tx_packets_per_second captures the average rate
of successfully transmitted unicast packets, in units of packets per second.
connectivity.wifi.successful_rx_packets_per_second captures the average rate
of received unicast data packets, in units of packets per second.
screen_doze captures whether the display is dozing in a low power state
(link).
flashlight captures whether the flashlight was turned on.
bluetooth captures whether Bluetooth was enabled.
usb_data captures whether a USB connection was established (as reported by
android.hardware.usb.action.USB_STATE).
cellular_high_tx_power captures whether the modem spent more of its time at
the highest power level versus any other level.
nr_state captures the service level of the 5G network that's connected
(link).
Updated comments on various batterystats fields. More improvements to come in
clarifying the name and use of batterystats metrics!
Dumped any existing logs when continuous logging starts, to retain logs
captured from before a reboot.
Added control over the maximum age of sampled data, to match the controls over
unsampled data.
Added support for parsing the binary log buffers (events, security, stats)
with continuous logs.
Modified dumpstate to write bugreports to /data/misc/MemfaultBugReports
instead of to Bort's app dir. This is necessary for Android 15 support and CTS
compliance to work around neverallow sepolicy rules. This also allowed
deleting the custom bort_app_data_file app label for the Bort app.
This release adds an additional metric for tracking the health of eMMCs as well
as a change to how built-in and collectd-based metrics interact to improve the
user experience for teams using a combination of the two.
The Lifetime Estimation B value for monitored eMMCs is now reported as
diskstats/<disk>/lifetime_b_pct
A warning is now emitted when there is an issue parsing the output from
memfault-device-info in memfault-core-handler. Previously, this would
cause coredump collection to fail silently.
Built-in CPU, memory, and thermal metrics can now be disabled individually
with the new metrics.system_metric_collection.{cpu,memory,thermal}.enable
boolean config.
memfaultd's .cargo/config.toml now sets --compress-debug-sections to
zlib and --force-unwind-tables to yes by default. These settings enable
building efficient debug sections and binaries whose coredumps can be fully
processed. We strongly recommend using them with any Rust programs you intend
to monitor with Memfault.
collectd-based metrics that overlap with built-in metrics will now be
selectively filtered out if both are enabled based on whether the overlapping
built-in metric group itself is enabled. This allows for using a mix of
collectd-based metrics and built-in metrics more easily.
Fixed an issue with the diskstats/<disk>/bytes_written metric where it would
overflow when the diskstats counter wrapped. This would cause very large
readings to be sent. Whenever there is a potential overflow now the reading
will be discarded.
This release adds several new metrics for tracking flash wear, as well as a new
syslog log source. It also includes a config flag to enable legacy statsd metric
names, and a data retention check to the upload process. For more information on
the new metrics, check out the
docs.
Added metrics for tracking flash wear for mmc block devices like eMMC and SD
cards
diskstats/<disk_name>/bytes_written
diskstats/<disk_name>/lifetime_pct
diskstats/<disk_name>/manufacturer_id
diskstats/<disk_name>/name
Added syslog as a logs source. This adds support for messages in both RFC5424
and RFC3164 format sent over UDP. This is enabled with the syslog feature
which defaults to enabled.
Added a config flag to enable legacy statsd metric names. This will generate
metrics that follow the format generated by the collectd statsd server. This
is a helpful option for people looking to remove collectd as a dependency,
but keep the legacy format for metric keys. The config value can be found in
metrics>statsd_server>legacy_key_names.
Added time-based data filtering: When upgrading multiple devices' visibility
levels, the Memfault backend now tells memfaultd to only upload data from
the time of the change forward. This prevents unexpected large data uploads
from device history.
Added interface/<interface>/total_bytes/{tx,rx} metrics. These allow us to
track the total bytes sent over an interface over the course of an hour.
Added intelligent traffic distribution: Device initial connections now include
a random delay (up to 25% of the configured upload interval). This prevents
traffic spikes when many devices connect simultaneously, ensuring smoother
backend performance.
ram and loop disks are no longer tracked with diskstats in auto mode.
These are virtual disks, and provide little value when tracking metrics.
Add support for uploading ELF files without DWARF debug info.
]]><![CDATA[April 2025]]>https://docs.memfault.com/changelog/2025/04/302025-04-30T00:00:00.000ZSee the health of individual devices at a glance
We have updated the device Overview page to now include a snapshot of that
device's Vitals for the filtered time period. The Device Vitals visualizations
give both technical and non-technical users a quick and easy way to understand
the health and performance of that device without needing to track each metric
individually on the timeline.
The overview will automatically display data for the Device Vitals being
collected in your project and can be filtered to show performance over a
specific time range using the date picker. If you want more guidance on how to
start collecting Device Vitals for your project, take a look at our
technical documentation.
Modify the test command used in our public CircleCI job, to work around an
issue with
CircleCI's v2 container runtime,
which uses cgroupv2 instead of cgroupv1.
Improved support for run time tracking on FreeRTOS kernel version v11 and
later, by adding compile-time checks for possible configuration issues.
Add reboot reason decoding for the NXP RW61x chip series, using the
PMU.SYS_RST_STATUS register to determine the reset reason. Add the file at
ports/nxp/rw61x/pmu_reboot_tracking.c
to your project to make use of it!
Add reboot reason decoding for the SiLabs SiWx91x chip series. This
implementation supports Power On Reset, Pin Reset, and Software Reset
causes only. Please
reach out if you are
interested in other reset reasons. Add the file at
sdk/embedded/ports/silabs/wiseconnect/siwx91x/siwx91x_reboot_tracking.c
to your project to make use of it.
Add an
implementation of memfault_reboot_reason_get()
for the STM32H5xx series of MCUs, using the RCC-RSR register to determine
the reset reason. Add the file to your project to make use of it!
ESP-IDF:
Add 2 new out-of-box metrics:
spi_flash_chip_id : the 24-bit RDID value of the SPI flash chip, for
example "c84017" = GigaDevice GD25Q64 8MiB
esp_chip_revision : the ESP32 chip and revision, for example
esp32c6-0.0 or esp32s3-0.2
For ESP-IDF v5.5 and later, enable ggdb3 by default for enhanced
debugging. This is controlled with the Kconfig CONFIG_MEMFAULT_GGDB3.
Set the User-Agent to MemfaultSDK/<version> when sending HTTP requests to
Memfault.
Update the
nRF91 example
to enable the DATETIME subsystem, to tag SDK event and log data with
timestamps once the network connection is activated.
ESP-IDF:
Update the prv_panic_safe_putstr() implementation to perform better on
modern ESP-IDF versions (>=4.4.0). This function is used to output local
prints during panic handling.
Add a Kconfig CONFIG_MEMFAULT_DATA_CHUNK_HANDLERS_CUSTOM to allow
overriding memfault_esp_port_data_available() and
memfault_esp_port_get_chunk(). If other MCUs are forwarding data to an
ESP32 for transport, enable this option and provide definitions to handle
additional sources. By default, these functions only check the local device
for available chunks.
Correctly print the initial delay and period in seconds for the periodic
upload task. Previously, this info log print was using the value in
milliseconds.
Added support for log message filtering. This feature gives you the ability to
exclude log lines that are spammy or contain potentially sensitive information
from being uploaded to Memfault.
Added built-in logs-to-metric rules that increment counter metrics when
a systemd_restarts or oomkill event is detected. These are widely
applicable to most Linux distros, and represent a good base for metric
collection
Fixed a problem where large HRT files could take a long time to write. This
was due to the file writer not being buffered.
Fixed a race condition that caused the journald cursor to not be written.
This would lead to the journald log collector capturing duplicate log lines
if memfaultd is restarted.
Fixed a problem where daily heartbeats were being saved when they were not
enabled.
Combined the regex feature with the logging feature to simplify feature
management as log filtering and matching based on regexes becomes a key part
of our logging offering.
