Health Monitoring App v2.1.x Release Notes

Review latency troubleshooting, security updates, and upgrade requirements for Health Monitoring App v2.1.x.

The following are the release notes for Health Monitoring App versions 2.1.x.

v2.1.0

Release Date

Release date: 20 November 2026

What's New

Health Monitoring App v2.1.0 adds per-file and per-injection latency troubleshooting for Tetra File-Log Agents (FLA) and Tetra Empower Agents. You can identify where a file or injection spent time, from its change timestamp through to Intermediate Data Schema (IDS) file registration.

The Operational Insights dashboard remains available for platform usage metrics. This release does not change its dashboard workflows.

Prerequisites

Health Monitoring App v2.1.0 requires the following:

For customer-hosted environments, the Databricks integration and data-app DNS and TLS configuration must be in place. See Health Monitoring App prerequisites.

New Functionality

Per-File and Per-Injection Latency Troubleshooting

Previously, the dashboard's aggregate latency metrics did not provide a complete latency breakdown for a single file. The following views now help you identify the stages contributing to ingestion delays:

  • File Latency Summary, File Latency Journey Average Duration by Stage, and File Latency Detail on the FLA tab
  • Injection Latency Summary, Injection Latency Journey, and Injection Latency Detail on the Empower tab

The summary tables show file paths, RAW and IDS file IDs, and latency measurements in seconds for Agent scanning, Agent generation, total Agent time, RAW-to-IDS processing, and end-to-end ingestion. The Empower summary also shows the project path.

The journey charts show seven ingestion stages, including upload, RAW registration, pipeline queue wait, pipeline execution, and IDS registration. The detail tables show each stage's start time, end time, and duration.

Selecting a RAW file ID or its associated IDS file ID resolves to the same source file's journey. With one source file selected, the journey chart shows that file's available stage durations. With several source files selected on the FLA tab, it shows the mean of the available durations for each stage. Without a file selection, it averages the files matching the other filters.

For instructions, see Health Monitoring App User Guide (v2.1.x).

Enhancements

Search and Select File IDs

The FLA tab's File Id filter now supports searching and selecting multiple RAW or IDS file IDs. Selecting both IDs for the same source file does not duplicate its journey. File Latency Detail includes fileid on each stage row to distinguish the selected source files.

The filter applies to the three FLA latency views and File Status. In File Status, either a RAW or an associated IDS file ID resolves to the corresponding RAW file. It does not narrow the other FLA charts.

The Empower tab adds a searchable, single-select File Id filter for its three injection latency views. Select either a RAW or an associated IDS file ID for the same injection journey.

Bug Fixes

  • Routine SQL statements and their bound parameter values no longer appear in INFO-level application logs. This reduces the risk of sensitive database values appearing in application logs.

Limitations

  • Latency values depend on the corresponding Agent and platform events. Missing events leave timestamps or durations unavailable; an unavailable value does not mean that a stage completed instantly.
  • The FLA latency views can include files that the Agent scanned but did not upload. These files show unavailable values for upload and later stages.
  • A failed or pending conversion can have no IDS file ID or RAW-to-IDS latency. The remaining stages are shown when their events are available.
  • Pipeline timing and status use the earliest available workflow for the file's trace that succeeded, failed, or was canceled. Reprocessed files can show an earlier run's timing and status, not the latest run. These views are not a complete pipeline-run history.
  • Any duration that combines Agent and platform timestamps can be negative because of clock differences. In the journey detail tables, stage_clock identifies stages that use both clocks as mixed.
  • The File Latency Summary, Injection Latency Summary, File Latency Detail, and Injection Latency Detail tables each return at most 1,000 rows. Narrow the filters when troubleshooting an individual file.
  • The existing Health Monitoring dashboard does not backfill metrics when it is activated. Some charts may remain empty until enough event data is available.

For filter behavior and troubleshooting, see the v2.1.x user guide.

Deprecated Features

There are no new deprecated features in this release. The existing Health Monitoring App v1.1.0 and Earlier Deprecation Notice still applies.

Known and Possible Issues

📘

NOTE

No new known issues were introduced in this release. The known issues listed below were also present in previous versions.

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

  • Downgrading from Health Monitoring App v1.1.0 to v1.0.0 may display the Operational Insights dashboard in the Health Monitoring view. Contact TetraScience before downgrading.
  • When upgrading from v1.0.0 to v1.1.0, selecting Change Version may temporarily display a 404 page until the installation dialog appears. The error disappears after installation and the dashboards load.
  • After activation, the app may return a 500 internal server error while establishing a user database. Log out of the TDP, close the browser, reopen it, and sign in again.
  • A graph may fail to render after selecting Enter fullscreen. Return to the dashboard and enter fullscreen again.
  • Opening the app for the first time may display Workgroup Not Found. See Rotate organization-level SQL credentials. Rotating these credentials invalidates the previous credentials, so coordinate with your administrator before doing so.

Security

SQLAlchemy logging is set to WARNING to suppress routine SQL statements and bound parameters. This change does not guarantee that every warning or error message is free of sensitive information.

Upgrade Considerations

To upgrade, follow Upgrade the Health Monitoring App and select v2.1.0 in the VERSION dropdown.

Before upgrading, confirm that your environment runs TDP v4.5.0 or later.

Related Resources


Did this page help you?