You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
added a commit
to kvch/beats
that referenced
this issue
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.
Closeselastic#7958
(cherry picked from commit 87b9f32)
…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)
Hi All.
I recently tried to start mongodb filebeat plugin (v 6.3.2)
To my surprise, all parsed logs appears as from Jan this year (day is correct).
json doc stored in ES (anonymized)
And a log line looks like (anonymized):
2018-08-13T11:54:11.537+0000 I XX YYY
The text was updated successfully, but these errors were encountered: