Repository navigation
spec: the TurboStats database section, for dbhealth - #441
Merged
Merged
Conversation
One new section in the v1 bundle, reported by the new dbhealth binary and rendered by a new kind of instance in control. Postgres first; the config and the section shape are the same for every kind.
…y; one instance per replica, grouped by cluster
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Design for review. Adds one section,
database, to the v1 TurboStats bundle: the probe (is it serving), resources (connections, size), per-table freshness and row counts, and replication. Reported by a new binary,turbolytics/dbhealth; rendered by a new kind of instance in control, beside pipelines.Decisions to check:
count(*)by choice on its own slow interval;Spec:
docs/superpowers/specs/2026-10-05-turbostats-database-section-design.md.