Changelog

Latest Version: 6.2.2

Release History

6.2.2

Fixes

• Definitions - device defaults are now applied to all device definitions within a single YAML file
• Discovery: persistence - discovered object inventory is now properly applied when the collector is restarted
• SNMP Error Handling - fixed a possible panic that can occur when objects are being pruned from the discovered inventory

Updates

• Discovery - device discovery now performs a bulk walk, rather than a simple walk, when SNMP v2c and v3 is configured, reducing the number of polls necessary to complete the discovery process

6.2.1

New Features

• Kafka Output: support for ECS - An option has been added to output records in Elastic Common Schema (ECS).

6.2.0

This is the initial generally available (GA) release of the new ElastiFlow Unified SNMP Collector.

New Features

• API: apply-definitions and rediscover-device - endpoints have been added to trigger the collector to re-read all definitions and take necessary actions (e.g. add/remove a device), and the rediscovery of a devices SNMP object instances.
• Discovery: persistence - Discovered device SNMP object instances can now be persisted to disk. This allow the collector to be restarted without rediscovering all devices.
• Elasticsearch and Opensearch Output: auto-generated index templates - Index templates for Elasticsearch and OpenSearch are now auto-generated from SNMP object definitions.
• Kafka Output: optional flattened field names - An option has been added to use flattened, rather than nested, field names in the JSON records produced to Kafka.
• API (formerly Metrics) Server - Added support for basic authentication to secure the API's HTTP Server.

Deprecations

• Default value of EF_OUTPUT_ELASTICSEARCH_TIMESTAMP_SOURCE - Beginning with ElastiFlow 6.3.0 the Elasticsearch output's default value for EF_OUTPUT_ELASTICSEARCH_TIMESTAMP_SOURCE will be changed to collect. This will allow the collector to handle a wider variety of situations without additional configuration. If you wish to continue to use the current default setting of end, you should ensure that it is specifically set in your configuration prior to the release and deployment of 6.3.0.
• Default value of EF_OUTPUT_ELASTICSEARCH_INDEX_PERIOD - Beginning with ElastiFlow 6.3.0 the Elasticsearch output's default value for EF_OUTPUT_ELASTICSEARCH_INDEX_PERIOD will be changed to rollover. This will enable the use of Index Lifecycle Management (ILM) to manage retention of ElastiFlow indices. If you wish to continue to use the current default setting of daily, you should ensure that it is specifically set in your configuration prior to the release and deployment of 6.3.0.
• Default value of EF_OUTPUT_OPENSEARCH_TIMESTAMP_SOURCE - Beginning with ElastiFlow 6.3.0 the OpenSearch output's default value for EF_OUTPUT_OPENSEARCH_TIMESTAMP_SOURCE will be changed to collect. This will allow the collector to handle a wider variety of situations without additional configuration. If you wish to continue to use the current default setting of end, you should ensure that it is specifically set in your configuration prior to the release and deployment of 6.3.0.
• Kafka output default values - Performance testing has shown that the current default values can be modified for improved throughput. Beginning with ElastiFlow 6.3.0 the default values of various Kafka output configuration options will be changed as in the table below. If you wish to continue to use the current default settings, you should ensure that it is specifically set in your configuration prior to the release and deployment of 6.3.0.

Option	6.2.x and earlier	planned for 6.3.0
EF_OUTPUT_KAFKA_PRODUCER_COMPRESSION	0 (none)	3 (LZ4)
EF_OUTPUT_KAFKA_PRODUCER_FLUSH_FREQUENCY	500ms	1000ms
EF_OUTPUT_KAFKA_FLAT_RECORD_ENABLE	false	true

Updates

• Logging - logs have been improved for improved structure and readability.
• Elasticsearch Output - Bulk index errors returned from Elasticsearch/OpenSearch are now logged.
• Kafka Output - producer pool has been improved for increased performance.