Repository navigation
Conversation
Both stat panels are full width and five grid rows tall, laid out `orientation: horizontal` -- which in Grafana means each reading runs horizontally and they stack vertically. So five readings (seven on the survey board) shared about 150px of height, Grafana auto-shrank the text to fit, and the one number a reader actually came for rendered at roughly 10px while 1,900px of panel width sat empty. Switched to `vertical`, which lays the readings out side by side: five columns of ~400px on the positioning board, seven of ~285px on the survey board, each with the full panel height. The widest value is the survey board's `2026-08-01`, which fits a 285px column at this size. `text.valueSize` is set explicitly rather than left to auto-fit so the size is a committed property of the dashboard instead of a function of how many fields the SELECT happens to return -- adding a column would otherwise silently shrink every number again. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both stat panels are full width and 5 grid rows tall with
orientation: "horizontal"— which in Grafana means each reading runshorizontally and they stack vertically. So 5 readings (7 on the survey
board) shared ~150px of height, Grafana auto-shrank text to fit, and the one
number a reader came for rendered at roughly 10px while ~1,900px of panel width
sat empty.
verticallays them out side by side instead: 5 columns of ~400px here, 7 of~285px on the survey board, each getting the full panel height. The widest value
is the survey board's
2026-08-01date, which fits a 285px column at this size.text.valueSizeis set explicitly rather than left to auto-fit, so the size is acommitted property of the dashboard instead of a function of how many fields the
SELECT returns — adding a column would otherwise silently shrink every number
again, which is the same class of hand-coupling as the
decimals: 0overridesbeing keyed on SQL alias strings.
Diff is 6 lines across the two dashboards. 371 tests green; nothing in
tests/test_grafana.pyasserts on panel options, so the causality andarchive-table lints are untouched.
🤖 Generated with Claude Code