primary-site-0.0.51

Foxglove Primary Site

primary-site-0.0.50

• Change: a device name specified in foxglove MCAP metadata will now create the device if it does not yet exist

primary-site-0.0.49

• Added: If the LOG_REPEATED_IMPORT_FAILURES environment variable is set to true, the inbox listener will log an error-level message whenever it has to quarantine an input file after exhausting all retries. This can help primary site operators detect issues with their deployment.
• Changed: For primary sites using Azure storage buckets with hierarchical namespaces enabled, the garbage-collector service will log an info-level message when it attempts to delete a non-empty directory, but it will skip over it.
• Fixed: If the inbox listener attempts to process an MCAP file with an invalid file offset, it will quarantine the file immediately rather than retrying three times.

edge-site-0.0.29

Fixed: When the edge controller attempts to submit a recording that Foxglove cloud considers invalid, it will gracefully drop the recording instead of retrying forever.

primary-site-0.0.48

Changelog

• inbox-listener: for built-in autoscaling, add Helm chart values to tune pollingInterval, successJobsHistoryLimit and failedJobsHistoryLimit

primary-site-0.0.47

Changelog

• Feature: add support for built-in inbox-listener autoscaling, see documentation for details

primary-site-0.0.46

• Fixed: if the garbage collector cannot delete a temp file, it will log an error instead of aborting.
• Fixed: the request ID tag in inbox listener logs now matches the request ID in the foxglove API for pending imports.
• Fixed: various corrupt BAG and MCAP errors will now result in the file being quarantined immediately rather than retrying 3 times.

primary-site-0.0.45

Inbox listener

Fixed: the lake object store is used for MCAP metadata, supporting multi-provider configurations

edge-site-0.0.28

Edge controller

Fixed: Use correctly built multiarch images.

primary-site-0.0.44

Changed

• New lake file path format: the inbox listener now writes files into the lake bucket with object paths starting with v1. This should not affect behavior.