-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues when selecting Date + Hour in Time Dimension #121
Comments
I actually cannot provide that much - worked on friday, broken today again... is there a way to fetch the raw result returned by the google api to diagnose that? |
change log.level=debug grafana.ini file https://github.com/grafana/grafana/blob/main/conf/defaults.ini#L1055 https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#log |
@aa-matthias When the amount of data increases, the rest of the values are added to the field (other). This operates independently of the maximum row number of api requests. Let me look more closely at the ga api policy. In the above case, the field of the date hour must be parsed by time, but it occurs because the other cannot be time parsed due to other changes. |
thanks - sorry, i kept having this topic in my backlog but missed to reply so far. |
Describe the bug
When selecting Date + Hour in Time Dimension queries stop showing. The error i get via Grafana Log is:
logger=plugin.blackcowmoo-googleanalytics-datasource t=2024-09-12T16:31:29.306872536+02:00 level=error msg=timeConverter error="parsing time "(other)00000" as "200601021504": cannot parse "(other)00000" as "2006""
logger=plugin.blackcowmoo-googleanalytics-datasource t=2024-09-12T16:31:29.306909005+02:00 level=error msg="parseRow: Failed to parse time dimension" error="parsing time "(other)00000" as "200601021504": cannot parse "(other)00000" as "2006""
Grafana Version & Plugin Version
11.2.0 with 0.3.0
To Reproduce
Steps to reproduce the behavior:
Query as shown in the Screenshot below - Data stops loading (changing Time Dimension to something else works)
Expected behavior
Graph should be shown as usual.
Screenshots

Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: