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.

Sign up for GitHub

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

Provide more information on alert delays causes #1698

Merged
merged 1 commit into from
Mar 14, 2024
Merged

Provide more information on alert delays causes #1698

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions docs/xdr/FAQ/Alerts_qa.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,5 +14,10 @@ If it is involved in the current alert, the bell is not displayed.

Besides matching a rule in real time, an alert can be triggered with a delay when:

- An IOC is published, old events are scanned and if an event matches, the rule will automatically trigger an alert.
- Reingesting old logs
- An IOC is published, old events are scanned and if an event matches, the rule will automatically trigger an alert.
- Logs from the source were received by Sekoia with a delay. Common route causes:
* the log collection was interrupted, if logs are buffered loccaly on customer's side, before being sent later when the collection restarts
* Reingestion of old logs

!!! Note
See more informaiton on `timestamp` and `event.created`fields [here](Events_qa.md#timestampeventcreated-eventstart-eventend-meaning).
Loading