Shorten events/search output in case of too long events
|Assignee:||Jan Mach||% Done:|
|Category:||Development - GUI|
If events to show are too big (lot of sources/targets), search output chokes.
Trim those lists (all lists, even Categories or whatever may get screwed up by sending clients) early in the process to not choke reading, processing, templating and client browser on it.
Fix: Fixed the output on web interface in case there are too many sources/targets/ports in the IDEA message.
It was possible for the IDEA message to contain even hundreds of thousands of IP addresses or ports in in source/target subkeys. In this case the event search and show views were rendered unusable. It could take minutes to render the result page and the display was cluttered and unusable. This patch should fix that. (Redmine issue: #4261)
#2 Updated by Pavel Kácha 12 months ago
Note that Aug 7 labrea reporter got silenced (produces trimmed and split events), so look for older examples. (Maybe based on original Radko’s example https://mentat-hub.cesnet.cz/mentat/events/show/26aa5f45-1a36-4bf4-b1ee-f2d5e9e1c140).
#3 Updated by Radko Krkoš 11 months ago
Another related effect is overload of disk subsystem (sustained disk utilization of ~80%) somewhere during import chain when processing such large events, leaving very little room for other activities, severely degrading overall performance. This has to be investigated further as it is effectively a DoS vector and there is a real chance of such events appearing from aggregators in near future.