Feature #4401

Chart dates should use same timezone as server

Added by Igal Koshevoy almost 2 years ago. Updated about 1 year ago.

Status:Closed Start date:07/30/2010
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:1.1.0
Keywords:roadmapped Affected URL:
Branch: Affected Dashboard version:
Votes: 0

Description

Currently, the charts displayed using the browser’s timezone, while the rest of the dates are rendered using the server’s timezone — which usually aren’t the same.

Related issues

related to Puppet Dashboard - Feature #4606: Application should use browser's timezone for displaying ... Accepted 08/24/2010
related to Puppet Dashboard - Bug #4605: Application should use the timezone and format set in a s... Closed 08/24/2010
related to Puppet Dashboard - Bug #4403: Run-failure chart's counts are different than the actual ... Closed 07/30/2010
related to Puppet Dashboard - Feature #5187: Display Improvements Closed 11/02/2010
related to Puppet Dashboard - Bug #4794: Dates and times in views should be shown in current Rails... Closed 09/17/2010
duplicated by Puppet Dashboard - Bug #3322: Graphs do not obey config.time_zone setting Duplicate 03/03/2010

History

#1
Updated by Jeff McCune almost 2 years ago

Updated information:

In version 1.0.3, the charts displayed appear to be in UTC or GMT or something entirely different. I’m running dashboard through webrick on a CentOS 5.5 system set in the same timezone as my mac workstation and the times associated with the reports appear way off.

I’ll attach screen captures if you’d like.

-Jeff

#2
Updated by Igal Koshevoy almost 2 years ago

  • Target version changed from 61 to 1.0.5

Issue #4403 and its minimalist solution affect this.

#3
Updated by Nick Lewis over 1 year ago

The charts appear to already be rendering with the timezone set in the server’s config/environment.rb. Is this the desired behavior, or should it be the actual timezone in which the server is located?

#4
Updated by Nick Lewis over 1 year ago

  • Status changed from Accepted to Needs More Information
  • Assignee set to Igal Koshevoy

#5
Updated by Oliver Hookins over 1 year ago

I notice that the list of recent reports on the frontpage, and in recently failed nodes / no longer reporting nodes are in UTC which is in environment.rb. Then, if I select a single node, all of the reports in the list are displayed also in UTC, but if I drill down into a single reports for this node, the log line timestamps are in CEST. I can’t say if this is coming from my browser, the server’s timezone or somewhere else though.

#6
Updated by Igal Koshevoy over 1 year ago

  • Assignee deleted (Igal Koshevoy)

Oliver: Thank you for reporting this problem and giving us an example of the location where we could find the wrong value. I’ve created bug #4794 and pushed a fix for it.

#7
Updated by Nigel Kersten over 1 year ago

  • Keywords set to roadmapped

#8
Updated by Jesse Wolfe over 1 year ago

  • Status changed from Needs More Information to Closed

Merged into next in commit:5acb5b260ddbd7d16edcae1fde6eff5f50a7b111

Merged into master in commit:4c484f2a6a6f627d4b8926404ca179ed373cb9cc as part of Iteration-2010-11-17

#9
Updated by James Turnbull about 1 year ago

  • Target version changed from 1.0.5 to 1.1.0

Also available in: Atom PDF