Skip to main content

13 posts tagged with "Edge Site"

Release notes for the Foxglove Edge Site edge controller and Helm chart.

View All Tags

Edge Site v0.1.1

Edge Site​

This release stops trusting compromised eMudhra certificate authorities.

Security
  • The edge controller no longer trusts certificates issued by compromised eMudhra certificate authorities.

Docs: About, Install, Upgrade | Debian Packages: amd64, arm64 | Binary Files: amd64, arm64

Edge Site v0.1.0

Edge Site​

This release replaces the edge controller with a reimplementation that runs from a Debian package, a statically linked Linux executable, a Docker image, or the edge-site Helm chart.

Sites upgrading from Helm chart 0.0.32 or earlier must follow Upgrade from chart 0.0.x to keep using their existing catalog.

New & Improved
  • The edge controller is available as a Debian package with a systemd service, a statically linked Linux executable, and a Docker image, for AMD64 and ARM64. See Installation.
  • Added the recordings_indexed_bytes, recordings_imported_bytes, recordings_deletion_retained, recordings_retained_pending_upload, and recordings_retained_pending_upload_bytes Prometheus metrics. See Available metrics.
Changed
  • The edge-site Helm chart stores the catalog at /data/index/controller.db. To keep an existing catalog, set DATABASE_CONNECTION_STRING as described in Upgrade from chart 0.0.x.
  • POST /v1/recordings requires projectId, validates deviceName, and rejects absolute paths and paths containing ... See Recordings API.
  • Retention deletes expired local recordings, while keeping recordings queued for import or waiting to upload. See Retention.
  • The recordings API accepts connections once the edge controller has connected to Foxglove.
  • In WATCH_AUTO_IMPORT_PATTERN, * matches across directory separators.
  • Azure uploads need STORAGE_AZURE_STORAGE_ACCOUNT_NAME, or a bucket name of the form <account>/<container>. See Configure cloud credentials.
Deprecated
  • Using S3-compatible object storage as the Edge Site's local recording storage (recordingStorage.provider: s3_compatible) isn't supported. Uploads to self-hosted Primary Sites and BYOS buckets remain supported.
  • GET /v1/recordings isn't available.
  • GARBAGE_COLLECTION_MAX_WORKERS, SLOW_QUERY_LOG_MIN_DURATION, SLOW_QUERY_LOG_PARAMETERS, DISABLE_DATABASE_STATISTICS_REPORTING, DISABLE_SERVER, and RECORDING_STORAGE_BUCKET_NAME are no longer read.
  • The imports_gigabytes and recording_upload_ms Prometheus metrics are no longer exposed.

Docs: About, Install, Upgrade | Debian Packages: amd64, arm64 | Binary Files: amd64, arm64

Edge Site v0.0.32

This release adds additional customization options.

Feature
  • Feature: add support for extraVolumes, extraVolumeMounts, initContainers and custom image names

Docs: About | Install | Upgrade

Edge Site v0.0.29

This release contains a fix for handling of some invalid MCAP files.

Fixes
  • 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.

Docs: About | Install | Upgrade

Edge Site v0.0.26

This release contains minor improvements.

New & Improved
  • Added the ability for Edge Sites to index MCAP channels written with schema ID 0 (no schema).

Docs: About | Install | Upgrade

Edge Site v0.0.25

This release contains minor improvements and fixes.

New & Improved
  • Validation was added to POST /v1/recordings to return an error status if the deviceName does not match our existing API's validation criteria
Fixes
  • Fixed an issue where garbage collection was not working for Edge Sites with a retention period configured and the site token configured via FOXGLOVE_SITE_TOKEN

Docs: About | Install | Upgrade

Edge Site v0.0.24

This release contains some minor fixes.

Fixes
  • Fixed a bug where new recordings might trigger an internal conflict when they have the same topics as previous recordings

Docs: About | Install | Upgrade