JD Strong
JD Strong
Fleet 4.42.0 is live. Check out the full changelog or continue reading to get the highlights. For upgrade instructions, see our upgrade guide in the Fleet docs.
Query results are now cached on a per-host basis. Cached query results are designed to significantly aid Fleet users, particularly when investigating the state of a currently offline host. By caching query results, administrators can access and review the latest recorded state of any individual host, even when that host is not actively connected to a network.
This addition benefits IT and security teams, facilitating a more efficient troubleshooting process. Custom data relevant to each host can be added to the Host details page, streamlining diagnostic and issue resolution tasks. This enhancement aligns with Fleet's commitment to providing user-friendly and efficient tools, enhancing the overall device management and security capabilities within the Fleet environment.
Fleet continues to enhance query management: the ability to gauge the performance impact of running queries. Live queries will now gather and display statistics on their impact on system resources. These statistics will be accessible for saved queries located in the Queries tab.
After executing a live query, users can conveniently view the updated performance impact statistics in the Queries pages. This allows for a more informed assessment of how each query affects system resources. Additionally, the resilience of query statistics has been improved; they will no longer reset after a host or agent reboot. This ensures continuity and reliability in monitoring performance over time.
In line with maintaining a streamlined and relevant dataset, statistics for a query will be automatically deleted when the query itself is deleted. The impact of each query will be categorized and displayed in a new "Performance impact" column, with labels such as "Minimal," "Considerable," and "Excessive," offering a clear, at-a-glance understanding of each query's system load. This feature aligns with Fleet's values of openness and objectivity, as it provides transparent and quantifiable data on the impact of queries, empowering users to make more informed decisions.
Fleet continues to focus on enhancing user management capabilities. This new feature will allow administrators to look up devices associated with specific users through the email addresses used with their Identity Provider (IdP), currently supported exclusively on macOS hosts. This addition will benefit organizations utilizing identity management systems, as it streamlines linking users to their respective devices, thereby improving administrative efficiency and device management accuracy. This feature aligns with Fleet's commitment to providing user-friendly, efficient tools for IT and security teams.
Stay tuned for upcoming updates and more inclusive features as we continue to enhance Fleet's versatility across different operating systems. To glimpse what's in store, please follow our progress on this story in the current sprint: Human-endpoint mapping expansion.
As part of Fleet's commitment to enhancing user experience and administrative efficiency, the organization of software listings in the UI is being updated to streamline the Software page for IT administrators. Admins can now view a consolidated list of software installed across their fleet, organized by software title. This organization method will enable admins to easily identify the most popular software used in their environment, irrespective of the versions installed. As part of this initial release, popular applications will be represented with icons. What applications would you like icons for? Comment on this issue, or contribute by making pull requests for icons of your favorite apps, fostering a collaborative development environment.
Administrators now have the capability to target hosts directly by their serial numbers through the fleetctl
command line. When using fleetctl run-script
and fleetctl mdm run-command
commands, identifying and managing specific hosts within the Fleet environment is streamlined. By enabling direct targeting of hosts by serial number, Fleet enhances the precision and efficiency of administrative tasks, aligning with its commitment to providing powerful and user-friendly device management tools. This addition is particularly useful for scenarios where quick identification and action on individual hosts are required, improving overall workflow efficiency.
Endpoint operations:
fleet/device/{token}/ping
endpoint for agent token checks.GET /hosts/{id}/health
endpoint for host health data.--host-identifier
option to fleetd for enrolling with a random identifier.software_version_id
and software_title_id
.software_version_id
and software_title_id
in various endpoints.Vulnerability management:
GET software/versions
and GET software/versions/{id}
endpoints for software version management.GET software
and GET software/{id}
endpoints.Device management (MDM):
FLEET_DEV_MDM_ENABLED
feature flag for Windows MDM.fleetctl
to configure Windows MDM profiles for teams and "no team".POST /mdm/profiles
, DELETE /mdm/profiles/{id}
, GET /mdm/profiles/{id}
, GET /mdm/profiles
, GET /mdm/profiles/summary
.fleetctl run-script
and fleetctl mdm run-command
.POST /api/v1/fleet/scripts/run/sync
timeout now returns error code 408 instead of 504.software
data ingestion and host_batteries
upsert.installed_from_dep
in mdm_enrolled
activity for DEP device re-enrollment.GET /hosts/{id}/health
endpoint reporting.overrides.platform
field to be set to null
.Visit our Upgrade guide in the Fleet docs for instructions on updating to Fleet 4.42.0.