[ 
https://issues.apache.org/jira/browse/RANGER-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akash Gupta reassigned RANGER-5704:
-----------------------------------

    Assignee: Akash Gupta

> Ranger Admin Dashboard Charts are displaying dates based on UTC Epoch instead 
> of Local Time
> -------------------------------------------------------------------------------------------
>
>                 Key: RANGER-5704
>                 URL: https://issues.apache.org/jira/browse/RANGER-5704
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 2.9.0
>            Reporter: Akash Gupta
>            Assignee: Akash Gupta
>            Priority: Major
>
> h3. *Summary*
> The charts in the Ranger Admin Dashboard are rendering data points using the 
> raw UTC/Epoch time from the backend database. This leads to a mismatch 
> between the chart visualisation and the actual local time of the user.
> ----
> h3. *Steps to Reproduce*
>  # Log in to the Ranger Admin from a machine set to {*}PDT (UTC-7){*}.
>  # Perform a policy action (e.g., Create a Policy) at 8:00 PM local time in 
> Ranger Admin.
>  # Observe the Policy Actions/Change count chart.
>  # Result{*}:{*} The action is logged on the chart for the wrong date i.e. a 
> day earlier (relative to the user's system clock).
> h3. *Expected Behaviour*
> The chart should dynamically convert the database Epoch time to the User’s 
> Local Timezone (browser-based) so that the chart date reflects the actual day 
> the action occurred in the user's current location.
> h3. *Current Behaviour*
> Dashboard chart data is rendered according to UTC/Epoch time. This causes 
> significant confusion for users in time zones far from UTC:
>  * *PDT Users:* Often see policy actions from "today" appearing on the 
> previous date.
> h3. *Technical Notes*
>  * Source Data: Database stores timestamps in Epoch/UTC.
>  * Affected Component: All the charts related data displayed on Ranger Admin 
> dashboard.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to