Agent v1.27.0

Gigamon AMX Demo Source, Microsoft DNS Demo Source, Minimum Agent Version Support, and OTTL Array Type Handling.

  2 minute read  

January 13, 2025

New Features

  • Gigamon AMX Demo Source: The demo source node can now emit Gigamon sample data.
  • Microsoft DNS Demo Source: The demo source node can now emit Microsoft DNS sample data.
  • Minimum Agent Version Support: Configuration validation now supports a minimum agent version for nodes. This enhancement ensures that pipeline components are compatible with the agent version in use.
  • OTTL Array Type Handling: Enhanced OTTL to accommodate other array types and improved error identification by including processor names in error messages. Users can now map Edge Delta data to their schema tables more seamlessly.

Improvements

  • Azure Blob Storage Refactor: Updated Azure Blob and Local Storage implementations. The refactor also includes the addition of a logger as a parameter for the S3 implementation.
  • GOMEMLIMIT Enhancements: Introduced default GOMEMLIMIT values for all components managed under Helm, with added support for automatic GOMEMLIMIT configuration if not predefined.
  • GCL Resource Label Handling: Changed GCL destination configuration to manage resource labels via whole field mapping instead of individual entry mapping.
  • OpenTSDB Processor Logging Reduction: Reduced verbosity in OpenTSDB logging.
  • Kubernetes Traffic Metrics: K8s traffic metrics now include domain information for enhanced data granularity.
  • Kubernetes and OpenTelemetry Libraries: Upgraded Kubernetes, OpenTelemetry, and other auxiliary libraries to their latest versions.

Bug Fixes

  • Node I/O Stats Discrepancy Resolution: Addressed issues causing disparities in pipeline views related to node I/O statistics.
  • Mutating Processors Item Sizes Compliance: Updated processors to better respect item size constraints.
  • OTTL Transform Node Casting: Eliminated unnecessary casting to BaseItem in the OTTL Transform node, which resolves a panic issue encountered after the Destination Transform.
  • Kubernetes Metrics Node Configuration: By default, kubelet, cadvisor, and node_exporter metrics are now excluded in the k8s_metrics node. Users can re-enable them if needed by updating the exclusion parameters.