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

Mongodb filebeat parsed timestamp is wrong #7958

Closed
piotrrybicki opened this issue Aug 13, 2018 · 0 comments · Fixed by #7974
Closed

Mongodb filebeat parsed timestamp is wrong #7958

piotrrybicki opened this issue Aug 13, 2018 · 0 comments · Fixed by #7974
Assignees
Labels

Comments

@piotrrybicki
Copy link

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)

{
"_index": "filebeat-mongodb-log-6.3.2-2018.08.13",
"_type": "doc",
"_id": "jz_pMmUBbSk-ag5Bud9u",
"_version": 1,
"_score": null,
"_source": {
"offset": 125734985,
"prospector": {
"type": "log"
},
"read_timestamp": "2018-08-13T10:51:38.085Z",
"source": "/var/log/mongodb/mongod.log",
"fileset": {
"module": "mongodb",
"name": "log"
},
"input": {
"type": "log"
},
"@timestamp": "2018-01-13T10:51:37.575Z",
"beat": {
"hostname": "xxx",
"name": "xxx",
"version": "6.3.2"
},
"host": {
"name": "xxx"
},
"mongodb": {
"log": {
"severity": "I",
"component": "xxx",
"context": "xxx",
"message": "xxx"
}
}
},
"fields": {
"@timestamp": [
"2018-01-13T10:51:37.575Z"
]
},
"sort": [
1515840697575
]
}

And a log line looks like (anonymized):

2018-08-13T11:54:11.537+0000 I XX YYY

@kvch kvch self-assigned this Aug 13, 2018
ruflin pushed a commit 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.

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.

Closes elastic#7958
(cherry picked from commit 87b9f32)
ruflin pushed a commit that referenced this issue 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
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants