Skip to main content

46 posts tagged with "Primary Site"

Release notes for self-hosted Foxglove Primary Site Helm chart.

View All Tags

Primary Site v0.0.85

This primary site release adds JSON output to the query service root URL handler. This is useful to check that the site ingress is configured correctly.

Added
  • Added JSON output to the query server root handler.

Docs: About | Install | Upgrade

Primary Site v0.0.84

This primary site release adds an optional feature that will send health metrics to Foxglove.

These metrics are all Prometheus metrics generated by the Foxglove services in the chart (query-server, inbox-listener or indexer, and site-controller) as well as the new kube-state-metrics component that monitors the pods and deployments in your cluster's Foxglove namespace.

This feature can be disabled by setting the following in your values.yaml:

globals:
  publishSiteMetrics: false
Added

  • Added new deployment for kube-state-metrics. This will monitor the Foxglove namespace and produce metrics about the health of pods.

    It can be disabled by updating your values.yaml file:

    kubeStateMetrics:
      enabled: false

  • The site-controller will now gather health metrics from the Foxglove namespace and send them to Foxglove. These metrics will be used to monitor the health of your deployment.

    It can be disabled by updating your values.yaml file:

    globals:
      publishSiteMetrics: false

Docs: About | Install | Upgrade

Primary Site v0.0.77

This primary site release changes the name of the stream-server to query-server. It contains breaking changes, read the changelog to see if manual intervention is required for your deployment.

Changed
  • The stream-server container image has been renamed to query-server. New images will no longer be published under the stream-server name.
  • the streamService values namespace has been renamed to queryService. Values defined in the legacy streamService namespace will continue to work. streamService values override default values defined in the queryService namespace before templating.
  • breaking The stream-service application and deployment are removed, and replaced with an query-service deployment. Any auto-scaler which uses the stream-service deployment name as a scaleTargetRef will no longer have any effect. To upgrade safely:
    • Add a new autoscaler that targets the query-service deployment.
    • Upgrade and test your deployment.
    • Schedule a date in the future to remove the old autoscaler. After removing the old autoscaler, this chart should not be rolled back past this version.
  • The stream Kubernetes service is duplicated with the name query. New deployments should set up ingress to the query service, but the stream service remains for backwards compatibility.
  • breaking The service account name has changed from stream-service to query-service. If you are using OIDC on AWS you must update your namespace_service_accounts field to support the name change.

Docs: About | Install | Upgrade

Primary Site v0.0.67

Added
  • inbox-listener: added MAX_FINALIZATION_WORKER_COUNT environment variable to configure the maximum worker count used to write files to the lake. This defaults to 40 and can be reduced to mitigate rate-limiting API errors from the lake bucket. When set to 0, the inbox listener uses one worker per topic in the input file.

Docs: About | Install | Upgrade