-
Bug
-
Resolution: Unresolved
-
Normal
-
Logging 6.4.z
-
Quality / Stability / Reliability
-
False
-
-
False
-
NEW
-
NEW
-
Bug Fix
-
-
-
Low
Description of problem:
LOG-7609 proposed to add a feature to extract the timestamp from logs at the point of ingestion. Investigation of the sink determined this to be problematic because it only evaluates the first N bytes of the message and it may not be consistent if they payload has more then one timestamp value (i.e. message is Viaq json). Additional inspection of ViaQ normalization found that timestamp is extracted from the log event for all sources with the exception of kube and openshift API audit logs.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
- ...
Actual results:
Expected results:
Additional info:
- is related to
-
LOG-7609 Allow configuration of splunk to auto extract the timestamp
-
- Closed
-
-
LOG-7612 Add auto extract timestamp to Splunk tuning
-
- Closed
-
- relates to
-
OBSDA-1185 Feature to enable "auto_extract_timestamp=true" from Red hat logging operator to splunk
-
- In Progress
-
- links to