Previously it was possible that during the daemon shutdown some IDEA messages could remain uncommitted when running in bulk commit mode. It was necessary to make use of 'stop' event to force commit and switch back to immediate commit mode for the rest of the events that still might be in the event queue (it is not guaranteed the stop event will be last in the queue, some of the previous events might still schedule some other event, which will be handled after the stop event). (Redmine issue: #4572)

(Redmine issue: #3361)

It is much better approach to leave all geoipupdate related stuff outside of the Mentat package a let administrator to install geolocation databases himself. Documentation was updated accordingly. (Redmine issue: #6157)

(Redmine issue: #3387)

(Redmine issue: #5751)

Updated installation documentation page to reflect Postgresql upgrade to v12 and new geoipupdate prerequisite.

(Redmine issue: #6157)

(Redmine issue: #6157)

(Redmine issue: #6157)

(Redmine issue: #6157)

(Redmine issue: #6157)

(Redmine issue: #6157)

MaxMind service changed its policy for downloading its free IP databases. This commit features necessary test code and configuration changes to make GeoIP enrichment plugin working again. There will be also documentation update to reflect necessary steps for upgrading, once these are finetuned. (Redmine issue: #6157)

(Redmine issue: #5751)

(Redmine issue: #5751)

(Redmine issue: #5751)

(Redmine issue: #5751)

This configuration is more conservative regarding the possible data loss in case of failure. (Redmine issue: #4572)

(Redmine issue: #3443)

The mentat-storage.py daemon has now ability to use transaction savepoints to reduce number of commits and thus greatly enhance event storage rate. The feature is configurable and optional. The mentat.services.eventstorage needed to be upgraded to support this new feature. Also, the pyzenkit module contained a bug, which prevented this feature to work correctly, so it needed to be fixed as well. (Redmine issue: #4572)

(Redmine issue: #6105)

(Redmine issue: #3443)

(Redmine issue: #4384)

(Redmine issue: #6096)

Added the ability to list all currently running event database queries and limiting number of queries per user.

Users are now limited in the number of event search queries they can execute on the event database. Also the list of all currently running queries available for administrator now contains all queries, not just the named ones. But only the named ones can be canceled from the interface, you must use PostgreSQL console to cancel the others. (Redmine issue: #4384)

(Redmine issue: #3361)

This feature is available for system administrators to keep them informed about the time consumption of different search stages: preparation, searching, postprocessing. (Redmine issue: #4384)

(Redmine issue: #4384)

List of running queries now contains context action for stopping that query. (Redmine issue: #4384)

(Redmine issue: #4384)

(Redmine issue: #4384)

(Redmine issue: #4384)

(Redmine issue: #4384)

(Redmine issue: #4384)

* Invalid dictionary declaration.
* Invalid working with aware and unaware timestamps.

(Redmine issue: #4384)

(Redmine issue: #4384)

This migration requires some maintenance tasks to keep the performance level. To make it easier for the user it is best to put it directly to the migration script. (Redmine issue: #4274,#4275)

By introducting new type of SELECT query the condition needed to be updated accrdingly. (Redmine issue: #4274,#4275)

By this move we attempt to speed up the searching process and lower the usage of system resources, because the amount of data the database engine needs to load and process will be significantly smaller. (Redmine issue: #4274,#4275)