The following are the release notes for the beta release versions of the Tetra File-Log Agent versions 4.6.x. The Tetra File-Log Agent automatically detects the changes of file-based outputs generated from instruments and then uploads them to the Tetra Data Platform (TDP).

📘

NOTE

New beta release functionalities in v4.6.x are documented in the following release notes only. Otherwise, customers should reference the Tetra File-Log Agent v4.5.x documentation for installation and setup instructions. v4.6.x documentation will be published along with the general availability release.

Upgrades

To upgrade to a new beta release Agent version, customers must contact their customer account leader. For more information about upgrading Agents, see Upgrade an Agent.

Installation

For installation instructions, see Tetra File-Log Agent Installation Guide (v4.5.x).

To configure and use the Agent after it's installed, see the Tetra File-Log Agent User Manual (v4.5.x).

v4.6.0 Beta Release

Release date: 18 November 2025

What's New

TetraScience has released its first beta release version of Tetra File-Log Agent v4.6.0. To help reduce data duplication and storage costs for customers, this release provides a new Index Only Data Ingestion functionality that automatically indexes data in the Tetra Data Platform (TDP) without needing to upload it to the platform.

New Functionality

New Functionality includes features not previously available in the Tetra File-Log Agent.

Index Only Data Ingestion (Beta)

To help reduce data duplication and storage costs for customers, a new beta release Index Only Data Ingestion functionality provides customers the option to automatically catalog and index files in the TDP without uploading their full content. This feature can be useful for compliance tracking, data discovery, and cost management purposes—or any time customers need to know what files exist, but don't need immediate access to their contents.

When Index Only Data Ingestion is enabled on a file scan path, the Agent uploads a 0-byte placeholder file with an .index suffix (for example, file.txt becomes file.txt.index) instead of the full file content, while preserving important file information, such as labels and Amazon Simple Storage Service (Amazon S3) metadata.

Information Preserved

The following information is attached to indexed files as labels and Amazon S3 metadata:

• file_index_only: true: Marks the file for downstream pipeline identification
• file_name: Original filename without the .index suffix
• file_size_bytes: Actual file size
• os_created_user: File owner (when Fetch OS File/Folder Owner is enabled)
• host_name and host_ip: System context
• x-amz-meta-ts_file_index_only: 1: Immutable marker in Amazon S3 metadata

The path to the source file location is preserved in the TDP file path (without the .index suffix). When customers search for indexed files in the TDP, they can use the file path, host_name, and host_ip labels to locate the source file on the original system.

Example If the original file is located at C:\Data\experiment_results.csv on host LAB-PC-01 with IP 10.0.1.50, the indexed file in the TDP will contain the following information:

• TDP file path: C:\Data\experiment_results.csv.index
• file_name label: experiment_results.csv
• host_name label: LAB-PC-01
• host_ip label: 10.0.1.50

To retrieve the actual file, the user would go to the source location C:\Data\experiment_results.csv on host LAB-PC-01 (IP: 10.0.1.50).

Configuration

To use the new Index Only Data Ingestion functionality, customers can configure the Index Only Data Ingestion option for each path from the Watcher Path Editor in the local Tetra File-Log Agent Management Console. This option is only available when File Watch Mode is set to File.

Important Considerations

• Index Only Data Ingestion is not compatible with the following settings and features:
  • Folder Mode: Index Only Data Ingestion is only available when File Watch Mode is set to File. The option is hidden when Folder mode is selected.
  • Archive: Index Only Data Ingestion cannot be used with Archive settings. When Index Only Data Ingestion is enabled, the Archive Settings section is hidden in the Agent Management Console.
  • Delete: Index Only Data Ingestion cannot be used with Delete settings.
  • Stream Upload: Index Only Data Ingestion cannot be used with Stream Upload settings. The Stream Upload section is hidden when Index Only Data Ingestion is enabled.
• When you enable Index Only Data Ingestion on a path, any existing Archive, Delete, and Stream Upload settings are automatically cleared.
• Modifying a path's Index Only Data Ingestion setting from enabled to disabled is not recommended, since it may lead to unexpected ingestion behavior.
• If a path's Index Only Data Ingestion setting is changed from enabled to disabled, existing files won't automatically re-upload with their full content. Files must be manually rescanned or modified to trigger re-upload with full content.
• Downstream systems like pipelines, data apps, and saved searches may not handle 0-byte placeholder files gracefully. Updating existing paths to use Index Only Data Ingestion could affect downstream consumers who expect actual file content.

Enhancements

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

• There are no enhancements in this release.

Bug Fixes

There are no bug fixes in this release.

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 and possible issues for the Tetra File-Log Agent v4.6.0 beta release:

• Files uploading when a path is updated with an Archive configuration can sometimes get stuck in the Pending Archive status. A fix for this issue is in development and testing and is scheduled for a future release.
• For a path configured in File mode, if a glob pattern doesn't start with “\*\*/” and the path has system directories that the Agent can't access, the path's scan process terminates. Check the logs and look for agents.filelog.scanStarted.v1, agents.filelog.scanError.v1, and agents.filelog.scanCompleted.v1 for a path to identify if the scan was terminated or completed.
• In the Service Settings section, if an existing path is highlighted and the DEL (Delete) keyboard key is pressed, the row is removed from the grid. However, this action doesn't remove the path from the Agent. A fix for this issue is in development and testing and is planned for a future release. To delete a path from the Agent in the Agent Management Console, customers must use the Delete option in the Action column of the grid for each path, and then choose Save.
• If a configured path becomes inaccessible by the Agent due to access permissions or network connection lost, the path may still display a green check next to the inaccessible path in the Agent Management Console.

Upgrade Considerations

When upgrading to the Tetra File-Log Agent v4.6.0 beta release, keep in mind the following:

• For installations that use a Tetra Data Hub, activating the Archive feature requires the following configurations in the Agent's Advanced Settings so that the Agent can authenticate with the TDP and retrieve verified checksums:
  • For TDP API URL Override, enter the TDP API endpoint for your deployment (for example, platform.tetrascience.com).
  • For Org Slug, enter the org slug for the organization that the agent is in.
  • For Authorization, enter the JSON Web Token that you're using.
• If a Tetra Data Hub acts as a proxy for the Agent and the Archive feature is activated, the TDP API endpoint must be accessible from either the Agent host or from the Data Hub Host if using a Tetra L7 Proxy Connector. For more information, see Tetra Agent Allow List Endpoints.

Other Release Notes

To view other Tetra Agent and Tetra Data release notes, see Tetra Agent and Tetra Data Release Notes.

To view other TDP release notes, see Tetra Data Platform (TDP) Release Notes.