[Carbon Black Cloud] - Fix @timestamp value by changing source to device_timestamp #9380
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.

100.0% Coverage on New Code
0.0% Duplication on New Code
Type of change
Proposed commit message
Till now the @timestamp value was created with the create_time value. But after some discussions internally it was found that this was incorrect as this is the time at which the event gets ingested into carbon black cloud. The correct source for the timestamp value is device_timestamp which is the time at which the event is detected by the device and reported. Changes have made to reflect this, and at the same time a new field has been introduced called create_time which mirrors the original create_time value so that data integrity is maintained with the original event.
NOTE
Please ignore the older commit history, as the branch was already existing locally without any changes from before but had merge commits as a result of merging upstream/main multiple times. Only the last few commits matter.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots
Test Results