Charts: [stable/prometheus-operator] Grafana dashboards timezone should not be hardcoded to UTC

Created on 14 Jul 2020 · 3Comments · Source: helm/charts

Describe the bug
Seems like https://github.com/helm/charts/pull/22900/files set the timezone on all dashboards to UTC. This is not ideal as can't be changed unless one wants to edit and save a copy of the dashboard.

Which chart: prometheus-operator

As suggested in https://github.com/coreos/prometheus-operator/issues/1807#issuecomment-417759647 it is better to se the timezone to "default" so that dashboards will use the global setting defined in preferences.

Source

acondrat

👍4

Most helpful comment

Just in case it helps this is the workaround we applied:

PODS=$(kubectl -n monitoring get cm -o json | jq -r '.items[].metadata.name | select(.|test("^prom-prometheus-operator-"))')
kubectl -n monitoring get cm $PODS -o yaml > workaround.yaml
sed -i -e 's/"timezone":.*/"timezone": "browsertime",/' workaround.yaml
kubectl -n monitoring replace -f workaround.yaml

kubectl -n monitoring delete pod/prom-grafanaXXXX

iaas365-dev on 19 Aug 2020

👍3

All 3 comments

Agreed, this is a very frustrating change!

chrishatfield86 on 22 Jul 2020

Just in case it helps this is the workaround we applied:

PODS=$(kubectl -n monitoring get cm -o json | jq -r '.items[].metadata.name | select(.|test("^prom-prometheus-operator-"))')
kubectl -n monitoring get cm $PODS -o yaml > workaround.yaml
sed -i -e 's/"timezone":.*/"timezone": "browsertime",/' workaround.yaml
kubectl -n monitoring replace -f workaround.yaml

kubectl -n monitoring delete pod/prom-grafanaXXXX

iaas365-dev on 19 Aug 2020

👍3

🚧 This chart is now deprecated.

Further development has moved to prometheus-community/helm-charts. The chart has been renamed kube-prometheus-stack to more clearly reflect that it installs the kube-prometheus project stack, within which Prometheus Operator is only one component.

If applicable, please re-open this issue there. Thanks!