Skip to main content

Home

v4.8.1.0 Release notes

Software version

Release date: August 10, 2023

See 4.8.1.0 for download information.

Software upgrade support

Upgrade is not supported in this release.

For fresh installations, see Installing Unravel.

Certified platforms

The following platforms are tested and certified in this release:

Cloud platforms

  • Google Cloud Platform (GCP) - BigQuery

Review your platform's compatibility matrix before you install Unravel.

Updates to Unravel's configuration properties

New features

  • Installation

    • More secure ways to get BigQuery data for Unravel monitoring

      You can set up Unravel, using any of the following secure authentication methods, to receive data from BigQuery for Unravel monitoring.

      • VM-based authentication: This method is used when Unravel is hosted on a VM in the GCP compute engine service.

        In this method, a service account is created in the project in which Unravel is hosted. Instead of downloading the service account key, the service account is attached to the Unravel VM.

      • Single key-based authentication: This method is ideal for cases where Unravel is installed on a VM that is hosted outside GCP on any other cloud or on-prem environment.

        Only one service account key representing all the projects is integrated with Unravel, which is downloaded and used. This method lets you use a single key instead of multiple keys to help in key rotation.

    • Terraform is separately provided independent of the installer

      Terraform is an open-source software for infrastructure provisioning. The Terraform creates resources on the GCP account and facilitates the smooth integration of Unravel with your cloud platform. Terraform is now provided in both ways; bundled with the installer as well as separated from the installer for independent handling of resource creation and state management.

      The external Terraform is available for all the authentication (VM authentication, Single key authentication, and Multiple key authentication) methods available for integrating BigQuery projects.

      Refer to BigQuery installation in Installing Unravel.

    • Support for integration of administration projects

      The integration of administrator projects is now supported. These projects help in retrieving reservations data required for Cost 360 observability dashboards.

    • Support for integrating billing data

      You can now export and integrate BigQuery billing data for Unravel querying.

  • Capture complete cost

    Unravel can now capture the complete cost concerning BigQuery, which includes computing, storage, and services. For computing, Unravel can capture the cost for both on-demand and capacity-based (Standard, Enterprise, Enterprise Plus) pricing plans.

  • Cost optimization

    • Get 360 degree view into BigQuery spends

      You can get a detailed view of your BigQuery spending in terms of services, projects, users, and jobs.

  • Insights

    • TopK insights with the highest potential for cost optimization

      The TopK insights are provided in the following categories for cost optimization.

      • Reservations

      • Jobs

      • Scheduled Queries

      • Projects

  • Alerting

    • Set alerting based on OpenSearch to detect violations

      You can set alerting based on OpenSearch to detect violations and get alerts in your specified notification channels.

  • Jobs

    • Side-by-side job comparison

      You can compare any two jobs side-by-side to easily identify the difference between the two jobs.

Improvements and enhancements

  • App Store

    • Appstore works seamlessly for both MySQL and PostgreSQL DB over SSL/TLS. (APP-674)

  • Jobs

    • The sink query in GCP is modified to get only the jobs which has job ID. (BQ-361)

  • Properties setting

    Changed the default behavior of manager config property set command to not override by default, and instead add an explicit --force' option to override. (INSTALL-3230)

Bug fixes

None

Unsupported

  • Unravel does not support Billing for on-prem platforms.

  • Monitoring the expiration of the SSL Certificates and Kerberos principals in Unravel multi-cluster deployments.

The following features are not supported for MapR:

  • Impala applications

  • Kerberos

  • The following features are not supported on the Data page:

    • Forecasting

    • Small Files Report

    • File Reports

  • The following reports are not supported on MapR:

    • File Reports

    • Small Files Report

    • Capacity Forecasting

    • Cloud Migration reports

  • AutoAction is not supported for Impala applications.

  • Billing

  • Insights Overview

  • Migration planning is not supported for the following regions for Azure Data Lake:

    • Germany Central (Sovereign)

    • Germany Northeast (Sovereign)

  • Forecasting and Migration: In a multi-cluster environment, you can configure only a single cluster at a time. Hence, reports are generated only for that single cluster.

  • Unravel does not support multi-cluster management of combined on-prem and cloud clusters.

  • Automatic FSImage processing is not supported for multi-cluster environments.

  • Unravel does not support apps belonging to the same pipeline in a multi-cluster environment but is sourced from different clusters. A pipeline can only contain apps that belong to the same cluster.

  • On the Table Details page under the Applications tab, inaccurate data is displayed for a table. This issue occurs if a table is deleted and recreated multiple times and applications executed to access the table before the next cycle of the table worker. (PG-156)

  • If tables are created with the same name and are accessed, deleted, and re-created, and if those tables are re-accessed, then their query and app count do not match. (DATAPAGE-502)

  • The query to fetch tableDailyKPIs is getting timed out in case of a huge table partition (27 million). (DATAPAGE-740)

  • For Hive metastore 3.1.0 or earlier versions, the creation time of partitions is not captured if a partition is created dynamically.  Therefore, the Last Day KPI for the partition section is not shown in Unravel. (DATAPAGE-473)

  • On the Data page, size data is missing for certain tables in databases, although the partition size is correctly displayed in the Partition Detail section. (DATAPAGE-695)

  • The Insights Overview tab uses UTC as the timezone, while other pages use local time. Hence, the date and time shown on the Insights Overview tab and the other pages after redirection can differ. (UIX-4176)

  • Kerberos can only be disabled manually from the unravel.yamlfile.

     kerberos:
          enabled: False
  • WorkloadFit report

    • A large number of tags can cause the Workload Fit report to fail. (PG-265, CUSTOMER-2084)

    • WorkloadFit report > Heatmap: The job count has data, but Vcore and memory are empty. (MIG-262)

  • Inconsistency between the regions displayed on the Unravel user interface and the ones included in AWS EMR. (MIG-280, MIG-281)

  • The Cloud Mapping Per Host migration report fails for some regions. (MIG-303)

  • Cluster discovery

    • The On-prem Cluster Identity might show an incorrect Spark version on CDH. The report may incorrectly show Spark 1 when Spark 2 is installed on the CDH cluster. (REPORT-1702)

  • Queue analysis:

    • The log file name (unravel_us_1.log) displayed in the error message is incorrect. The correct name of the log file is unravel_sensor.log. (REPORT-1663)

  • Cloud Mapping Per Host report scheduled in v4.6.1.x does not work in v4.7.1.0. Users must organize a new report. (REPORT-1886)

  • When using PostgreSQL, the percentage (%) sign is duplicated and displayed in the Workload Fit report > Map to single cluster tab. (MIG-42)

  • SQL events generator generates SQL Like clause event if the query contains a like pattern even in the literals. (TEZLLAP-349)

  • After upgrading to v4.7.1.0, Notebooks do not work. You can configure them separately. (REPORT-1895)

  • After upgrading from v4.6.x to v4.7.1.0, the Tez application details page does not initially show DAG data. The DAG data is visible only after you refresh the page. (ASP-1126)

  • In the App summary page for Impala, the Query> Operator view is visible after scrolling down. (UIX-3536).

  • When you click the hive query, which was executed as part of the Hive on Spark application, a blank page is shown. (UIX-6037)

  • On the Clusters > Resources page, in the Group By drop-down list, the Application Type, User, and Queue options are duplicated for the YARN/IMPALA resource job type. The issue occurs if identical user-defined tags are used. (UIX-5898)

  • Jobs are falsely labeled as a Tez App for Oozie Sqoop and Shell actions. (PLATFORM-2403)

Support

For support issues, contact Unravel Support.