Closed sairamvla closed 7 years ago
I have not been able to reproduce this, where I pointed the swimlane visualization at an index pattern in a daily format 'test-2017.06.09'.
What steps did you take when changing the index pattern? Were you creating different index patterns in Kibana, or did you have the data going into a different named elasticsearch index?
Searching on https://discuss.elastic.co I wonder if this is caused by a mapping issue, as reported on https://discuss.elastic.co/t/5-1-1-custom-format-isnt-supported/70125 ?
Thanks @peteharverson. Sorry for any trouble. This is due to my elastic search template field mismatch. Swimlane works as expected.
I installed Swimlane plugin for Kibana 5.4.0. When I changed the elastic search index to daily partition like test-2017-06-28, Swimlane visualizations in Kibana are throwing this exception:
Error: [unsupported_operation_exception] custom format isn't supported at respond (http://mdc2pr149:8080/bundles/kibana.bundle.js?v=15063:12:2730) at checkRespForFailure (http://mdc2pr149:8080/bundles/kibana.bundle.js?v=15063:12:1959) at http://mdc2pr149:8080/bundles/kibana.bundle.js?v=15063:1:9902 at processQueue (http://mdc2pr149:8080/bundles/commons.bundle.js?v=15063:38:23621) at http://mdc2pr149:8080/bundles/commons.bundle.js?v=15063:38:23888 at Scope.$eval (http://mdc2pr149:8080/bundles/commons.bundle.js?v=15063:39:4619) at Scope.$digest (http://mdc2pr149:8080/bundles/commons.bundle.js?v=15063:39:2359) at Scope.$apply (http://mdc2pr149:8080/bundles/commons.bundle.js?v=15063:39:5037) at done (http://mdc2pr149:8080/bundles/commons.bundle.js?v=15063:37:25027) at completeRequest (http://mdc2pr149:8080/bundles/commons.bundle.js?v=15063:37:28702) at XMLHttpRequest.xhr.onload (http://mdc2pr149:8080/bundles/commons.bundle.js?v=15063:37:29634)
When I remove the timestamp from index name, it works. But I need daily partitions to purge the indexes.
Any ideas why this is failing?
Thanks in advance