You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello Grafana guys 馃憢馃徏,
We used the Grafana helm chart and noticed that timestamp representation differs between the grafana-sc-dashboard and the grafana containers. When you have json logging enabled then your logs probably look like this:
# grafana-sc-dashboard
{"time": "2024-04-24T09:09:26.606514+00:00", "taskName": null, "msg": "Found a folder override annotation, placing the metrics-dashboard-15.1.0-dev1 in: /tmp/dashboards/dev1", "level": "INFO"}
# grafana
{"level":"info","logger":"settings","msg":"Config overridden from Environment variable","t":"2024-04-23T06:59:14.858660879Z","var":"GF_PATHS_LOGS=/var/log/grafana"}
You have a t field in one container and for the next one, time. Log parsing is unnecessarily complicated for some log collectors like FluentD when you count with time (default key name for the time field), but you have t 馃槥.
Can you please consider to rename that field t to time 馃檹馃徏?
The text was updated successfully, but these errors were encountered:
Hello Grafana guys 馃憢馃徏,
We used the Grafana helm chart and noticed that timestamp representation differs between the
grafana-sc-dashboard
and thegrafana
containers. When you havejson
logging enabled then your logs probably look like this:You have a
t
field in one container and for the next one,time
. Log parsing is unnecessarily complicated for some log collectors like FluentD when you count withtime
(default key name for the time field), but you havet
馃槥.Can you please consider to rename that field
t
totime
馃檹馃徏?The text was updated successfully, but these errors were encountered: