Repository navigation
Add fleet history charts to the Dashboard - #79
Merged
Merged
Conversation
…into the top row The Dashboard gains a window picker (1h to 7d) with alerts raised by severity, the noisiest rules and devices, top CPU and devices by type. One read, /api/dashboard, feeds them all, through the control database and the storage interface so it behaves the same on every backend. Fabric Integrity moves from the side column into the readout row.
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
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.
The Dashboard gains a Fleet history section with a window picker (1h, 6h, 24h, 7d): alerts raised by severity, noisiest rules and devices, top CPU, and devices by type. One read,
/api/dashboard, feeds them all through the control database and the storage interface, so it behaves the same on SQLite, DuckDB and ClickHouse.Fabric Integrity moves from the side column into the top readout row.
Tested on the test server by loading the Dashboard. The new endpoint was not called directly with data; the page's empty states were the only thing seen.
The user guide's Dashboard section is updated.