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

Fix date format in Mongodb Ingest pipeline #7974

Merged
merged 2 commits into from
Aug 15, 2018

Conversation

kvch
Copy link
Contributor

@kvch kvch commented Aug 15, 2018

Previously, number of month was not parsed correctly in case of mongodb/log Filebeat module. Now this is fixed and the expected outputs are updated accordingly.

Closes #7958

@kvch kvch requested a review from ruflin August 15, 2018 12:01
Copy link
Member

@ruflin ruflin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WFG

Does this need a bug and needs backport label?

@kvch kvch added the needs_backport PR is waiting to be backported to other branches. label Aug 15, 2018
@kvch
Copy link
Contributor Author

kvch commented Aug 15, 2018

I added the label and the failing test in Jenkins is unrelated.

@ruflin ruflin merged commit 87b9f32 into elastic:master Aug 15, 2018
@ruflin
Copy link
Member

ruflin commented Aug 15, 2018

@kvch Haven't seen that failure yet, should we open a Github issue for it?

kvch added a commit to kvch/beats that referenced this pull request Aug 15, 2018
Previously, number of month was not parsed correctly in case of mongodb/log Filebeat module. Now this is fixed and the expected outputs are updated accordingly.

Closes elastic#7958
(cherry picked from commit 87b9f32)
@kvch kvch added v6.5.0 and removed needs_backport PR is waiting to be backported to other branches. labels Aug 15, 2018
@kvch
Copy link
Contributor Author

kvch commented Aug 15, 2018

Opened: #7977

ruflin pushed a commit that referenced this pull request Aug 16, 2018
…7978)

Previously, number of month was not parsed correctly in case of mongodb/log Filebeat module. Now this is fixed and the expected outputs are updated accordingly.

Closes #7958
(cherry picked from commit 87b9f32)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mongodb filebeat parsed timestamp is wrong
2 participants