TSVB users are confused by the "Last value" mode because the order of operations is not clear. For example, imagine that you are looking at this table:
This table is not showing the complete data, but there's no indicator to users why this is happening. This is happening so frequently that it's been added to the first question in the TSVB frequently asked questions.
There are two main pieces of information missing:
- What time period is being displayed?
- Can we compare the current slice of time to any other slices of time?
I propose that we add two indicators to all the "last value" mode charts:
- An indication of the actual time range, like "Feb 2, 2021 4:55 AM to Feb 2, 2021 5:00 AM"
- An indicator that the data is fetched using "last value mode" as opposed to entire time range
This issue is related to an actual bug in TSVB, but is harder to fix because it changes some of the assumptions about how TSVB works.
TSVB users are confused by the "Last value" mode because the order of operations is not clear. For example, imagine that you are looking at this table:
This table is not showing the complete data, but there's no indicator to users why this is happening. This is happening so frequently that it's been added to the first question in the TSVB frequently asked questions.
There are two main pieces of information missing:
I propose that we add two indicators to all the "last value" mode charts:
This issue is related to an actual bug in TSVB, but is harder to fix because it changes some of the assumptions about how TSVB works.