Adding a top-level timestamp into nodes stats response?


(Lukáš Vlček) #1

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


(Shay Banon) #2

Make sense: https://github.com/elasticsearch/elasticsearch/issues/1851.

On Wed, Apr 11, 2012 at 11:47 AM, Lukáš Vlček 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


(Lukáš Vlček) #3

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 wrote:

Make sense: https://github.com/elasticsearch/elasticsearch/issues/1851.

On Wed, Apr 11, 2012 at 11:47 AM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

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


(Shay Banon) #4

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 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 wrote:

Make sense: https://github.com/elasticsearch/elasticsearch/issues/1851.

On Wed, Apr 11, 2012 at 11:47 AM, Lukáš Vlček lukas.vlcek@gmail.comwrote:

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


(system) #5