Improved 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.

Saved Issue Search and Summaries​

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.

A 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.

See 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.

New Search Features to Quickly Triage Issues and Find Outliers​

This month, we've made it easier to spot patterns and outliers across your Fleet in our Device and Issue search. These new capabilities level-up your filtering and sorting options, as well as add context-enriching calculations to help you understand the impact of an Issue at a glance.

Device Search now supports sorting on all columns—including Device Vitals, reboot counts, and custom filters—making it easier to surface anomalies. Plus, when filtering, the Report Count column is automatically shown to provide added context.

In Issue Search, you'll now see the percentage of impacted devices per Issue, giving you an instant sense of scale without needing to calculate Fleet size.

Improved Device Details Page​

We have been making a number of usability improvements to the Device Details page including streamlining the amount of information visible when first viewing the page. Below is the view when first viewing the Device details page, highlighting software version and last seen.

Expanding this section now reveals more details on the status, config state and Release information.

This is the first in a series of planned improvements to the Device Details page designed to make it easier, and faster to get to the information that really matters. These changes should also make the Device Details more usable for team members who may be less familiar with Memfault, or do not require the level of information available in the Device timeline.

Issue Charts Drilldown and Improved Tooltips​

The recently added Trace and Issue summary charts now also support drilldown and we have added more details to the tooltips available on hover when viewing these charts in your dashboards.

This combination of improvements should make it easier to analyze Issue data at a glance and investigate when you spot something unexpected. You can read more about the new issue summary charts in our docs.

New Trace and Issue Summary Charts​

We have introduced two new Issue Charts for looking at Trace or Issue count distributions between different populations of devices. These Charts allow grouping by Issue ID or Issue Reason and support comparisons of different data sets with Dashboard filters.

New Four-Eyes Approval Process for OTA Updates​

Cohorts can now be configured to require an additional Team member with the right permissions to approve a Release Activation before it will be executed. This adds an extra layer of assurance and security to the Device update process.

To activate this approval process, open the Cohort you want to enable it for, open the Settings tab, and select a Team that can approve Release Activations. Admins can create a new team under Admin → Teams. When activating a Release for this Cohort, a Release Activation Request will be created requiring approval from one of the selected team members before activation. Read more about this in the OTA documentation.

Organizing Metrics with Tags​

Metrics can now be assigned a customizable tag. Adding tags allows for better categorization of metrics and an improved search experience.

To try this feature, head to Project Settings → Metrics and select a Metric. In the Edit Metric modal window you can select or add new tags. For example, you could tag all metrics related to your battery performance with the tag battery. Read more about this the Metrics documentation.

Sidebar Customization​

We've shipped a set of customization features to help you keep important Dashboards front and center

• Add your Favorite Dashboards to the Sidebar from the All Dashboards page or on any individual Dashboard page.
• You can assign a custom emoji to each Dashboard by clicking the icon next to the Dashboard's name.
• You can choose to Pin a Dashboard for everyone in the Project. You can use this feature to highlight the most important Dashboards to your team.
• In addition to hiding the sidebar you can now drag to resize too.

Pin Metrics to refine the Device Timeline​

We enabled users to reduce the number of metrics shown on the Device Timeline by pinning what's most relevant for their projects.

• Under Project Settings pin Metrics that are shown on the Timeline as default.
• Toggle 'Show only Pinned Metrics' on and off to switch between views.

Introducing Dark Mode​

You request, we deliver. Dark Mode is now available for all Memfault users. Whether you prefer a darker interface for its sleek look or its practicality, this feature is designed to enhance your Memfault experience.

• Switch between Dark and Light mode, or use your System Settings under the profile dropdown in the top right corner.

Get Notified When Devices In Your Fleet Go Offline​

Our new Device Offline Alert triggers notifications when a monitored Device hasn't communicated with the Memfault platform for a specified time period. You can configure the alert to send a message via email, to a Slack channel, or configure webhooks to use wherever else you need to be alerted. Device Offline Alerts are assessed every 5 minutes and can be tailored with start and end delays to manage noise and avoid premature alerts due to brief connectivity losses. Read the docs for more details on how to setup and configure Device Offline Alerts in Memfault.

Processing Log History Now Available For 60 Days​

We extended our Processing Log retention period from 7 to 60 days. Memfault's Processing Log provides a chronological view of events and data essential for diagnosing SDK integration issues and tracking data uploads. You can filter on date range, Device serial, software version, log type, and level to quickly locate relevant entries. You can also access detailed metadata on a log, and focus on specific transactions, aiding in a streamlined diagnostic investigation. Read the docs for more detail on how to best use the Processing Log for troubleshooting Device behavior and SDK integrations in Memfault.