Actions
User story #11107
closedCompliance logfile parsing regex
Effort required:
Name check:
Fix check:
Regression:
Description
Hi,
At https://www.rudder-project.org/doc-4.1/_monitoring.html#_monitor_events you have a format for Logstash parsing of non-compliant-reports.log.
You might want to add the generic regex-formatted parsing (which could be used for other similar log-processing frameworks):
^\[(?P<Date>[^\]]+)\] N: (?P<NodeUUID>[^ ]+) \[(?P<NodeFQDN>[^\]]+)\] S: \[(?P<Result>[^\]]+)\] R: (?P<RuleUUID>[^ ]+) \[(?P<RuleName>[^\]]+)\] D: (?P<DirectiveUUID>[^ ]+) \[(?P<DirectiveName>[^\]]+)\] T: (?P<TechniqueName>[^/]+)/(?P<TechniqueVersion>[^ ]+) C: \[(?P<ComponentName>[^\]]+)\] V: \[(?P<ComponentKey>[^\]]+)\] (?P<Message>.+)$
Updated by Alexis Mousset over 7 years ago
- Assignee set to Alexis Mousset
- Target version set to 3.1.22
Updated by Alexis Mousset over 7 years ago
- Status changed from New to In progress
Updated by Alexis Mousset over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-doc/pull/354
Updated by Alexis Mousset over 7 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-doc|a279164ae849b1a423a3cbd61c00440dcb093e91.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to Released
Actions