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
State Timeline event widths prematurely end #76869
Comments
Thanks for the quick reply. Omitting null values is not desired, as for example given the following data: 06:00:00: "State 1" I would expect to see three blocks shown with a 30 minute gap between each? If we omit null values / empty strings then this just has the effect of artificially expanding the first event through the 'no state' period so that it ends at the start time of the next event, rather than 30 mins before. A temporary workaround is to map null value to "." as below: However this isn't ideal, as a "." is still shown between events and a tooltip is available. Also as mentioned it renders as expected when only showing one series, the issue appears when showing another series as it then terminates events in the first series when there is a change in any other. |
coming back to this, it will be fixed by #84130 🎉 |
@leeoniya fantastic, thanks for the feedback and the fix 👍 |
What happened?
When displaying multiple series the events in the previous series are terminated at the start time of the next series. For example:
The event should start at 06:16 and end at 08:21, however in the visualisation view it ends at 06:19 (the same time as an event starts in the next series):
If you disable all other series then the data is rendered as expected:
What did you expect to happen?
Each series should be treated individually and remain independent from events in other series.
Did this work before?
N/A
How do we reproduce it?
Is the bug inside a dashboard panel?
Panel debug snapshot dashboard
Environment (with versions)?
Grafana: 10.0.2 (also tested with latest)
OS:
Browser: Chrome
Grafana platform?
None
Datasource(s)?
InfluxDB
The text was updated successfully, but these errors were encountered: