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

update chronicle backend #127

Merged
merged 1 commit into from
Sep 7, 2022
Merged

update chronicle backend #127

merged 1 commit into from
Sep 7, 2022

Conversation

crowdstrikedcs
Copy link
Member

Currently we use the process start time as the events timestamp. From feedback this should be instead the UTCTimestamp as often times a process may be running for a while before a detection is emitted. This will help to remove the delta between the detection being emitted and the time that Chronicle logs the event as occurring. As it stands, long running processes are causing Chronicle to not emit alerts at ingestion time due it thinking the event has occurred in the past.

Currently we use the process start time as the events timestamp. From feedback this should be instead the UTCTimestamp as often times a process may be running for a while before a detection is emitted. This will help to remove the delta between the detection being emitted and the time that Chronicle logs the event as occurring.
Copy link
Contributor

@carlosmmatos carlosmmatos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@isimluk isimluk merged commit 38d2d37 into main Sep 7, 2022
@isimluk isimluk deleted the crowdstrikedcs-patch-1 branch September 7, 2022 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants