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.

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

FileBeat log configuration not working #2

Open
pranav-patil opened this issue Sep 25, 2019 · 0 comments
Open

FileBeat log configuration not working #2

pranav-patil opened this issue Sep 25, 2019 · 0 comments
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@pranav-patil
Copy link
Owner

The LogStash service is unable to fetch the logs from FileBeat with the filebeat-ds.yaml config file. Currently the application logback directly sends all the logs to 5044 to logstash server. The application logback should be switched to standard ConsoleAppender, with a LogstashEncoder needed to encode logs in JSON. Filebeat should be configured to extract the application logs from the Kubernetes Pod logs.
FileBeat later decodes JSON log using decode_json_fields to map each field (such as timestamp, version, message, logger_name, …) to an indexed Elasticsearch field.

<configuration>
    <appender name="jsonConsoleAppender" class="ch.qos.logback.core.ConsoleAppender">
        <encoder class="net.logstash.logback.encoder.LogstashEncoder"/>
    </appender>
    <root level="INFO">
        <appender-ref ref="jsonConsoleAppender"/>
    </root>
</configuration>
@pranav-patil pranav-patil added bug Something isn't working enhancement New feature or request labels Sep 25, 2019
@pranav-patil pranav-patil self-assigned this Sep 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant