Visit our new documentation site! This documentation page is no longer updated.

Release Note 20140819

Table of Contents

Features & Improvements

This is a summary of the new features and improvements introduced in this release:

Console: Improved Treasure Agent Monitoring Service Scalability

Improved the Treasure Agent Monitoring Service (TAMS) to scale better even with a very high number of td-agent instances reporting metrics.

The changes included:

  1. Automatically removing instances inactive for more than 1 week
  2. Remove instances inactive for more than 1 hour on request (Delete Old Instances Button button)
  3. Only update and display monitoring data for instances in Up Label state
  4. Paginate the list of instances

Console: Improved Treasure Agent Monitoring Service Scalability

Console: Timezone Selection in File Uploader

Added the ability to select the timezone for the time column. This is important when the time column format does not express the timezone in any way, such as Unix time format (e.g. 1408588817 which corresponds to 2014-08-21 02:40:17 UTC) or as a date-time without timezone (e.g. 2014-08-21 02:40:17).

Previously all values in the time column where interpreted in UTC / GMT timezone.

Console: Timezone Selection in File Uploader

SDKs: Released the JavaScript SDK v1.1.1

This release is an incremental update of the JavaScript SDK which addresses an issue with the ‘td_referrer’ method found to not return the referrer of a request correctly.

Bug Fix

This is the only important Bug Fix made in this release:

Console: Schedule’s Execution With Large Delay Values

  • [Problem]
    Schedules that are setup with a delay greater than their periodicity stopped executing.
    Updating the Schedule’s ‘Last Job ID’ field causes the reevaluation of the next run time based on the schedule’s periodicity. This causes the schedules to never execute again beginning with the first ‘Last Job ID’ update because the delay requirement is lax. Only a handful of schedules were affected; schedules whose delay was equal or below the schedule’s periodicity are not affected instead.
    Changed the Schedule model to reevaluate the next run time only if any attribute but ‘Last Job ID’ was updated.

Last modified: Dec 12 2015 06:04:40 UTC

If this article is incorrect or outdated, or omits critical information, let us know. For all other issues, access our support channels.