-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
Logging 5.4.1
-
False
-
None
-
False
-
NEW
-
NEW
-
-
Logging (Core) - Sprint 220
BACKGROUNG:
Logs are appearing in incorrect sequence in Kibana for this an issue was raised and was fixed in Logging 5.4.0.
[+] https://issues.redhat.com/browse/LOG-2099
The bug is actually fixed for configuration without structuredTypeKey: openshift.labels.myLabel
When structuredTypeKey: openshift.labels.myLabel is not used in CLF openshift.sequence is created in below way
~~~
{
"_index" : "app-000008",
.....
.....
"openshift" :
,
~~~
Example included with Kibana images in https://access.redhat.com/solutions/6962533
ISSUE:
When structuredTypeKey: openshift.labels.myLabel is used in CLF openshift.labels.myLabel is created and openshift.sequence is not created
~~~
"_index" : "app-000001",
....
....
"openshift" : {
"labels" :
~~~
Please see the attached images of CLF and Kibana where openshift.sequence is missing.