Skip to content

Trim the JSON source in indexing slow logs backport#38081 #38156

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

Merged
merged 1 commit into from
Feb 1, 2019

Conversation

pgomulka
Copy link
Contributor

@pgomulka pgomulka commented Feb 1, 2019

The '{' as a first character in log line is causing problems for beats when parsing plaintext logs. This can happen if the submitted document has an additional '\n' at the beginning and we are not reformatting.
Trimming the source part of a SlogLog solves that and keeps the logs readable.

relates #38080
backport #38081

The '{' as a first character in log line is causing problems for beats when parsing plaintext logs. This can happen if the submitted document has an additional '\n' at the beginning and we are not reformatting. 
Trimming the source part of a SlogLog solves that and keeps the logs readable.

closes elastic#38080
@pgomulka pgomulka self-assigned this Feb 1, 2019
@pgomulka pgomulka added :Core/Infra/Logging Log management and logging utilities backport v6.7.0 labels Feb 1, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@pgomulka
Copy link
Contributor Author

pgomulka commented Feb 1, 2019

@elasticmachine run elasticsearch-ci/1

@pgomulka pgomulka merged commit b10e95f into elastic:6.x Feb 1, 2019
@pgomulka pgomulka removed the v6.7.0 label Feb 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport :Core/Infra/Logging Log management and logging utilities
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants