Actions
User story #3024
closedUser story #2988: Log agent's report about failure in a dedicated logfile
[Integration] Log agent's report about failure in a dedicated logfile
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
Since #3018 (implementation part) is almost done, we can now begin its integration.
There's two things that must be done as integration part :
- First, add, in rudder-webapp.properties, the property defining log frequency.
The property is called : rudder.batch.reports.logInterval
only the property need to be inserted, but here it is with it commentary :#################### # Report logger ################################################################## #################### # # Non compliant reports logger. # # Non compliant reports can be logged by rudder. # A value need to be specified to determine the interval between two logger run. # A negative or 0 value means to not log reports. # rudder.batch.reports.logInterval=1
- Secondly, to keep track and persist the logger process, we need to keep the last id processed by the logger.
To do that we want to add a new table in the database containing only the last id processed.
The table name is ReportLogLastId with only one column lastId which is an integer.
The creation SQL request has been added to file Reportsschema.sql, but in case of migration that table has to be created.
I added a migration file : dbMigration-2.4-2.5-last-error-report-id.sql
pull request : https://github.com/Normation/rudder-packages/pull/7
Actions