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
## Description
When scraping 4.2 clusters, it seems that timestamps are formatted like this: `2022-09-16T15:26:52.563+0000`, but on 5.0 it's formatted like this: `2022-09-16T15:26:52.563+00:00`.
This causes the timestamp to fail to parse correctly.
Time failed to parse correctly {"kind": "receiver", "name": "mongodbatlas", "pipeline": "logs", "error": "parsing time \"2022-09-16T15:38:11.184+0000\" as \"2006-01-02T15:04:05.000-07:00\": cannot parse \"+0000\" as \"-07:00\""}
Additional context
No response
The text was updated successfully, but these errors were encountered:
BinaryFissionGames
changed the title
[mongodbatlasreceiver] Timestamp - audit log fails to parse on 4.2 clusters
[mongodbatlasreceiver] Audit log timestamp parsing fails to parse on 4.2 clusters
Sep 16, 2022
BinaryFissionGames
changed the title
[mongodbatlasreceiver] Audit log timestamp parsing fails to parse on 4.2 clusters
[receiver/mongodbatlas] Audit log timestamp parsing fails to parse on 4.2 clusters
Sep 16, 2022
What happened?
Collector version
c0666b6
Environment information
No response
OpenTelemetry Collector configuration
No response
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: