Skip to main content

StackState v4.6.0 released!

StackState Tech Support
Updated

We are proud to present the latest release of StackState!

The StackState v4.6 release brings powerful new capabilities:
  • Important improvements in topology visualization to accelerate troubleshooting.
  • Support for OpenTelemetry traces, specifically for serverless AWS Lambda applications built with Node.js. This new low-latency data requires no integration, and will immediately enrich your topology with additional relationships and telemetry.
  • Expanded Autonomous Anomaly Detection capabilities to automatically analyze the golden signals of throughput, latency and error rate. Automatic health checks can then run on this data and alert you as soon as anomalies are found. This will help you to get to the root cause of incidents more quickly and proactively prevent problems before they occur.
 
Details of the included improvements and bug fixes can be found below. To learn more about the new features included in this release, checkout the webinar introducing StackState v4.6.0 (youtube.com).

Improvements

  • Topology synchronization progress counters have been moved from individual synchronizations to the `stackstate.log` file for Linux-based distributions. Errors for topology mapping and templates remain in the synchronization-specific logs. STAC-15529
  • The MinIO chart now allows the registry to be configured separately from the repository. Also, the chart will now use any globally configured pull secrets to fetch Docker images. STAC-15180
  • The component context menu now displays the preview of the three top priority metrics. STAC-15076
  • `PodDisruptionBudget` and `PodSecurityPolicy` now use the updated apiVersion (policy/v1) for newer Kubernetes versions. STAC-14968
  • The MinIO Helm chart has been updated to specify both a requests and limits for the memory resource. STAC-14771
  • All PodDisruptionBudget(s) can be configured through the Helm Values. STAC-14770
  • In the StackState Helm chart, the Ingress path can now be configured through the value `ingress.path`. STAC-14769
  • All pods in the StackState Helm charts can now be configured to use a pullSecret to pull protected images. STAC-14767
  • Non-propagating unhealthy components are marked as problem root causes. STAC-13618

 

Bug fixes

  • Increased performance of network connections correlation by better data scheduling and by adjusting CPU limits in the Helm chart (default from 0.6 to 2). STAC-15822
  • Fixed an issue that caused custom Kafka producer configuration to be disregarded by the correlator and receiver. STAC-15795
  • Clears the following CVEs STAC-15733:
    • CVE-2022-23852
    • CVE-2022-23990
  • The limit of problems visible in the StackState UI has been increased to 999. STAC-15688
  • Remediation for CVE-2022-23307 by removing Log4J dependencies from StackGraph. STAC-15655
  • Fixed an issue that caused several pods to be stuck in Pending mode after an API key update. STAC-15525
  • Fixed bug when major part of Kubernetes topology is missing when a big element is reported (such as big ConfigMap). STAC-15458
  • Fixed receiver out of memory issue appearing under load preventing processes from appearing on topology. STAC-15431
  • Fixed an issue that caused the StackState UI to crash occasionally due to a misconfiguration of the Prometheus nginx exporter. STAC-15167
  • Fixed an issue that caused component properties to not display correctly when a component is merged from two of the same synchronization sources. STAC-15147
  • Fixed an issue that caused StackState to stop receiving health synchronization data after Kafka has rebalanced partitions to consumers. STAC-14676
  • Fixed an issue that caused the anomaly event chart to not display full metric data. STAC-14630
  • The `backup-stackgraph` Kubernetes CronJob now correctly checks whether the StackGraph export exists before copying it. STAC-14532
  • Fixed error on the Traces Perspective stemming from server and browser clocks not being synchronized. STAC-12832

 

Support

StackState offers technical support for the three most recent major releases. The release of StackState v4.6 marks the End of Life (EOL) of the StackState 4.3 version range. Consequently, this version of the product will no longer be supported and we encourage customers still running the 4.3 version range to upgrade to a more recent release.

 

Upgrading to v4.6.0

Before upgrading to StackState v4.6.0, please review the upgrade instructions provided in the documentation.

Download

You can download the release at the StackState Software Distribution site.

Helm charts

The StackState v4.6.0 helm charts are available via our helm repository, helm.stackstate.io

 

Comments

0 comments

Article is closed for comments.

Powered by Zendesk