-
Task
-
Resolution: Done
-
Critical
-
None
-
None
Summary
Implement the JSON forwarding proposal
Acceptance Criteria
- Transformed records include additional top-level fields
- The schema field is optional
- Structured JSON container and journal records are parsable
- Legacy managed ES continues to utilize "flat_labels" with no structured messages
- The 'structured' field is populated as a map for JSON messages and 'message' field is unpopulated
- The 'message' field is populated as-is string for non-JSON messages and the 'structure' field is unpopulated
Notes
- Additional acceptance criteria can be determined from the proposal
- is related to
-
LOG-1148 Stop mangling JSON records for non-elasticsearch outputs
- Closed
-
LOG-1099 Add JSON pipeline to Elasticsearch
- Closed
-
LOG-1153 Create rollover/delete policies for json indices
- Closed
- relates to
-
LOG-1355 No default output configuration in Clusterlogforwarders.logging.openshift.io
- Closed
-
LOG-2011 Support Json Forwarding feature
- Closed
- links to
(4 links to)