[Bug 249108] sysutils/logstash7: Update to 6.9.1
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Sep 4 13:53:07 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249108
Bug ID: 249108
Summary: sysutils/logstash7: Update to 6.9.1
Product: Ports & Packages
Version: Latest
Hardware: Any
URL: https://www.elastic.co/guide/en/logstash/current/logst
ash-7-9-1.html
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: elastic at FreeBSD.org
Reporter: juraj at lutter.sk
Flags: maintainer-feedback?(elastic at FreeBSD.org)
Assignee: elastic at FreeBSD.org
Attachment #217745 maintainer-approval+
Flags:
Flags: maintainer-feedback+
Created attachment 217745
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=217745&action=edit
sysutils/logstash7: Update to 7.9.1
Hi,
please find the patch attached.
Changelog:
* Notable issues fixed:
- Fixes in Docker image configuration of Monitoring and Central Management:
- As more and more users adopt our docker images, we’ve been getting
reports on gaps where these images don’t provide all the configuration knobs
the other artifacts do. This release exposes more environment variables for
configuring proxy support and certificate verification mode for monitoring and
central management , and for configuring verification_mode
- Pipeline execution fixes to flushing and shutdown
- Since 7.2.0, a change caused terminating pipelines to not request input
plugins to cleanup before shutdown, which could cause leaks in resources that
weren’t freed during pipeline reloads. You can find more information on the fix
here:
- Logstash supports ordered execution for pipelines with a single worker. A
bug was found in this mode where the flushing mechanism wasn’t working,
preventing plugins like the aggregate filter from working correctly. This has
been fixed, and you can read the details here:
* Consistent Fingerprinting:
- Our fingerprint filter is a popular solution to perform deduplication of
data in downstream systems like Elasticsearch, by computing a hash value based
on data from each event. Users reported that this filter could produced
different values for events containing the same data since it didn’t ensure the
order in which Hash Maps/Objects/Ruby Hashes processed their key/value pairs.
This has now been fixed, and you can read more about how it was solved and all
the tests we’ve done here:
* Updated JRuby to 9.2.13.0:
- The new JRuby release brings greater stability to its code optimizations in
multithreaded workloads and a fix to exception handling in Windows
environments, both issues that could affect our users. See the JRuby release
notes for more information.
* Plugins:
- Avro Codec - 3.2.4
- [DOC] Add clarifications on partial deserialization
- Fingerprint Filter - 3.2.2
- Fixed lack of consistent fingerprints on Hash/Map objects
- Kv Filter - 4.4.1
- Fixed issue where a field_split_pattern containing a literal backslash
failed to match correctly
- Elasticsearch Input - 4.7.1
- [DOC] Updated sliced scroll link to resolve to correct location after doc
structure change
- [DOC] Added usage example of docinfo metadata
- Http_poller Input - 5.0.2
- [DOC]Expanded url option to include Manticore keys
- Snmp Input - 1.2.5
- Updated snmp4j library to v2.8.4
- Fixed: support SNMPv3 multiple identical security name with different
credentials
- Fixed: multithreading problem when using multiple snmp inputs with
multiple v3 credentials
- Syslog Input - 3.4.4
- Refactor: avoid global side-effect + cleanup
- avoid setting BasicSocket.do_not_reverse_lookup as it has side effects
for others
- Jdbc Integration - 5.0.6
- DOC:Replaced plugin_header file with plugin_header-integration file.
- Rabbitmq Integration - 7.1.1
- DOC:Replaced plugin_header file with plugin_header-integration file.
- Elasticsearch Output - 10.6.2
- [DOC] Added clarifying info on http compression settings and behaviors
- [DOC] Fixed entry for ilm_policy default value
Testport results:
https://freebsd-stable.builder.wilbury.net/data/11_4_RELEASE_GENERIC-default/2020-09-03_21h31m39s/logs/logstash7-7.9.1.log
https://freebsd-stable.builder.wilbury.net/data/12_STABLE_GENERIC_amd64-default/2020-09-03_23h40m09s/logs/logstash7-7.9.1.log
https://freebsd-current.builder.wilbury.net/data/13_CURRENT_GENERIC_amd64-default/2020-09-04_14h49m05s/logs/logstash7-7.9.1.log
Approving on behalf of elastic@
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-elastic
mailing list