Discover: Field [timestamp] of type [long] does not support custom time zones

[evertvh]

I followed the instructions to create the dashboard, and after fixing the issue described here, I got the dashboard to work.

However, I still encounter this error on the Kibana Discover tab, and it is not possible to search any logs via Discover.

Discover: Field [timestamp] of type [long] does not support custom time zones Error: Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Field [timestamp] of type [long] does not support custom time zones"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"awswaf-2020-09-22","node":"U_7wNOMGQnia50Brp9KZDQ","reason":{"type":"illegal_argument_exception","reason":"Field [timestamp] of type [long] does not support custom time zones"}}],"caused_by":{"type":"illegal_argument_exception","reason":"Field [timestamp] of type [long] does not support custom time zones","caused_by":{"type":"illegal_argument_exception","reason":"Field [timestamp] of type [long] does not support custom time zones"}}},"status":400} KbnError@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/bundles/commons.bundle.js:1:7604 RequestFailure@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/bundles/commons.bundle.js:1:8108 callResponseHandlers/<@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/bundles/commons.bundle.js:1:1901189 Promise.try@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/bundles/commons.bundle.js:1:535719 Promise.map/<@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/bundles/commons.bundle.js:1:535085 Promise.map@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/bundles/commons.bundle.js:1:535046 callResponseHandlers@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/bundles/commons.bundle.js:1:1900201 fetchSearchResults/<@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/bundles/commons.bundle.js:1:1882354 processQueue@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:199687 scheduleProcessQueue/<@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:200662 $digest@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:210414 $evalAsync/<@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:212944 completeOutstandingRequest@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:64425 Browser/self.defer/timeoutId<@https://search-waf-dashboards-idofdashboard.eu-central-1.es.amazonaws.com/_plugin/kibana/built_assets/dlls/vendors.bundle.dll.js:316:67293

If I check the actual field type for 'timestamp' via the mapping API, it is indeed set to 'long':

When I check the Index Pattern via the Management tab, I see that the field type of timestamp is set to Date though:

How can I solve this error? Or how can I get the log search function to work?

[jracz18]

I have the same issue, haven't been able to figure it out

[JohnD87]

Same issue here.

[Mudpuppy12]

Same

[Mudpuppy12]

I deleted the index, then pushed more data into it and it seemed to fix the the issue

[mrghar]

I noticed that there's a message in Kibana/Management/Advanced Settings for the Time Warning:

'Time pattern warning: When an index pattern is using the now unsupported "time pattern" format, a warning will be displayed once per session that is using this pattern. Set this to false to disable that warning.'

[Galal-Eltfawy]

refreshing the index would solve it.

[ne1000]

@Galal-Eltfawy Yes, I refreshed it, but there are new issue，as bleow Discover: "field" is a required parameter