# Adding a top-level timestamp into nodes stats response? **URL:** \ **Category:** Elasticsearch\ **Created:** [April 11, 2012, 8:47am UTC](https://discuss.elastic.co/t/adding-a-top-level-timestamp-into-nodes-stats-response/7290 "2012-04-11T08:47:57Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\ **Post date:** [April 11, 2012, 8:47am UTC](https://discuss.elastic.co/t/adding-a-top-level-timestamp-into-nodes-stats-response/7290/1 "2012-04-11T08:47:57Z")
Hi, I think it would be useful to have an explicit top-level timestamp information for each nodes stats response. By timestamp I mean information about time a particular response is relevant to. I know there are several timestamps nested inside the response but they are relevant to respective sub/parts of the response and not every sup/part has its own timestamp (roughly half of them do not have it). This can make it hard if you want to sort values correctly because you should not rely either on AJAX response arrival time or AJAX request time. What we really need is the time when this request was processed on the server side. Or am I missing something here? This is probably not a big problem in general but it can hit you when you really try to use and display response data precisely (like in bigdesk). Regards, Lukas ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 11, 2012, 9:20am UTC](https://discuss.elastic.co/t/adding-a-top-level-timestamp-into-nodes-stats-response/7290/2 "2012-04-11T09:20:37Z")
Make sense: [Node Stats: Add timestamp per node stats element · Issue #1851 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1851). On Wed, Apr 11, 2012 at 11:47 AM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote: > Hi, > > I think it would be useful to have an explicit top-level timestamp > information for each nodes stats response. By timestamp I mean information > about time a particular response is relevant to. I know there are several > timestamps nested inside the response but they are relevant to respective > sub/parts of the response and not every sup/part has its own timestamp > (roughly half of them do not have it). This can make it hard if you want to > sort values correctly because you should not rely either on AJAX response > arrival time or AJAX request time. What we really need is the time when > this request was processed on the server side. Or am I missing something > here? > > This is probably not a big problem in general but it can hit you when you > really try to use and display response data precisely (like in bigdesk). > > Regards, > Lukas ---
**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\ **Post date:** [April 11, 2012, 9:24am UTC](https://discuss.elastic.co/t/adding-a-top-level-timestamp-into-nodes-stats-response/7290/3 "2012-04-11T09:24:16Z")
Thanks. May be it would be needed to add similar timestamp to other stats-like responses (may be indices stats will be next?) Lukas On Wed, Apr 11, 2012 at 11:20 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > Make sense: [Node Stats: Add timestamp per node stats element · Issue #1851 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1851). > > On Wed, Apr 11, 2012 at 11:47 AM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote: > > > Hi, > > > > I think it would be useful to have an explicit top-level timestamp > > information for each nodes stats response. By timestamp I mean information > > about time a particular response is relevant to. I know there are several > > timestamps nested inside the response but they are relevant to respective > > sub/parts of the response and not every sup/part has its own timestamp > > (roughly half of them do not have it). This can make it hard if you want to > > sort values correctly because you should not rely either on AJAX response > > arrival time or AJAX request time. What we really need is the time when > > this request was processed on the server side. Or am I missing something > > here? > > > > This is probably not a big problem in general but it can hit you when you > > really try to use and display response data precisely (like in bigdesk). > > > > Regards, > > Lukas ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [April 11, 2012, 9:35am UTC](https://discuss.elastic.co/t/adding-a-top-level-timestamp-into-nodes-stats-response/7290/4 "2012-04-11T09:35:18Z")
Indices stats are a bit trickier, since they are not "node" level, so require some more thought. Shard level we can definitely add it. On Wed, Apr 11, 2012 at 12:24 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote: > Thanks. > May be it would be needed to add similar timestamp to other stats-like > responses (may be indices stats will be next?) > > Lukas > > On Wed, Apr 11, 2012 at 11:20 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > Make sense: [Node Stats: Add timestamp per node stats element · Issue #1851 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1851). > > > > On Wed, Apr 11, 2012 at 11:47 AM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com)wrote: > > > > > Hi, > > > > > > I think it would be useful to have an explicit top-level timestamp > > > information for each nodes stats response. By timestamp I mean information > > > about time a particular response is relevant to. I know there are several > > > timestamps nested inside the response but they are relevant to respective > > > sub/parts of the response and not every sup/part has its own timestamp > > > (roughly half of them do not have it). This can make it hard if you want to > > > sort values correctly because you should not rely either on AJAX response > > > arrival time or AJAX request time. What we really need is the time when > > > this request was processed on the server side. Or am I missing something > > > here? > > > > > > This is probably not a big problem in general but it can hit you when > > > you really try to use and display response data precisely (like in bigdesk). > > > > > > Regards, > > > Lukas ---
**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, 3:32am UTC](https://discuss.elastic.co/t/adding-a-top-level-timestamp-into-nodes-stats-response/7290/5 "2017-07-06T03:32:59Z")