Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[8.15](backport #40512) [ES output] Correctly log event fields in events log file #40531

Merged
merged 2 commits into from
Aug 19, 2024
Merged

[8.15](backport #40512) [ES output] Correctly log event fields in events log file #40531

merged 2 commits into from
Aug 19, 2024

Commits on Aug 14, 2024

  1. [ES output] Log event fields in events log file (#40512) 

    The Elasticsearch output, when faced with ingestion errors was logging
the raw publisher.Event that had already been encoded, hence no event
fields were present in the logs.

This commit fixes it by adding a String method to the encodedEvent
type and using the encodedEvent in the logs instead of the
publisher.Event.

(cherry picked from commit e7732c6)

# Conflicts:
#	libbeat/outputs/elasticsearch/client.go
    @belimawr @mergify
    belimawr authored and mergify[bot] committed Aug 14, 2024
    Configuration menu
    Copy the full SHA
    9ee160f View commit details
    Browse the repository at this point in the history

  2. Fix merge conflicts

    @belimawr
    belimawr committed Aug 14, 2024
    Configuration menu
    Copy the full SHA
    cf89b68 View commit details
    Browse the repository at this point in the history