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

Jump to bottom

Discuss about option singleMessage #32

Open
c8y3 opened this issue Nov 22, 2021 · 2 comments
Open

Discuss about option singleMessage #32

c8y3 opened this issue Nov 22, 2021 · 2 comments

Comments

@c8y3
Copy link
Collaborator

c8y3 commented Nov 22, 2021 •
edited
Loading

When the backlog is activated, the plugin will, by default, generate one log per message in the backlog.
If option singleMessage is activated, only one log, with the complete backlog will be generated.
Maybe we should consider to invert the option singleMessage (it should be activated by default to avoid unnecessary flooding)
Discuss...
@c8y3 c8y3 changed the title Remove option singleMessage Discuss about option singleMessage Nov 30, 2021
@frantz45
Copy link
Collaborator

This feature is important to work with SOAR which are not able to aggregate alerts based on a specific field (alert_id)

@frantz45
Copy link
Collaborator

It may be linked with #41

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@c8y3 @frantz45