Version 4.0.1

Release Date: 26th December, 2025

New Features and Enhancements

Kubernetes and OpenShift Observability

• Install Pulse on OpenShift Cluster: The capability to install Pulse on an OpenShift cluster is now generally available (GA). For details, see Install Pulse on Kubernetes (Kubernetes-Based).

• Support for Spark on OpenShift: Pulse Observability: Introduced Pulse observability support for Spark on OpenShift, enabling visibility into Spark workloads. Pulse integrates with running Spark pods to collect metrics and logs, processes telemetry through the Pulse Agent, and stores it in backend databases. These insights are exposed through Pulse services and dashboards for monitoring, alerting, and analysis.

  • For details on the architecture, see Spark on OpenShift: Pulse Observability.

• Introduced Kubernetes Metrics Dashboards: Introduced built-in dashboards in Pulse to monitor Kubernetes cluster and namespace CPU and memory metrics directly from the Pulse UI. For details, see Monitor Kubernetes Clusters.

• Support for Standalone Trino on Kubernetes: Pulse now provides observability for standalone Trino deployments running on Kubernetes. This includes real-time monitoring of query performance, cluster health, and resource utilization. Pulse also captures Trino query events and JVM metrics to enable proactive troubleshooting and operational insights.

  • For details about the configuration, see Configure Pulse to Monitor Standalone Trino Deployed on Kubernetes.
  • For details about the User Guide, see Trino.

• Support for Standalone PulseNode & Pulseaxn Deployment: This release introduces support for standalone installation of PulseNode and Pulseaxn on non-Kubernetes VMs, along with Pulseaxn deployment on Kubernetes clusters in the same namespace as Pulse. For details, see Install Agents on Standalone VM.

Deployment and Platform

• Podman Runtime Support: Pulse can now be deployed using Podman as the container runtime. This enables deployments in environments where Docker is not allowed, and Podman is the organizational standard for containers. For details on the configuration, see Initialise and Configure Pulse CLI.
• Support for Knox in Pulse: Pulse now supports Apache Knox integration. Knox acts as an authentication gateway between Hadoop services and the external environment. With this enhancement, Pulse can now authenticate through Knox to securely connect to Hadoop services. For details about the configuration, see Configure Pulse to Connect to Hadoop Services via Knox with LDAP.
• Support for Token-based authentication in Pulse: Pulse now supports token-based authentication for connecting to Ambari and Cloudera. Basic authentication was already supported. This enhancement allows Pulse to connect securely to Ambari or Cloudera using either existing user credentials or a generated token, improving both security and integration flexibility. For details about the configuration, see Configure the Acceldata Core Components.
• License-Based Node Quota Enforcement: Pulse now enforces customer node quotas based on the licensed node count across all clusters. If usage exceeds the licensed limit, a warning is shown during a 15-day grace period. After the grace period, affected clusters are disabled until the license is updated. For more information, see Node Quota Enforcement.
• Support for Azul OpenJDK 17: Pulse now supports Azul OpenJDK 17, ensuring full compatibility across Pulse containers and agents. This enables seamless deployment in environments standardized on Java 17, including enterprise Hadoop platforms.
• Admin Console Notifications Configuration: The Admin Console now includes a dedicated Alerts and Actions Notifications configuration interface that allows administrators to configure and send notifications through multiple channels. This enhancement enables centralized management of notification settings and delivery targets. For more information, see Manage Notifications.

Observability and Insights

• Kafka Consumer Dashboard Enhancements: The Kafka consumer group dashboard for standalone Kafka 3 clusters has been enhanced to provide richer visibility into consumer groups. The updated views improve how consumer groups, topics, and consumption state are displayed, making it easier to troubleshoot lag and consumption patterns. For details, see Consumer Topics.
• Enhanced Incident Search with Advanced Filtering: The Search field on the Incidents page now supports advanced filtering capabilities. Users can filter incidents by Alert Name using multiple operators, including equals (=), IN, regex match (=~), and NOT IN. This enhancement enables more precise incident searches and faster troubleshooting workflows.
• Dashplots Naming Rule Enforcement: When creating a dashboard in Dashplot Studio, the dashboard name must contain only letters, numbers, and hyphens. Spaces and special characters are not supported.
• Introduced Dashboard Reporting Options: Pulse now supports advanced reporting options, including sending chart images, sending data in Excel sheets, or both. For configuration details, see Advanced Options.
• Introduced the ImpalaTablesWithMissingStatistics dashboard: This dashboard identifies tables with missing statistics based on HDFS directory ownership on the Dashplot Studio page.

Resolved Issues

• Fixed an issue where files with a replication factor of 0 (due to erasure coding) were incorrectly treated as directories. Files and directories are now correctly identified.
• Fixed an issue where the HDFS File Explorer in Pulse showed incomplete directory structures and missing paths (such as /prod and /prod/archive) even after successful automated and manual fsimage loads.”
• Fixed an issue where Pulse failed to display database data due to connection errors caused by URL misconfiguration.
• Fixed an issue where links in ‘Succeeded Action’ email alerts redirected to port 4000 instead of the correct SSL-enabled load balancer URL.