The following are the Tetra File-Log Agent release notes for versions 4.5.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).

Upgrades

To upgrade the Tetra File-Log Agent, 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.5.0

Release date: 14 October 2025

What's New

TetraScience has released its next version of the Tetra File-Log Agent, version 4.5.0. This release focuses on making it faster for scientists to access data for analysis by reducing the Agent's scan detection latency for paths with multi-level directories and increasing data acquisition throughput into the Tetra Data Platform (TDP) by 41% from the previous Agent version. These updates reduce the need for customers to manage multiple Agents for high-throughput workloads, too. This release also adds more flexibility to how customers can customize file ingestion patterns, making it easier to specify exactly what files should be uploaded and excluded.

New Functionality

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

Stream Data Directly to Amazon S3

When the S3 Direct Upload option is activated, the Agent can now optionally stream file uploads directly to Amazon Simple Storage Service (Amazon S3) without requiring the file(s) to be stored locally in the Group User temporary folder before they're uploaded to the TDP. When coupled with the other performance improvements included in this release, direct streaming to Amazon S3 helps increase the Agent's data acquisition throughput by 34%.

To set up direct streaming to Amazon S3, customers can configure a new Stream Uploads option for each path from the Watcher Path Editor in the Agent Management Console. Direct streaming to Amazon S3 is disabled by default.

For more information, see Configure the Tetra File-Log Agent FileWatcher Service in the Tetra File-Log Agent Installation Guide (v4.5.x).

New Command to Process Events When Files Change

A new File Changed command (TetraScience.Agent.FileLog.FileChangedCommand) processes file change events for both file and folder modes from any external deployed system (for example, network attached storage). Because each external deployed system is customer specific, a custom solution that uses this command is required to send file change events to the Agent. Creating these custom setups can be beneficial for troubleshooting unusually long scan latency in external systems.

For more information, see Tetra File-Log Agent File Changed Command.

Enhancements

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

Performance Improvements

To help increase the Agent's data acquisition throughput, this release introduces the following performance improvements:

• Detection of new or changed files for a configured path in both File and Folder modes has been redesigned to remove third-party libraries and .NET file abstractions in network protocols that were previously used by the Agent. This update reduces average scan latency for configured paths with multi-level directory structures from hundreds of seconds to tens of seconds.
• Small files (less than or equal to 100 MB) are now uploaded more efficiently to Amazon S3 by using fewer REST API calls.

Extended Glob Patterns

The Agent now supports the following extended glob patterns, which provide customers more ways specify the files that the Agent should upload to the TDP:

• ?(pattern-list) matches zero or one occurrence of the given patterns
• *(pattern-list) matches zero or more occurrences of the given patterns
• +(pattern-list) matches one or more occurrences of the given patterns
• @(pattern-list) matches one of the given patterns
• !(pattern-list) matches anything except one of the given patterns
• #{repetition} and #{min repetition, max repetition}

For more information, see Common Glob Patterns.

Other Enhancements

• The frequency for scanning a configured path (Scan Interval (seconds)) can now be configured separately from the Change Interval (seconds) setting, which is the duration that a file must remain unchanged before it can be uploaded. Scan Interval (seconds) is only configurable through the Agent the Management Console currently, but will be available through remote TDP Agent Configuration in a future release.
• Agents with S3 Direct Upload activated now use a SHA1 checksum to ensure data integrity on file uploads (instead of the SHA256 checksum used previously).
• Label validation for specifying labels through the Watcher Path Editor in the Agent Management Console is now consistent with the TDP.
• Events reported in the Health Monitoring Dashboard now include additional timestamps for last modified date for Folder mode, the full path as configured in the Agent, and changed detected state (event or scan).
• Customers can now configure a Max File Size when downloading files from the TDP with the TetraScience.Agent.FileLog.DropFile.CopyFile command.

Bug Fixes

The following bugs are now fixed:

• If access permissions change for a directory that was previously accessible by the Agent, the Agent now fails the scan.
• Paths with leading spaces are now scannable.
• When the Agent's SymlinkBehavior is set to Ignore, the Agent previously ignored directory symlinks, but now will still scan and include the files within a symlinked directory.

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.5.0 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 Tetra File-Log Agent v4.5.0, 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.