Project

General

Profile

Actions

Feature #7692

open

Better reporting

Added by Jakub Judiny 7 months ago. Updated 3 days ago.

Status:
In Review
Priority:
Normal
Assignee:
Category:
Development - GUI
Target version:
Start date:
11/08/2023
Due date:
% Done:

0%

Estimated time:
To be discussed:
No

Description

- support for vulnerable-implementation event class (VA2AM)
- Event class management GUI module (mentat-inspector should create inspection rules based on information from this module)
- better aggregations (more aggregated fields, and aggregation by detectors, aggregations set in mentat.const, aggregate only relevant source sections)
- better report show view (more displayed information based on event class settings, move JSON to custom view and add syntax highlighting, better integration with events module, better UI - get rid of tabs)
- change report emails format to be similar to new web report view
- subclassing

Wiki: Reporting


Related issues

Related to Mentat - Bug #7700: When accessing event search by event-class using context search, search form is not able to be rendered for unauthorized usersResolvedJakub Judiny01/10/2024

Actions
Actions #1

Updated by Jakub Judiny 6 months ago

  • Status changed from New to In Progress
Actions #2

Updated by Jakub Judiny 5 months ago

Rajmund Hruška these are the temporary changes to reporting we talked about. Could you please take a look at it and deploy it on Alt?

Actions #3

Updated by Jakub Judiny 3 months ago

- support for vulnerable-implementation event class (VA2AM)
- Event class management GUI module (mentat-inspector should create inspection rules based on information from this module)
- better aggregations (more aggregated fields, and aggregation by detectors, aggregations set in mentat.const, aggregate only relevant source sections)
- better report show view (more displayed information based on event class settings, move JSON to custom view and add syntax highlighting, better integration with events module, better UI - get rid of tabs)
- HTML report emails
- subclassing

Actions #4

Updated by Jakub Judiny 3 months ago

  • Description updated (diff)
Actions #5

Updated by Jakub Judiny 3 months ago

  • Related to Bug #7700: When accessing event search by event-class using context search, search form is not able to be rendered for unauthorized users added
Actions #6

Updated by Jakub Judiny 3 months ago

  • Target version changed from Backlog to 2.13
Actions #7

Updated by Jakub Judiny 2 months ago

  • Description updated (diff)
Actions #8

Updated by Pavel Kácha 26 days ago

From today's meeting:

  • Subclass definition can be pynspect expression, similar to class
  • Dates
    • Mail: rfc3339ish (but FTAS usable), with spaces between date/time/timezone, completely vertical format (no table), if group decided to have local date, show both local and UTC, otherwise just UTC
    • Web: rfc3339is, honor user timezone setting within the table, in the popup bubble show localised date (+ timezone name, like Europe/Prague), possibly UTC, and maybe other format (real rfc3339 with T maybe)
Actions #9

Updated by Jakub Judiny 23 days ago

Just a note: I found out that web time is not displayed based on user settings, but based on group reporting settings at the time the report was created.

Actions #10

Updated by Jakub Judiny 23 days ago

  • Status changed from In Progress to Resolved
Actions #11

Updated by Pavel Kácha 6 days ago

  • Related to Feature #7739: Extend report search for other attributes from metadata added
Actions #12

Updated by Pavel Kácha 5 days ago

  • Related to deleted (Feature #7739: Extend report search for other attributes from metadata)
Actions #13

Updated by Pavel Kácha 5 days ago

Note: will need some nice mention in Release notes

Actions #14

Updated by Rajmund Hruška 3 days ago

  • Status changed from Resolved to In Review
Actions

Also available in: Atom PDF