Fixed Issues

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

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.

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 the user SSO ID was used as their email.

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.