# LogsUI in kibana 7.4.0 getting error when trying to look at the logs with date\_nanos
**URL:** https://discuss.elastic.co/t/logsui-in-kibana-7-4-0-getting-error-when-trying-to-look-at-the-logs-with-date-nanos/204335
**Category:** Logs
**Created:** [October 20, 2019, 6:54am UTC](https://discuss.elastic.co/t/logsui-in-kibana-7-4-0-getting-error-when-trying-to-look-at-the-logs-with-date-nanos/204335 "2019-10-20T06:54:07Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Alex-St](https://discuss.elastic.co/u/Alex-St)
#### Post date: [October 20, 2019, 6:54am UTC](https://discuss.elastic.co/t/logsui-in-kibana-7-4-0-getting-error-when-trying-to-look-at-the-logs-with-date-nanos/204335/1 "2019-10-20T06:54:07Z")
open logs UI - configure to use SourceTime which is in date\_nanos instead of @timestamp field, logsUI tries to load data for several seconds, then displays graphics on the left side (timeline), and briefly shows the logs, but almost immediately causes the following error:
Invariant Violation: Minified React error #185; visit [https://reactjs.org/docs/error-decoder.html?invariant=185](https://reactjs.org/docs/error-decoder.html?invariant=185) for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at ba ([http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:200:315](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:200:315))
at x ([http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:200:584](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:200:584))
at qf ([http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:200:96685](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:200:96685))
at Object.enqueueSetState ([http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:200:48105](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:200:48105))
at DatePicker.E.setState ([http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:192:1610](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:192:1610))
at DatePicker.componentDidUpdate ([http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:184:64661](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:184:64661))
at Vh ([http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:200:85102](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:200:85102))
at Zh ([http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:200:86620](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:200:86620))
at [http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:200:99742](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:200:99742)
at Object.exports.unstable\_runWithPriority ([http://somehost:5601/built\_assets/dlls/vendors.bundle.dll.js:151:3314](http://somehost:5601/built_assets/dlls/vendors.bundle.dll.js:151:3314))
---
### Author:  [@weltenwort](https://discuss.elastic.co/u/weltenwort)
#### Post date: [October 21, 2019, 11:33am UTC](https://discuss.elastic.co/t/logsui-in-kibana-7-4-0-getting-error-when-trying-to-look-at-the-logs-with-date-nanos/204335/2 "2019-10-21T11:33:32Z")
Hi @Alex-St,
thanks for pointing that out. The Logs UI currently requires the documents to adhere to [ECS](https://www.elastic.co/guide/en/ecs/current/ecs-base.html), which specifies the `@timestamp` field to be a `date`. I'll investigate whether supporting `date_nano` would be feasible.
(From the stack trace it looks like the datepicker causes the failure.)
---
### Author:  [@Alex-St](https://discuss.elastic.co/u/Alex-St)
#### Post date: [October 23, 2019, 8:54pm UTC](https://discuss.elastic.co/t/logsui-in-kibana-7-4-0-getting-error-when-trying-to-look-at-the-logs-with-date-nanos/204335/3 "2019-10-23T20:54:54Z")
I see. I like the idea of ECS and will put it on the roadmap. However, I am not convinced that if I switch to @timestamp now and keep date\_nanos format will fix LogsUI for me. It look like the LogsUI allows user to select a different field as input and is trying to display something on the time graph, it fails a little bit after that. I am thinking that this is related to the date\_nanos which is relatively new feature and still not very stable.
---
### Author:  [@weltenwort](https://discuss.elastic.co/u/weltenwort)
#### Post date: [October 23, 2019, 9:55pm UTC](https://discuss.elastic.co/t/logsui-in-kibana-7-4-0-getting-error-when-trying-to-look-at-the-logs-with-date-nanos/204335/4 "2019-10-23T21:55:25Z")
Indeed, the `date_nanos` type is not yet universally supported throughout the stack. If you already ingest your data in nanosecond resolution I would recommend to keep doing that in a dedicated field and duplicate the value with a millisecond resolution in the `@timestamp` field. That way you might be able to reindex or alias historical data more easily once the high-resolution timestamp is supported everywhere.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 20, 2019, 9:55pm UTC](https://discuss.elastic.co/t/logsui-in-kibana-7-4-0-getting-error-when-trying-to-look-at-the-logs-with-date-nanos/204335/5 "2019-11-20T21:55:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.