Mezmo Agent 3.9 Now Available!

Mezmo is pleased to announce the GA release of the Mezmo Ingestion Agent 3.9. You can download this version of the Agent from the Mezmo GitHub repo, where you can also find more detailed documentation.

Major updates in this version of the Agent include:
​
​Added an option to delay Kubernetes logs until pod metadata is available

The agent uses the Kubernetes api to enrich log line information with appropriate pod data. If the api is non-responsive, by default the agent will send the log lines without the associated pod labels. This feature adds a new configuration parameter MZ_METADATA_RETRY_DELAY to wait for a specified period of time for the label data to become available.

Replaced debouncer with a custom solution to simplify and reduce file events

On heavily loaded systems, where the Agent is monitoring files with multiple symlink copies, if the Agent has queued data from one of the copies and the symlinks are deleted out of sequence, then the Agent could send multiple copies of the same line. The change modifies the order in which events are processed, which ensures no duplicates are sent. The deduplication also reduces memory required and improves overall throughput in these scenarios.

Correctly handle truncation during create events

There’s a still existing edge case when log rotation re-uses inodes, new files might be treated as truncations. Ensuring the truncation is caught during a file create instead of a create write can help alleviate potential of log drop in this case. If you’re using logrotation, make sure the `create` option is enabled.

Additional updates include:

• Added support for Windows event logs
• Fixed an issue where Agent would crash if Windows log directory wasn’t present
• Added support for Mac (Experimental)
• Optimized memory allocations in file system monitoring
• Reduced memory overhead of Kubernetes watchers
• Pinned RocksDB version to 8.3.2
• Added rate limiting to logging in hotpath components
• Changed journald dockerfile to not enumerate Linux devices
• Environment configuration is now printed on startup
• Added an Icon for the Windows executable
• Kubernetes metadata watcher now configured with appropriate options
• Fixed offsets not tracking correctly across cache clearing restarts when lookback is disabled
• Added log to notify when Agent exits gracefully