(Redmine issue: #3443)

(Redmine issue: #4321)

Previous feature was not working in Python3.5, because the 'timespec' parameter of datetime.datetime.isoformat() method was added in Python 3.6. (Redmine issue: #4321)

The reporting dashboards now demonstrate new feature: quick search options and time window paging. For performing common quick searches it is now possible to choose the appropriate option from presented list and get results without choosing the time windows manually. Additionally the result page for this quick search option provides means for paging back and forward in time with appropriate time window. For example you may search for current month and then use the time window paging to get results for previous month. (Redmine issue: #4321)

(Redmine issue: #3443)

This commit introduces new group of timescatter visualisations. It is still work in progress and it is being deployed prematurely for demonstartion purposes. The chart capabilies are being demonstrated on reporting dashboard to show the number of reports being generated in different time of day and days. Many time consuming features were not yet implemented like exporting to CSV and rendering dataset table, I would not be wise to spend time implementing feature, that will be rejected in the end. (Redmine issue: #4321)

(Redmine issue: #3443)

NVD3 charting library has a drawback, that it does not render correctly charts, that are initially hidden from the user, for example in tab panels. These charts are not re-rendered on tab show and have to be updated manually. Previous solution used simple mechanism of emiting window.resize event, which was captured by all charts that were currently on the page. This approach could be very slow on some views with many charts and it was very inefficient, because all chart were updated regardless of their visibility to the user. New approach is much smarter, because it updates only those charts, that are necessary. There is still room for improvement though, it does not work optimally for nested tabs. This drawback will be fixed in some of the following commits. (Redmine issue: #4321)

Similarly to timeline module and reporting dashboard view the timeline calculations were implemented for event dashboard view. This required some additional minor tweaking and improvements in overall design. (Redmine issue: #4321)

The method for outputting the byte sizes in human readable and localized strings was redesigned.

Translated recently implemented features. (Redmine issue: #3387)

Improved layout of DOM elements, added more PostgreSQL configurations to list of displayed values, enhanced visual style and amount of the information displayed in PostgreSQL configuration view table.

Database status module now provides more information about current PostgreSQL settings.

(Redmine issue: #3361)

After previous commits the database status view module was broken, because it was still using old charting code. This is fixed in this commit. Additionally, this commit introduces new ability to define custom value label and formatter for dict based pie datasets. The implementation of this feature was necessary to enable displaying values in tables as size in bytes instead of simple count (which was necessary for datasets showing sizes of database tables). (Redmine issue: #4321)

Added few remarks pointed out by Radko Krkoš to the documentation section about RAM based filesystem. (Redmine issue: #3361)

Certain key categories (IPs, abuses, ...) in pie chart dataset tables have associated context search actions that provide user with ability to quickly search different parts of the application. (Redmine issue: #4321)

It is now possible to use main logger from within the Jinja2 templates.

All blueprints can similarly to registering menu entries register context search actions for one or more groups. These are then used for generating context search action dropdown menus for various items like IP addresses, groups, etc. One of the example use cases is the event search result page, which contains action search menus for each of the displayed IP address, abuse group, category, etc. (Redmine issue: #4321)

Sorry, previous fix was not correct.

(Redmine issue: #3361,#4570)

There was an invalid expression in the algorithm. Also the setdefault method is much more convenient than previous solution.

The warning setting results in additional and unnecessary email being sent in case the module is executed from cron.

Radko Krkoš authored 6 years ago and Jan Mach committed 6 years ago

Enumeration tables used to speed up enum generation for filtering were incorrect as multiple NULL values could have been inserted increasing the table size over time. This affected the enumerations for non-array parameters only. As the 'any value' and 'without value' options are added automatically, we can disable support for NULLs, fixing the growing tables.

(Redmine issue: #4367)

(Redmine issue: #4321)

(Redmine issue: #4321)

It has special meaning, it does not belong to any data series. (Redmine issue: #4321)

After previous changes the statistics panel in report detail view needed to be updated as well. I have also unified HTML coding style to match other similar views (eg. event dashboard view). (Redmine issue: #4321)

Various secondary statistics like counts, minimums, maximums and sums were pre-calculated together with regular statistics. These operations do not make sense anymore from multiple point of views:
- They are not used during chart generation anymore, because these values are calculated by JavaScript code.
- They do not make sense during merging statistical data, because they produce incorrect results anyway (for example without knowing the exact omitted values it is not possible to calculate the counts, averages, minimums etc.).

(Redmine issue: #4321)

Translated recently implemented features. (Redmine issue: #3387)

(Redmine issue: #4321)

(Redmine issue: #4321)

(Redmine issue: #4321)

Added missing pie charts containing totals to all timeline charts. Hidden the abuses panel from external processing statistics display. (Redmine issue: #4321)