This topic describes the release notes for Log Service Logtail and provides links to the relevant references.

1.0.22

  • Fixed issues

    When network interruptions occur in global acceleration mode, Logtail stops submitting status data that is generated by the system to Log Service. This issue is fixed.

1.0.21

As a minor version of Logtail V1.0, Logtail V1.0.21 is the first one that is released in all regions. Logtail V1.0.21 includes all features of Logtail V0.16.64 and provides the following new features:

  • New features
    • Logtail can record the fine-grained information of checkpoints on local disks. To use this feature, set the exactly_once_concurrency parameter. For more information, see Logtail configurations.
    • The log time can be automatically set to the local time of the server. To use this feature, set the enable_log_time_auto_adjust startup parameter. For more information, see Set the startup parameters of Logtail.
    • The metadata information of a raw file can be added to the related log entry. To use this feature, set the enable_log_position_meta parameter. For more information, see Logtail configurations.
    • The current year or a specified year can be added to the log time. To use this feature, set the specified_year parameter. For more information, see Logtail configurations.

0.16.68

  • Fixed issues
    • When Logtail collects the standard output of containers, Log Service fails to parse the output data if the P (partial) tag of the output data cannot be identified. This issue is fixed.
    • If the service_skywalking_agent_v3 agent is installed on multiple application servers, the ID of a span and the ID of a parent span in the Links parameter are invalid. This issue is fixed.

0.16.64

  • Optimization

    The timeout period for requesting a container engine is increased from 3 seconds to 30 seconds. The DOCKER_CLIENT_REQUEST_TIMEOUT environment variable is added to specify the timeout period for requesting a container engine.

  • Fixed issues
    • The ID of a parent span in the service_skywalking plug-in is incorrect. This issue is fixed.
    • The code that is used to create a Logtail configuration file based on environment variables stops running if the related container engine has an exception. This issue is fixed.

0.16.62

Note If you are using Logtail V0.16.58 or Logtail V0.16.60, we recommend that you upgrade Logtail to V0.16.62.
  • Fixed issues

    Data fails to be sent due to out-of-order data. This issue is fixed.

0.16.60

  • New features

    Container data in the containerd environment can be collected.

0.16.56

  • Optimization

    The net_err_stat metric in service logs applies to sending errors that are caused only by network issues.

0.16.54

  • New features

    The net_err_stat metric is added to service logs. The number of sending errors that occur in the last 1, 5, or 15 minutes can be recorded.

0.16.52

If a large number of Logtail configuration files are created to collect container data (standard outputs or container files), we recommend that you upgrade Logtail to V0.16.52 or later. This helps you reduce the CPU overhead.

  • Optimization

    The CPU overhead during container data collection is optimized.

0.16.50

  • New features

    The service_telegraf plug-in can be installed at runtime. This feature is available only for Elastic Compute Service (ECS) users.

0.16.48

  • Optimization

    The service_telegraf plug-in is optimized. Multiple configuration files are supported on a single machine.

0.16.46

Note If the endpoint of Log Service is in the China (Hangzhou), China (Shanghai), or China (Beijing) region, you can upgrade Logtail to V0.16.46 or later. This prevents Logtail from switching endpoints when network jitter occurs.
  • Optimization

    The network types that are available for Logtail are strictly limited.

0.16.44

  • New features

    The service_telegraf plug-in is added to collect metric data.

0.16.42

  • New features

    Multi-level matching is supported when you use a blacklist to filter data. Example: /path/**/log.

  • Optimization

    The policy that is used to obtain local IP addresses is optimized. If a policy is invalid, the first IP address in the IP address list is obtained.

0.16.40

  • New features
    • The metric_system_v2 plug-in is added to collect the data of host statuses.
    • The max_docker_config_update_times parameter is added in the ALIYUN_LOGTAIL_MAX_DOCKER_CONFIG_UPDATE_TIMES environment variable. This parameter is applicable to scenarios in which you need to frequently create short-lived jobs in a Kubernetes environment.
  • Optimization

    The performance of CPU overhead is optimized for scenarios in which a large number of Logtail configuration files are created to collect container data.

  • Fixed issues

    The processor_split_log_string plug-in generates blank rows. This issue is fixed.

0.16.38

  • New features
    • A custom name for the time field is supported in full regex mode.
    • The KeepSourceIfParseError parameter is added in the processor_json, processor_regex, and processor_split_char plug-ins. If raw data fails to be parsed, the raw data can be retained. For more information, see Customize Logtail plug-ins to process data.

0.16.36

  • New features

    The processor_encrypt plug-in is added for encryption.

0.16.34

  • New features

    An HTTP probe is added for ‎Kubernetes health check.

  • Fixed issues
    • Core dumps are caused by libcurl in some environments. This issue is fixed.
    • When you install Logtail in CentOS 8, the GNU Libidn libary cannot be found. This issue is fixed.

0.16.32

  • New features

    The IgnoreFirstConnector parameter is added in the processor_json plug-in. For more information, see Expand JSON fields.

0.16.30

Notice If you run Logtail V0.16.30 for a long period of time, files may fail to be opened. We recommend that you update Logtail to the latest version.
  • New features

    Kubernetes clusters can be filtered by using whitelists or blacklists when you collect Docker standard outputs or files from the clusters.

  • Optimization

    The concurrency competition among Logstores in the same region due to poor network connections is optimized.

  • Fixed issues

    A checkpoint loss issue occurs due to logic errors when a file is opened. This issue is fixed.

0.16.28

  • New features

    A parameter is added to specify a tail size for the data that is collected for the first time.

  • Optimization

    The logic of container metadata collection is optimized to reduce the impact of faulty containers.

  • Fixed issues
    • The docker_stdout process causes memory leaks in complex environments. This issue is fixed.
    • Complete millisecond timestamps are not supported in JSON mode. This issue is fixed.

0.16.26

  • New features

    Containerd logs can be collected.

  • Fixed issues
    • The checkpoints of rotated files cannot be found. This issue is fixed.
    • If the /usr/local/ilogtail/user_log_config.json file does not exist, the local Logtail configuration file /etc/ilogtail/user_config.d is not loaded. This issue is fixed.

0.16.24

  • New features
    • The working_ip and working_hostname parameters can be set by using environment variables.
    • The force_quit_read_timeout parameter is added to specify the timeout period before you force Logtail to quit if events are blocked and fail to be read.
    • Tags such as path and topic can be passed to plug-ins.
    • The aggregator_shardhash plug-in is added and the shardhash parameter can be set in the plug-in.
    • The processor_gotime, processor_rename, processor_add_fields, processor_json, and processor_packjson plug-ins are added for data processing. For more information, see Customize Logtail plug-ins to process data.
    • LogtailInsight is updated. The progress viewing feature is added. This feature can be used only after you set the mark_offset_global_flag or customized_fields.mark_offset parameter.
  • Optimization
    • If the Journal plug-in runs for an extended period of time, the memory usage is high. This issue is fixed. The memory is released at the earliest opportunity.
    • The interval at which configurations are obtained when no on-premises configuration files exist is optimized.
  • Fixed issues
    • If multiple Logtail configuration files exist, duplicate data is collected. This issue is fixed.
    • Timestamps at the millisecond and microsecond levels do not support JSON int64. This issue is fixed.

0.16.23

  • New features
    • Millisecond and microsecond timestamps (%s) are supported.
    • Multiple on-premises Logtail configuration files can be loaded. File path: /etc/ilogtail/config.d/.
    • Multiple on-premises user configuration files can be loaded. File path: /etc/ilogtail/user_config.d/.
    • The processor_split_key_value and processor_strptime plug-ins are added for data processing. For more information, see Extract log fields by splitting key-value pairs and Extract log time.
    • The oas_connect_timeout and oas_request_timeout parameters are added to support the scenarios of slow networks.
  • Optimization

    The limits on the inputs parameter in hybrid configurations (file + plug-in) are removed.

0.16.21

  • New features
    • Custom static themes can be configured.
    • The blacklist filtering feature is supported.
    • The EnableEventMeta parameter is added in the service_canal plug-in to allow you to collect the header information for MySQL binary logs.
  • Optimization

    The stop mechanism of plug-ins is optimized.

  • Fixed issues

    GBK logs causes potential memory leaks. This issue is fixed.

0.16.18

  • New features
    • Docker events can be collected. For more information, see Collect Docker events.
    • Systemd-journald logs can be collected. For more information, see Collect systemd-journald logs.
    • The processor_pick_key and processor_drop_last_key plug-ins are added for data processing.
  • Optimization
    • The memory usage for container logs and plug-ins is optimized.
    • The performance of multi-line log collection is optimized for container standard outputs.

0.16.16

  • New features
    • The resources of Kubernetes audit logs can be automatically generated.
    • The startup parameters can be set by using environment variables. The startup parameters include CPU, memory, and sending concurrency.
    • The automatic upload of custom tags can be configured by using environment variables.
    • Configuration files can be automatically created in sidecar mode. For more information, see Use CRDs to collect Kubernetes container logs in Sidecar mode.
  • Optimization

    AliUid files can be automatically saved to local files.

  • Fixed issues
    • When Logtail collects files in containers, Logtail stops responding. This issue is fixed.
    • The IncludeLabel parameter of a configuration file that is created by using environment variables does not take effect in Kubernetes. This issue is fixed.

0.16.15

  • New features
    • The global transaction identifier (GTID) mode can be enabled for MySQL binary logs. If a MySQL server supports the GTID mode, this mode is automatically enabled.
    • Specified wildcards are supported for file names when you import historical data.
    • Indexes can be automatically generated for Kubernetes logs.
  • Optimization
    • The discardUnMatch parameter can be checked and logs that fail to be split into multiple lines are reported.
    • Logtail retries to collect data if an unknown sending error occurs. This prevents data loss in some cases, such as when a packet is modified during the sending process.

0.16.14

  • New features
    • The wildcard mode is supported when you import historical data.
    • The default_tail_limit_kb startup parameter is added to specify the size of data that is collected before a specified checkpoint when files are collected for the first time. Default value: 1024. Unit: KB.
    • The batch_send_seconds parameter is added to specify the interval at which data packets are sent during log collection.
    • The batch_send_bytes parameter is added to specify the size of the data packet to be sent during log collection.
  • Optimization

    The logs that are split by Docker Engine can be automatically merged when Logtail collects container standard outputs.

0.16.13

New features
  • Log collection can be configured by using environment variables.
  • The metadata of MySQL binary logs can be collected, such as the _filename_ and _offset_ fields.
  • The parameters in the installation script can be automatically selected in a virtual private cloud (VPC).
  • The global acceleration feature can be configured when Logtail is installed For more information, see Configure log collection acceleration for Logtail.

0.16.11

  • Optimization

    When you collect MySQL binary logs, you can collect the information of the _filename_ and _offset_ fields.

  • Fixed issues

    When you collect container standard outputs in multi-line mode, exceptions occur This issue is fixed.

0.16.10

  • Optimization

    The method that is used to collect container standard outputs is upgraded.

0.16.9

  • Fixed issues
    • The leak of socket fd occurs. This issue is fixed.
    • The limits on the update frequency of Logtail configuration files are added for container files.

0.16.8

  • New features
    • The input source Lumberjack protocol is added to collect data from Logstash and Beats. For more information, see Collect data from Beats and Logstash.
    • The inotify blacklist feature is added.
  • Fixed issues
    • The inconsistent parameters in earlier installation packages are revised.
    • When you install Logtail in some systems, the operating system version cannot be obtained. This issue is fixed.

0.16.6

  • New features
    • Host monitoring data can be collected.
    • Redis monitoring data can be collected.
    • Data definition language (DDL) statements in MySQL binary logs can be collected.
    • Container standard outputs and files can be filtered by using Docker environment variables.
  • Fixed issues
    • Data can be collected from a MySQL table that does not have a primary key.
    • An event loss issue occurs due to unstable subscription channels of container engines in container collection mode. This issue is fixed.

0.16.5

0.16.4

0.16.2

0.16.0

  • New features
    • MySQL binary logs, MySQL query results, and HTTP input sources are supported. For more information, see Customize Logtail plug-ins to process data.
    • Data analysis can be performed by combining regular expressions, anchors, delimiters, and filters.