We are proud to present the latest release of StackState!
This release is yet another significant step towards completing our vision toward fully autonomous operations using the 4T Data Model.
We've improved StackState in the following areas:
- Show configuration changes for faster root cause analysis. STAC-12441
- Alert on anomalies detected by the Autonomous Anomaly Detector. STAC-11798
- Drill down on Problems for faster investigation. STAC-10481
- Introduced check functions that alert on anomalies detected by the Autonomous Anomaly Detector. Previous anomaly detection functions and baseline streams and functions are deprecated and will be removed in StackState 4.4. STAC-12256
- The Autonomous Anomaly Detector (AAD) is now enabled by default in the Kubernetes distribution. STAC-12024
- It is now possible to configure whether ClusterRoles and ClusterRoleBindings need to be installed by the StackState Helm chart using the flag `cluster-role.enabled`. STAC-11749
- StackState HDFS pods now run without privileges in Kubernetes. STAC-11741
- Added support for interacting with external systems using self-signed certificates. STAC-11738
- The field specifying the role to use for Keycloak authentication (default field name: `roles`) is now configurable using the `groupsField` configuration parameter. STAC-11609
- StackState now supports API tokens for authentication of the StackState CLI. This allows the StackState CLI to work with Keycloak or OIDC as an authentication provider. STAC-11608
- The CLI will now issue a deprecation warning when not using the new API token based authentication. See https://l.stackstate.com/cli-up-auth-deprecated. STAC-12567
- Added support for backup and restore procedure for self-hosted Kubernetes setup. STAC-11548
- It is now possible to use component actions when time-traveling. STAC-11462
- Introduced auto-grouping to automatically choose the correct grouping level for views. STAC-11396
- Authentication settings are now directly configurable on the Helm chart. STAC-11237
- Added permission `manage-event-handlers` to protect creation of event handlers. STAC-11172
- Allow filtering Events by source. STAC-10644
- Allow filtering Events by category. STAC-10643
- Events of type Anomaly now display a metric chart including the anomaly in the Event Details pane. STAC-10031
- Added a permission to protect usage of `Http` and `Graph` script APIs in Analytics. STAC-9834
- Added ability to filter on labels in the Component Details pane. STAC-11824
- Added ability to search and filter components in the Topology perspective List mode. STAC-11413
- Added ability to export component list as a CSV file in the Topology perspective List mode. STAC-3593
- Added ability to search telemetry streams on the Component Details pane. STAC-3194
- Fixed issue that prevented view event handlers from being updated. STAC-12296
- Fixed issue that prevented proxy settings from being picked up in asynchronous event handlers. STAC-12097
- Fixed memory consumption issue in slicer pod that caused intermittent out of memory errors. Any custom memory settings for the slicer pod can be removed. STAC-11841
- Fixed issue that caused the Slack event handler to fail when sending a notification of a view health state change event. STAC-11831
- Fixed issue that caused the StackState helm chart to fail with custom image registries. STAC-11717
- Fixed issue that prevented copy_images.sh script from working with containers without a docker.io prefix. STAC-11697
- Fixed issue that caused the old and new state to disappear for certain health state changes in the Event Perspective. STAC-11691
- Fixed issue that prevented exports produced by the CLI on Windows from being imported. STAC-11096
- Fixed issue that caused incorrect anomalies to be detected on CloudWatch metrics by introducing two new aggregation methods: COUNT_NO_ZEROS and SUM_NO_ZEROS. Aggregation methods COUNT and SUM keep the existing behavior of filling gaps in metrics with zeroes, with a configurable delay. STAC-11079
StackState offers technical support for the three most recent major releases. The release of StackState 4.3 marks the End of Life (EOL) of the StackState 4.0 version range. Consequently, this version of the product will no longer be supported and we encourage customers still running the 4.0 version range to upgrade to a more recent release.
Upgrading to 4.3.0
Before upgrading to StackState 4.3.0, please review the upgrade instructions provided in the documentation.
You can download the release at the StackState Software Distribution site.
The StackState 4.3.0 helm charts are available via our helm repository, helm.stackstate.io
Article is closed for comments.