Actions
Bug #13427
closed
On error on nodecompliance SQL, logs are huge
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
0
Name check:
Fix check:
Regression:
Description
One user reported an error on insertion for "nodecompliance" table. That resulted in the full row content being logged, and that content is huge (it is the JSON serialisation of detailled compliance).
We must only log the error without details, and only add details for debug level (or trace).
The problematic insert was:
[2018-09-07 02:22:56] ERROR report - Error when saving node compliances: Batch entry 0 insert into nodecompliance (nodeid, runtimestamp, endoflife, runanalysis, summary, details)
values (‘9c8bab57-d6e2-475b-99f9-df2e8e0521cf’, ‘2018-09-07 02:22:32+02’, ‘2018-09-07 02:32:32+02’, ’{
...
huge json
...
}’) was aborted: ERROR: permission denied for relation nodecompliance Call getNextException to see other errors in the batch.
Updated by 
Updated by 
Updated by 
Updated by
Actions