Fixed Issues

Fixed UI bugs and made improvements to dashboard import/export workflows.

Fixed a bug where UI showed blank integration pages.

Fixed bugs on infrastructure UI that caused some information cells to be blank.

Fixed a bug on Logs dashboard in Control Plane.

Fixed an issue that prevented users from downloading metrics data for analytics.

Resolved a bug where queries only worked with pushdown operators but failed with non-pushdown operators.

Fixed an issue where saved queries were always stored in the general folder. Users can now select a target folder.

Enabled the hydration service to support string search and regex queries.

Fixed an issue that prevented logs data from being downloaded. Data can now be exported as CSV, JSON, or TXT.

Fixed the diff operator to correctly output the difference between the current and previous row.

Added support for stacked columns as a chart type in log panels.

Fixed an issue where silencing an alert suppressed the entire alert rule instead of a single alert instance.

Completed migration of the required Kubernetes dashboard from Sumo Logic to Kloudfuse, with save and cat operator support.

Fixed an issue where logical operators in queries were case sensitive.

Fixed editor behavior so that pressing Enter runs a query, while Shift+Enter moves to the next line.

Fixed issues with cat and save operators for lookup tables and improved sorting support in FuseQL.

Fixed an issue in scheduled views implementation.

Improved performance in Logs hydration.

Fixed issues in RBAC implementation which prevented users from being deleted and users’ roles from being downgraded to viewer.

We fixed support for zstd compressed logs payload from Datadog. This improves log ingestion reliability.

We fixed incorrect span.kind classification for Datadog spans to improve trace accuracy.

We fixed handling of moving attributes to hc attributes within span attributes to preserve metadata correctly.

We fixed incorrect Helm validation for Azure deep store configurations to ensure successful deployments.

We fixed incorrect handling of label filters in the hydration service for accurate data hydration.

We fixed an issue where recording rules failed to evaluate after the upgrade to 3.4.0. This is a critical fix, and it requires an upgrade to this release. See Release Notes for 3.4.0.p1.

We fixed a UI issue in RBAC that appears when switching between User and Service Account views.

We fixed an issue where the filter was not active during events list download.

We fixed an issue were users could not search the event message body.

We fixed an issue where users could not create dashboard panels with FuseQL Advanced Search.

We fixed an issue with Edit and Duplicate functionality in RUM Alerts.

We fixed an issue with editing contacts.

We fixed an issue with Viewer role write permissions when creating alerts.

We fixed an issue where the alert did not render correctly on the Alert Detail Page.

We fixed an issue where users were unable to add variables to Dashboards.

We fixed an issue where users with a Viewer role were able to see all users and polices.

We fixed an issue where users were unable to mute an alert.

We fixed an issue where users were unable to create an alert in the Kloudfuse Alert UI.

We fixed an issue of incorrect type in the logs table, and moved the logs schedule view support table to the component.

We fixed an issue where using mixed-case email addresses in the IdP authentication through SSO and SAML resulted in duplicate users.

We fixed an issue where effective policies were not shown correctly for the selected user.

We added an option to specify the group name prefix for mapping roles. See Configure Role Group Prefix.

We fixed an issue where high cardinality attribute filters from span detail did not carry over the selected field.

We fixed an issue where the traces chart did not appear, and the UI erroneously reported a "data is not found" error.

We fixed an issue where the Metric Explorer does not load the chart.

We fixed an issue where the trace id did not propogate fully, so that traces visible in Grafana did not appear in the Kloudfuse UI.

We fixed an issue where a log rate control parameter,skipCpRules was not applied correctly.

We fixed an issue where PromQL queries were malformed because of missing encoding.

We fixed an issue where Admin users were getting a "Restricted Access" message after logging in.

We fixed an issue where Audit Logging could not be enabled because of incorrect workflow to SAML Authentication configuration.

We fixed an issue where the RUM logs ingestion failed due to incorrect encoding value.

We fixed an issue where users where not able to create dashboards through in-product Kubernetes integration.

We fixed an issue where the Pinot Controller returned a false negative status, 500, when generating a response.

We fixed an issue where Kloudfuse was reporting drops in OTel Protocol logs as allowed.

We fixed an issue where the AZ-service was exiting the restore workflow early.

We fixed and issue where the logs filter for dashboard panels was not performing.

We fixed an issue where the FuseQL arithmetic formulas were not evaluating correctly.

We fixed a display issue, so that the UI shows the Table view when the query contains an aggregation, and the Logs view if it does not.

We fixed an issue where the workflow displayed a pre-populated scheduled view.

We fixed an issue where users did not have an affordance for adding logs from a FuseQL query result to a dashboard.

We fixed an issue where the user could delete classes; this is no longer possible.

We fixed an issue where users were unable to edit an existing alert created through FuseQL.

We fixed an issue where viewers where not able to create alerts in folders where they had admin access.

We fixed an issue where errors displayed on the graph, but did not appear in the Error tab.

When we introduced splitting of longer time range metric queries into smaller separate queries, it created performance issues. We fixed these issues by tuning the splitting logic.

We fixed an issue where a PromQL queries were not parsing properly during streaming due to a whitespace delimiter.

We fixed an issue where the matching function did not work for the regex non-match.

We fixed regex search anchoring for PromQL queries.

We fixed an issue where a prefix was not removed for OpenTelemetry logs ingestion.

We optimized the performance of alerts.

We fixed an issue where the user SSO ID was used as their email.

When we introduced splitting of longer time range metric queries into smaller separate queries, it introduced performance issues. We fixed the issue by tuning the splitting logic.

We fixed an issue where the table columns for APM were not fully configurable.

We fixed an issue where the Prometheus Engine was disabled by default, and therefore could not support @ modifiers.

We fixed an issue where analysis with K-lens did not work properly.

We fixed an issue where the Analyze button appeared on the interface for all alert types.

We fixed an issue that prevented the display of data for Apdex metrics services.

We fixed an issue where the Create Event Alerts page had no title.

We fixed an issues where the log level and security indicator represented in the UI did not match the original log record.

We fixed an issue where incorrect color labels (legend) appeared on the RUM charts.

We fixed an issue where the User ID and User Email was visible on the RUM Details RUM page, but did not appear in the RUM Table view.

We fixed an issue where the Create Event Alerts page had no title.

We fixed an issue where it was not possible to create the first Alert Suppress Schedule in the set. It addresses a Known issue: Unable to Create the First Suppress Schedule.

We fixed an issue where it was not possible to edit the query of an existing log alert.

We fixed an issue where the ingester was dropping AWS metrics that were sourced outside the curated AWS namespaces.

We fixed an issue where the Pod Restart alert fired incorrectly because the alert rule was evaluating partial results.

We fixed an issue where the Create Alert option was disabled when the analytics query result set is empty.

We fixed an issue where sorting was unavailable before an aggregation operator.

We fixed an issue where regex search was incorrectly enabled for uuid columns like view.id, session.id, action.id, resource.id, error.id, and longtask.id.

We fixed an issue where the Forecast operation results did not display correctly after switching to Advanced Search, in both Timeseries View and when creating a Log Forecast alert.

We fixed an issue where changing the time picker in FuseQL Advanced Search mode did not re-run the query.

We fixed an issue where changing variables in the Kloudfuse Overview dashboard did not work properly, or propagate to the subordinate charts.

We fixed an issue where a Suppress Schedule for Alerts could not be deleted if it was assigned to a Contact Point.

We fixed an issue where APM/ASM service filtering was affected by RBAC policies for Metrics.

We fixed an issue where the Edit Contact Point interface was titled Create Contact Point.

We fixed an issue where dedup and backshift operators used in the KfuseQL Advanced Search break subsequent access to view columns, facets, and labels extracted by the query.

We fixed an issue where the number datatype had inadequate support when querying scheduled views.

We fixed an issue with correctly saving and displaying advanced function alerts using FuseQL, namely incorrect display, incorrect grouping, improper calculation and display of an internal operator.

We fixed issues where the date did not show properly on the chart or in the tooltip, and the start of the forecast did not update to current time properly.

We previously did not support filtering for generation 1 metrics for AWS/FSx Namespace for ONTAP filesystems.

We previously did not support querying scheduled views from the Table or List interface.

We fixed an issue where dynamic variables were not picked up correctly.

We fixed and issue where numeric columns added during regular search did not display when switching to Advanced Search.

We added instructions for using scripts to manage alerts and dashboards. See Manage Alerts.

We fixed an issue with the deployment marker on Service Traces.

We fixed an issue when the specified time range for dashboards did not apply to internal panels, and they instead showed only the latest time range.

We fixed an issue where a facet or label that you add to a column disappears when switching between regular and advanced logs search.

We fixed an issue where the left filter panel on both Logs and APM interfaces did not load the value on the initial click; it now refreshes automatically.

We fixed an issue when a selected filter for active services did not apply when showing all (active and inactive) services.

We fixed an issue where labels were not working properly on the Kloudfuse UI. We upgraded our UI to support the interval data type.