Update event.kind allowed value descriptions to clarify usage of "alert" and "signal" #1548
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.
We have received questions from community members about when to use
event.kind:alert
vs.event.kind:signal
These allowed values can cause confusion, since documents that contain
event.kind:signal
are often referred to as "alerts."As background, the overloading of the term "alerts" is a longstanding issue in security information and event management, where there was frequently confusion between external alerts generated by some external system and alerts generated by the SIEM itself. Any usage of the unmodified "alerts" was thus ambiguous.
The proposed language attempts to provide clear guidance:
event.kind:alert
event.kind:signal