-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Timeseries value magnitudes are greatly affected by temporal resolution #71827
Copy link
Copy link
Open
Labels
A-sql-console-timeseriesSQL Observability issues related to console timeseries metrics and viewsSQL Observability issues related to console timeseries metrics and viewsC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-3-ux-surpriseIssue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.T-observability
Description
This video from v21.1.10 shows a problem where the magnitude of the metric changes dramatically when you increase the temporal resolution of the chart. At a one-day timescale, the number of open transactions only shows ~800. When you zoom in, however, we see that there are more than 5,600 connections open.
Damned.Lies.mov
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-sql-console-timeseriesSQL Observability issues related to console timeseries metrics and viewsSQL Observability issues related to console timeseries metrics and viewsC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-3-ux-surpriseIssue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.T-observability