-
Bug
-
Resolution: Done
-
Normal
-
Logging 6.3.z
-
Incidents & Support
-
False
-
-
False
-
NEW
-
NEW
-
Before this fix, the prune filter was failing to remove the .openshift.sequence field. With this fix, the field is now correctly pruned from the log record as expected.
-
Bug Fix
-
-
-
Logging - Sprint 277, Logging - Sprint 278
-
Moderate
Description of problem:
The `.openshift.sequence` not getting pruned in Logging 6.3
Version-Release number of selected component (if applicable):
.openshift.sequence is pruned in 6.2 but not pruned in 6.3
How reproducible:
1> Create CLF in 6.3 using below filters
spec: filters: - name: remove-pod-owner prune: in: - .kubernetes.pod_owner - .kubernetes.annotations - .kubernetes.container_image - .kubernetes.container_image_id - .kubernetes.container_iostream - .kubernetes.container_id - .kubernetes.namespace_id - .kubernetes.namespace_labels - .openshift - .openshift.sequence type: prune
2> Observe in ouput that openshift.sequence is not getting pruned
Additional info:
Same configuration works in 6.2 openshift.sequence is pruned
- is cloned by
-
LOG-7805 [release-6.3] The `.openshift.sequence` not getting pruned in Logging 6.3
-
- MODIFIED
-
- links to