# Timelion metrics using nested objects **URL:** \ **Category:** Kibana\ **Created:** [June 13, 2016, 7:42pm UTC](https://discuss.elastic.co/t/timelion-metrics-using-nested-objects/52655 "2016-06-13T19:42:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![esds2000](https://avatars.discourse-cdn.com/v4/letter/e/858c86/32.png) [@esds2000](https://discuss.elastic.co/u/esds2000)\ **Post date:** [June 13, 2016, 7:42pm UTC](https://discuss.elastic.co/t/timelion-metrics-using-nested-objects/52655/1 "2016-06-13T19:42:13Z")
Trying to figure our the correct syntax to reference nested fields in timelion. For example, using the Marvel index, how would you plot node\_stats.indices.docs.count? This expression, .es(index='.marvel-es-1-\*',metric='avg:node\_stats.indices.docs.count'), does not plot any data. The field type is a number. ---
**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\ **Post date:** [June 14, 2016, 9:34pm UTC](https://discuss.elastic.co/t/timelion-metrics-using-nested-objects/52655/2 "2016-06-14T21:34:41Z")
That looks right, thought I'm not well versed in Timelion so there may be a slight syntax issue I'm not seeing. Before I go digging, are you sure you have access to the index? You can check by hitting the cluster with a `_search`, like: `http://hostname:9200/.marvel-es-1-*/_search` Assuming that your cluster accessible from `hostname` on port `9200`. If you get results back, then it's not an access problem. ---
**Author:** ![esds2000](https://avatars.discourse-cdn.com/v4/letter/e/858c86/32.png) [@esds2000](https://discuss.elastic.co/u/esds2000)\ **Post date:** [June 14, 2016, 10:04pm UTC](https://discuss.elastic.co/t/timelion-metrics-using-nested-objects/52655/3 "2016-06-14T22:04:40Z")
It does have access, \_search returns all the data. Also, I can visualize the data with standard kibana graphs. I've used timelion for some of our other indices and the same expressions I have tried work for fields that are not nested, so that's the only thing that seems different. ---
**Author:** ![Kurt\_S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kurt_s/32/17755_2.png) [@Kurt\_S](https://discuss.elastic.co/u/Kurt_S)\ **Post date:** [January 5, 2017, 4:46pm UTC](https://discuss.elastic.co/t/timelion-metrics-using-nested-objects/52655/4 "2017-01-05T16:46:56Z")
I have this same problem with the .marvel-es-\* indices. I can get nested fields out of other indices but it seems to me that Timelion can't cope with the dot in ".marvel-es-\*" ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [January 20, 2017, 7:35pm UTC](https://discuss.elastic.co/t/timelion-metrics-using-nested-objects/52655/5 "2017-01-20T19:35:12Z")
Kurt, I could reproduce that as well, and it seems to be a bug. I filed [https://github.com/elastic/kibana/issues/9983](https://github.com/elastic/kibana/issues/9983) ---
**Author:** ![Kurt\_S](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kurt_s/32/17755_2.png) [@Kurt\_S](https://discuss.elastic.co/u/Kurt_S)\ **Post date:** [January 23, 2017, 1:15pm UTC](https://discuss.elastic.co/t/timelion-metrics-using-nested-objects/52655/6 "2017-01-23T13:15:27Z")
Hi Tim, I have the solution now (got it from our support). Marvel stores it's timestamp in the field "timestamp" instead of "@timestamp". You have to add in the Timelion query "timefield=timestamp" and it should work. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:33pm UTC](https://discuss.elastic.co/t/timelion-metrics-using-nested-objects/52655/7 "2017-07-06T13:33:21Z")