Moved some content from website to autogenerated documentation to prevent from repeating the same content on multiple places. Added information about versioning and tagging. (Redmine issue: #3361)

The Sphinx-doc reported various minor bugs when generating the documentation. These should be fixed now. (Redmine issue: #3361)

* Added section for useful links and references.
* Created substitution to create direct link to Git revision page in our project support system.
* Created substitution for easy generation of documentation links.

(Redmine issue: #3361)

(Redmine issue: #3387)

(Redmine issue: #4307)

According to the documentation, the MTA sets the Return-Path header not using email message headers, but using envelope headers. It was necessary to use command line option of sendmail utility to pass configured value of Return-Path down to email. (Redmine issue: #4307)

Currently focus of this section is Mentat system health monitoring. (Redmine issue: #4222,#3361)

(Redmine issue: #4213,#1017,#3361,#3443)

(Redmine issue: #4114)

The component identification is not available through daemon object. (Redmine issue: #4262,#3443)

(Redmine issue: #3361)

(Redmine issue: #4262,#1017,#3443)

Previously the enrichment plugin reload was hardcoded in a way, that during the reload a brand new instance of the plugin was created, which resulted in discarding of the internal state of the plugin. For some use cases this was not appropriate. The plugin reload event is now implemented differently, so the insternal state is kept. (Redmine issue: #4262)

I have added prototype periodical anomaly detection scripts created by Pavel Kácha into Mentat package. So far these are just simple shell scripts intended to be executed periodically via cron that will simply use the PSQL utility to query database and send the result via email. Possible improvements might be to envelope these into Mentat script to make use of common configurations. (Redmine issue: #4222)

(Redmine issue: #4307)

(Redmine issue: #3387)

This is a final piece in the puzzle. It was necessary to implement mechanism for removing outdated records from enumeration tables. (Redmine issue: #4252)

With the addition of database migration tools the steps for successfull upgrade of Mentat system within the 2.x series had to be documented. (Redmine issue: #4252)

Added debug level logs to better track precaching operations. (Redmine issue: #4252)

(Redmine issue: #4252)

Our database specialist pointed out, that currently the distinct value calculations for event table columns result in heavy paralel sequential scans. This is because the data model is optimized for efficiency and we are using as few relations and joins as possible for best performance. This means our event data model is flat and there are no tables containing common values like categories etc. The drawback if this approach is, that for retrieving column value enumerations the queries are very, very resource consuming. These results are used "only" for things like generating select boxes containing possible values in the web interface. These queries are executed periodically and they can load the database for tens of seconds, which is does not make sense in comparison with the use cases. Therefore we have decided to implement optimalization mechanism, that will cleverly precalculate the lists into separate tables and fetching it then will be a matter fraction of a second. (Redmine issue: #4252)

(Redmine issue: #1017)

It was possible for the reporter to attach files of any size to the report. The MTA then complained for the message being too big and refused to mail it. Now it is possible for each group co configure maximal attachment size limit (defaults to 10MB). Attachment files exceeding this limit will not be added to the report and user will be informed in the email text to download it from the server. (Redmine issue: #4232)

With future improvements of database schema there must be a mechanism for performing database migrations. Problem is we have two databases, one accesed via SQLAlchemy and the second directly via Psycopg2. I have selected to use Flask-Migrate plugin built on top of Alembic to perform metadata database migrations. (Redmine issue: #4230)

This step will greatly simplify the requirements for our automated build and deployment system. The MongoDB related code is still there for the purposes of data migration. (Redmine issue: #4225,#3387,#1017)

Previous revision f3c669ae did not fully resolve the issue with incorrect pager links. It was necessary to implement generic mechanism for storing information about which fields can contain multiple values directly in the form object. I have used static class method to solve this issue. (Redmine issue: #4090)

(Redmine issue: #3387)

Some of the original content was moved to a web page of Mentat system as a service operated by CESNET. Some of the content was abbreviated without any replacement. (Redmine issue: #4114)

* Implemented global macro for rendering popover help.
* Added help text for all object management dashboard panels.
* Translated all newly added strings to czech language.

(Redmine issue: #4221)

* Added panels for filters with future and expired validity.
* Added panel for groups with custom target emails.
* Added panel for groups with custom reporting timing.

(Redmine issue: #4221)

(Redmine issue: #4221)

* Divided dashboard panels into separate tabs (users, groups, filters, settings)
* Added more hopefully usefull info panels for users and groups
* Added panels for reporting settings
* Added icon for reporting settings module
* Translated newly added strings into czech language

(Redmine issue: #4221)

* Added column with item age and creation time.
* Added column with group name to panels related to filters.
* Added more item context actions.

(Redmine issue: #4221)

Feature: Added explicit usage of right submenu alignment for all relevant item context action menus.

(Redmine issue: #1017,#3443)

According to the recommendation of our database specialist the event table watchdog query was rewritten for better performance. New approach makes better use of database and results in better database query plan and procesing time. More detail on the issue in appropriate Redmine ticket. (Redmine issue: #4100)

(Redmine issue: #4221)

(Redmine issue: #3443)