Agent v0.1.101

May 6, 2024

The following changes been implemented in this agent release:

New Features

• The Mask node now includes a number of regex patterns out of the box for masking important fields such as email, bitcoin address, different types of credit card numbers etc.
• Metrics Generation for Log Threshold Monitors: Agents now generate metrics required for log threshold monitors. A hidden Log-to-Metric node fetches monitors from the backend and associates metrics with them. This node is also connected to the ed_metrics_output node type.

Improvements

• Health Signal Enhancements in Debug Output: The health node output can now be viewed in the debug output node, allowing users to visualize the health signals it produces. The base strategy for health status now registers a ’not ok’ status if there are more than 10 issues within a 10-minute window.

Bug Fixes

• Elastic Output Warning Suppression: An issue where the lastErr variable in the Elastic output node wasn’t being set properly has been addressed, ensuring that warnings are now logged if entries encounter issues during processing.
• Enhanced Isolation in Pipeline Testing: Changes have been made to pipeline testing to prevent the activation of components. During testing, Output nodes are substituted with Void nodes, ensuring that no real output operations are executed. This approach solidifies the testing environment’s isolation, ensuring that it remains unaffected by any output-side effects.
• Source Detector and Enrichment Tagging Fix: A bug concerning the incorrect tagging of log file names in source detector and enrichment in config v2 has been rectified, improving tagging accuracy in specific use cases.
• Corrected Outgoing Bytes and Lines Reporting: A previous bug that prevented successful reporting of outgoing bytes and lines, even when there were successes, has been fixed. This enhances the accuracy of transmission analytics.
• Panic Prevention During OTEL Patterns Emission: Adjustments have been made to check whether the compactor is running before proceeding with any data upload. This change prevents the Agent from panicking and attempting to write to a closed channel when stopping, thereby ensuring a smoother shutdown process.
• Concurrent Map Read/Write Issue Resolved: An agent panic caused by concurrent map read/write operations, especially relevant during output node and dependencies construction, has been addressed. This fix includes the enforcement of correct logic to determine if a link should copy the object considering both Incoming and Outgoing data configurations.
• Pusher Logging and Health Tracking: Improvements in Pusher logging have been applied, allowing more detailed error logging and better health status accuracy.