Actions
Bug #16255
closed
Improve performance of logs parsing by rsyslog
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
We can simplify the parsing of logs by rsyslog, and also make it more efficient, by taking into account that there is a @0@ token at the middle of reports
simplifying it improves perf: less message dropped on system where load is too hig
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1563
Updated by Nicolas CHARLES almost 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|c97840d9dfe71740b6dda6d7b0c9046d2e2a4f94.
Updated by Alexis Mousset almost 5 years ago
- Subject changed from Improve parsing of logs by rsyslog to Improve performance of logs parsing by rsyslog
- Name check changed from To do to Reviewed
Updated by Alexis Mousset almost 5 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ almost 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.
Actions