Skip to content
This repository has been archived by the owner on Jan 7, 2020. It is now read-only.

Wrong client timestamp #456

Closed
bovy89 opened this issue Mar 3, 2016 · 3 comments
Closed

Wrong client timestamp #456

bovy89 opened this issue Mar 3, 2016 · 3 comments
Assignees
Labels
Milestone

Comments

@bovy89
Copy link

bovy89 commented Mar 3, 2016

Hi,
the timestamp retrieved from sensu api, seems to be not correct.

If i interrogate sensu-api directly with my browser, i obtain something like 1457037509 as timestamp.

I inspected the response in Uchiwa with firebug and i obtain something like 1.457035675e+09.

The value 1457037509 is correct and the label indicates "a few second ago"; the value 1.457035675e+09 instead indicates "25 minute ago".

Sensu version: 0.22.0

Uchiwa version: 0.14.2

@dmichelotto
Copy link

+1

@kaos
Copy link

kaos commented Apr 9, 2016

Is it correct on the /clients page, but not on the detail page for the client?
If so, you've hit a bug which I've addressed in PR sensu/uchiwa-web#93: sensu/uchiwa-web@da1fb63

And it's not the raw timestamp value that is wrong.. it is how it is presented, in that case.

@palourde palourde added this to the 0.15.0 milestone May 23, 2016
@palourde palourde self-assigned this May 23, 2016
@bovy89
Copy link
Author

bovy89 commented Jun 30, 2016

This bug still exists:

Release 0.13 (correct)
013_img1
013_img2

Release > 0.13 (bugged)
016_img1
016_img2

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants