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

Group-By Function for Event View #204

Closed
mattnewham opened this issue Aug 3, 2012 · 2 comments
Closed

Group-By Function for Event View #204

mattnewham opened this issue Aug 3, 2012 · 2 comments

Comments

@mattnewham
Copy link

I would like to see the ability to "group-by" certain elements in the event view. For example, I would often prefer to group events by message ID, regardless of where they came from. Depending on my analysis technique, I may prefer to view events this way rather than the significantly more granular "per-event" view shown by default.

I am aware I can sort-by event type, but performing a "group-by" significantly reduces the amount of lines displayed in the window and allows me to make a decision what I would prefer to look at and in what order of priority.

@djcas9
Copy link
Contributor

djcas9 commented Aug 6, 2012

Doing a dynamic group-by is a little difficult because each query may need to be custom for performance reasons. Have you seen the Group by unique session option under the "Filter Options" menu? This may work for the time being until something is put in place to better sort the data. A lot of limitations are due to the structure of the database schema and to keep legacy support for BASE/Barnyard it will have to stay unchanged.

@mattnewham
Copy link
Author

Hey Dustin

The group by unique sessions feature actually works quite well and is certainly going in the right direction! Thanks for pointing that out. I will see how that works out for us. I suspect most of these issues can be solved by more efficient rule writing (flowbits, thresholding etc). I guess most of the issues I come accross are due to a signature causing an excessive number of hits due to error or development. In this case I would prefer to purge the DB as raised in other tickets on here.

@djcas9 djcas9 closed this as completed May 5, 2013
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

No branches or pull requests

2 participants