-
Notifications
You must be signed in to change notification settings - Fork 22
Heat map time range inconsistent with data #22
Comments
Thank you for taking the time to tell me about this 🙏 I agree it does look weird. I've been trying to reproduce this without success though. Could you elaborate on what you mean by "when data stops after a certain point"? |
Marcus, thank you for responding. Let's say, for example we choose a timeline of Feb 1, 2021 - Mar 1, 2021. Let's assume that this dataset does have data starting from Feb 1, 2021. If for some reason, after Feb 7, 2021 the dataset has no data, the heat maps will only be displayed from Feb 1, 2021 - Feb 7, 2021. Currently, in the panel, the x-axis does not extend beyond Feb 7, 2021. Please see the link in "Query B" above and scroll down to the heat map. Intuitively, one would expect that even though there are no heatmaps to display (because there is no data) beyond Feb 7, 2021, the empty x-axis would extend all the way to Mar 1, 2021 because that was the specified timeline. Hope this clears things a bit. |
Thank you for clarifying! I'll try and see if I can reproduce this and get back to you |
Grafana: v7.3.3 |
This is a pretty neat plugin! Thanks for making it available.
Came across an issue when data stops after a certain point, The heat map time range seems to be inconsistent. Don't know whether this is by design but it didn't appear to be quite intuitive. The issue may be better explained by two examples:
Query A - expected results:
30 day time period; heat maps show the full 30 days.
https://portal.netsage.global/grafana/d/80IVUboZk/individual-flows-per-country?orgId=2&from=1610092800000&to=1612771199000&var-src=United%20States&var-dest=Germany
Query B - unexpected results:
30 day time period, but heat maps show only a week.
https://portal.netsage.global/grafana/d/80IVUboZk/individual-flows-per-country?orgId=2&var-src=Austria&var-dest=Philippines&from=1607438294129&to=1610030294129
Any pointers in resolving this would be greatly appreciated!
The text was updated successfully, but these errors were encountered: