10000 Tags · phobosq/beats · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Tags: phobosq/beats

Tags

v6.4.2

Toggle v6.4.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Set CFLAGS for Packetbeat arm64 cross-compile (elastic#7809) (elastic…

…#8409)

Cross-building Packetbeat was failing because the appropriate CFLAGS were not being set.

(cherry picked from commit 9796ec9)

v6.4.1

Toggle v6.4.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Document the use of `make release` instead of `make package` (elastic…

…#8187) (elastic#8304)

The `package` Makefile target was removed and replaced by the `release` and `snapshot` targets.

(cherry picked from commit 19f7dd3)

v5.6.12

Toggle v5.6.12's commit message
Bump docs version for 5.6.11 (elastic#8026)

v6.4.0

Toggle v6.4.0's commit message
Fix changelog entry (elastic#8001) (elastic#8003)

(cherry picked from commit 8e4fd66)

v6.3.2

Toggle v6.3.2's commit message
Fix filebeat registry meta being nil vs empty (elastic#7632) (elastic…

…#7644)

Filebeat introduces a meta field to registry entries in 6.3.1. The meta field is used to distuingish different log streams in docker files. For other input types the meta field must be null. Unfortunately the input loader did initialize the meta field with an empty dictionary. This leads to failing matches of old and new registry entries. Due to the match failing, old entries will not be removed, and filebeat will handle all files as new files on startup (old logs are send again).

Users will observe duplicate entries in the reigstry file. One entry with "meta": null and one entry with "meta": {}. The entry with "meta": {} will be used by filebeat. The null-entry will not be used by filebeat, but is kept in the registry file, cause it has now active owner (yet).

Improvements provided by this PR:

* when matching states consider an empty map and a null-map to be equivalent
* update input loader to create a null map for old state -> registry entries will be compatible on upgrade
* Add checks in critical places replacing an empty map with a null-map
* Add support to fix registry entries on load. states from corrupted 6.3.1 files will be merged into one single state on load
* introduce unit tests for loading different registry formats
* introduce system tests validating output and registry when upgrading filebeat from an older version

Closes: elastic#7634

(cherry picked from commit c558984)

v6.3.1

Toggle v6.3.1's commit message
Move changelog entries of backports for 6.3.1 (elastic#7460)

* Move changelog entries of backports for 6.3.1

* Move a couple of non-breaking changes to added

* Move Heartbeat breaking changes to Added

* Moved some more entries out of the breaking changes section

* Added suggestions in review

v5.6.11

Toggle v5.6.11's commit message
Bump version to 5.6.11 (elastic#7319)

v6.3.0

Toggle v6.3.0's commit message
Don't emit Kubernetes autodiscover events without host (elastic#7235) (

…elastic#7289)

Some kubernetes events are generated while the container is being
configured. It doesn't make sense to emit an event yet, as the host will
be update right afterwards.

This PR changes the code to ignore Pod events without an IP address.

(cherry picked from commit 7b5a7e4)

v5.6.10

Toggle v5.6.10's commit message
Fix out of bounds access in HTTP parser (elastic#6409) (elastic#6997) (

…elastic#7065)

A broken HTTP request caused the parser to report a panic.

Fixes elastic#6409

v6.2.4

Toggle v6.2.4's commit message
Defer registry state cleanup (elastic#6347) (elastic#6812)

- Defer registrar state gc until the registry needs to be written.
- when updating regitrar states from batch, ensure all updated states will
have same timestamp.

Depends on elastic#6346

(cherry picked from commit 2d2400b)
0