Foxglove 2.13.0
ποΈ Direct file accessβ
If you have a self-managed Primary Site, you can now get the path of MCAP files in your data lake using the /lake-files
endpoint. This allows you to directly access your Foxglove data for things like custom analysis, machine learning, post-processing, resimulation, and more.
You can query the /lake-files
endpoint for the data associated with a device using deviceId
or deviceName
and a time range. Alternatively you can request the indexed data associated with a recording using recordingId
or recordingKey
. In either case, you'll get a list of MCAP files in object storage that you can directly access using your prefered AWS, GCP, or Azure SDKs and tools.
Self-managed Primary Sites and the /lake-files
endpoint require an Enterprise plan.
New & Improved
- The Problem sidebar now automatically opens with a 'Retry' button when a network issue can be resolved by reloading the data source
Performance
- Minor performance improvements to message handling
- Plot panel performance improvements
Fixes
- Fixed a bug that was causing extension loading to hang
- MCAP metadata for recordings imported via Edge Sites or Foxglove Agent is now indexed and available through the API
- Fixed minor issues with message path autocomplete
- Fixed an issue with cleaning up background workers for Plot panels
- Fixed a bug preventing data from user scripts to load after switching layouts in some cases
- Fixed bug with reading optional fields in OMG IDL messages
- Fixed a bug causing two instances of a panel to be added to a layout on double-click
- Fixed an occasional bug with the Plot panel where the scatter plot displayed incorrectly until the user interacted with the plot
- Fixed a bug with plot downsampling causing out of memory errors for large datasets at certain zoom levels
API
- For self-managed Primary Sites, the
/recording-attachments
API now returnslakePath
, the path of the object in the data lake
Downloads: Linux: deb amd64 arm64, snap amd64 | Windows: Universal | Mac: Universal