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

[Google Workspace] @timestamp field contains improper value in google workspace #5301

Closed
brijesh-elastic opened this issue Feb 16, 2023 · 2 comments · Fixed by #5304
Closed
Assignees
Labels

Comments

@brijesh-elastic
Copy link
Contributor

While doing an audit on the older version of Google Workspace Integration, we saw an inconsistency in the graph for longer period. Looking at the code, It turned out that the @timestamp field was not mapped to the google_workspace.id.time and was storing the ingest time in the timestamp field.

Current behavior:
Google Workspace - 2

Expected behavior:
Google Workspace - 1

However, all the data is being ingested and can be sorted in a proper manner if google_workspace.id.time field is used for it.

@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@elasticmachine
Copy link

Package google_workspace - 2.2.3 containing this change is available at https://epr.elastic.co/search?package=google_workspace

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