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
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:
Expected behavior:
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.
The text was updated successfully, but these errors were encountered:
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 thegoogle_workspace.id.time
and was storing the ingest time in the timestamp field.Current behavior:
![Google Workspace - 2](https://user-images.githubusercontent.com/123942796/219366078-f5698c10-1aa5-4504-8d7c-b42a76a8d71a.png)
Expected behavior:
![Google Workspace - 1](https://user-images.githubusercontent.com/123942796/219366045-599b485b-aa59-45aa-b138-0d2de0073ae3.png)
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.The text was updated successfully, but these errors were encountered: