API ReferenceProduct Documentation
Product Documentation

Health Monitoring App v2.0.x Release Notes

The following are the Health Monitoring App release notes for versions 2.0.x. The app provides two comprehensive dashboards in the Tetra Data Platform (TDP) user interface to help customers gain an end-to-end understanding of data usage and downtime as well as platform usage:

v2.0.0

Release date: 24 April 2026

What's New

TetraScience has released Health Monitoring App version 2.0.0. This release update’s the app’s dataset queries to use the new Lakehouse-based tables that power the Health Monitoring App’s dashboards in Tetra Data Platform (TDP) v4.5.0 and later. There are no other new functionalities or enhancements in this release.

Upgrading to Health Monitoring App v2.0.0 or later is recommended after upgrading to TDP v4.5.0 or later for improved functionality and will be required starting in TDP v4.6.0. For upgrade instructions, see Upgrade the Health Monitoring App.

For more information, see the Health Monitoring App v1.1.0 and Earlier Deprecation Notice.

Prerequisites

Health Monitoring App v2.0.0 requires the following:

For Customer-Hosted TDP Environments Only

  • The TetraScience Databricks integration (which supports the Lakehouse). Contact your customer account leader to set this up.

New Functionality

New Functionality includes features not previously available in the Health Monitoring App.

  • There is no new functionality in this release.

Enhancements

Enhancements are modifications to existing functionality that improve performance or usability, but don't alter the function or intended use of the system.

  • The ORG__tss__system database tables that contain the information used for the dashboards in the Health Monitoring App have been migrated to new Lakehouse-based tables. There are no changes to the Health Monitoring App dashboards' functionality.

Migrating the ORG>__tss__system database tables to the Lakehouse architecture provides the following benefits:

  • Performance and cost efficiencies
  • An optimized data model for monitoring dashboards
  • The ability to evolve the schema for new features without breaking user-visible tables

Customers using the Health Monitor app versions earlier than 2.0.0 are encouraged to upgrade to version 2.0.0 or later after upgrading to TDP v4.5.0. Versions earlier than 2.0.0 will continue to work on TDP v4.5.0 but support will be removed in TDP v4.6.0. For more information, see the Health Monitoring App v1.1.0 and Earlier Deprecation Notice.

Bug Fixes

There are no bug fixes in this release.

Limitations

The following are known limitations of Health Monitoring App v2.2.0:

  • Metrics data for the Operational Insights dashboard is backfilled with data from July 2025 and later only when the app is activated. However, it can take several days for the data to backfill (one month of data takes about a day to populate). Until the data backfill completes, only the latest data captured from when the app is updated appears in the dashboard.
  • Metrics data for the Health Monitoring App dashboard isn't backfilled when the app is activated, so the available data spans one day in duration only when the new Health Monitoring dashboard first appears in customers' TDP environments.
  • If the available data spans one day in duration only (for example, when the new dashboard is first activated) then charts in the new Health Monitoring dashboard will appear empty. If customers hover their cursors over an empty chart, they will see a single data point, which is a summary statistic for that day. Once customers have two days of data available, then the charts and tables will populate as normal.
  • The File Ingestion Journey chart on the FLA tab won't show any file search indexing events or other downstream file events if those events occur outside of the Time range filter defined by customers. This behavior occurs because all File Ingestion Journey events are a subset of the original files that were scanned during the specified time range.
  • There is a maximum number of table rows available for each of the following troubleshooting metrics:
    • Last Agent Heartbeat: 100 row maximum
    • File Status: 1,000 row maximum
    • Workflow Status: 1,000 row maximum
    • Path Status (Latest Scan): 1,000 row maximum

Deprecated Features

There are no new deprecated features in this release. For more information about TDP deprecations, see Tetra Product Deprecation Notices.

Known and Possible Issues

The following are known issues for Health Monitoring App v2.0.0:

  • Downgrading from Health Monitoring App v1.1.0 to v1.0.0 may result in the Operational Insights dashboard being displayed in the Health Monitoring view instead of the Health Monitoring dashboard. TetraScience recommends not downgrading from v1.1.0 since v1.1.0 did not introduce changes to the Health Monitoring dashboard. If customers need to downgrade, they should contact TetraScience for assistance.
  • When customers upgrade to Health Monitoring App v1.1.0 from v1.0.0 and select Change Version, a 404 error page might display until the installation dialog appears. After the new app version is installed, the 404 page disappears and the app's dashboards load. A fix for this issue is in development and testing and is scheduled for a future Tetra Data Platform (TDP) release.
  • After being activated, the Health Monitoring App may return a 500 internal server error as it establishes a new user database. To resolve the issue, customers should log out of the TDP, close their web browser, and then reopen the browser and sign back in to the TDP.
  • After selecting Enter fullscreen on a graph, the graph can sometimes fail to render and an error appears. To resolve the issue, navigate back to the dashboard and re-enter the fullscreen view.
  • The app might also display a Workgroup Not Found error when opened for the first time. To resolve the issue, customers must rotate their organization-level SQL Credentials. Keep in mind, the new set of generated credentials will cause the previous set of credentials to stop working.

Security

The Health Monitoring App implements the following security measures:

  • All dashboard data is encrypted in transit using TLS 1.2+
  • Access to metrics is controlled through TDP's role-based access control system
  • Audit logging tracks all dashboard configuration changes
  • Alert configurations are encrypted at rest

Upgrade Considerations

To upgrade to Health Monitoring App v2.0.0 from earlier versions, TDP v4.5.0 or higher is required. For upgrade instructions, see Upgrade the Health Monitoring App.

When activating the Health Monitoring App, keep in mind the following:

  • After being activated, the app may return a 500 internal server error as it establishes a new user database. To resolve the issue, customers should log out of the TDP, close their web browser, and then reopen the browser and sign back in to the TDP.
  • The app might also display a Workgroup Not Found error when opened for the first time. To resolve the issue, customers must rotate their organization-level SQL Credentials. Keep in mind, the new set of generated credentials will cause the previous set of credentials to stop working.
  • The app can be deactivated at any time, if needed. (For customer-hosted deployments only) Activating the Health Monitoring App introduces additional data processing costs in the Data Lakehouse. To process integration events in near real time, the app creates its own silver Lakehouse Tables that are required for data cleaning and validation. These tables support the analytics displayed in the Health Monitoring App and are activated through a feature flag (enable_dam_silver_tables), which can be turned off at any time. For a cost estimate based on your specific needs, contact your customer account leader. (Updated on 14 November 2025)

For more information about the Health Monitoring App, see Health Monitoring App.

Updated 5 days ago