Bug #4237

The mentat-reporter.py is sending suspiciously too few reports per day

Added by Jan Mach 12 months ago. Updated 10 months ago.

Status:ClosedStart date:07/30/2018
Priority:UrgentDue date:
Assignee:Jan Mach% Done:


Category:Development - Core
Target version:2.1


After the migration the total number of reports sent and total number of reported events dropped dramatically. Verify, that there is nothing amis, fix any issues found.

Associated revisions

Revision c7085b59
Added by Jan Mach 12 months ago

Feature: Added total number of generated reports into periodical statistical summary.

By adding the total number of all generated reports and separate counters for summary and extra reports one will have better insight into the reporting performance. (Redmine issue: #4237)

Revision afc2168d
Added by Jan Mach 12 months ago

Fix: The reporting dashboard was wrongly using all reports for statistical calculations.

When calculating statistics, only summary reports should be considered. Otherwise some of the data can get calculated more than once and statistics are mangled. (Redmine issue: #4237)

Revision 7966301a
Added by Jan Mach 12 months ago

Refactor: Moved code generating overall overview report bodies to separate method.

(Redmine issue: #4237)

Revision 0ddab875
Added by Jan Mach 12 months ago

Feature: Improved thresholding cache logging ability.

Thresholding cache provides better logs, sot that administrator has better ability to verify correct functionality. (Redmine issue: #4237)

Revision 03126e10
Added by Jan Mach 12 months ago

Feature: Improved unit tests for mentat-informant.py.

Added unit test for testing method for saving attachments into JSON file. (Redmine issue: #1017,#4237,#4229)


#1 Updated by Jan Mach 12 months ago

  • Status changed from New to In Progress

I have started working on this issue. For now nothing seems to be wrong. I have suspicions that if there is an issue, it will be in thresholding mechanism, because the number of thresholded events in really high. I have improved the logging capabilities of thresholding cache to be able to inspect that further.

#2 Updated by Jan Mach 11 months ago

  • Target version changed from 2.0 to 2.1

#3 Updated by Jan Mach 10 months ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100

I haven`t found any problems or errors anywhere in reporting algorithm, that could cause drop in the number of reported events. I am closing this issue as resolved and will monitor the reporting further.

Also available in: Atom PDF