Consolidate entity-free observability for 1.9 - #4302
Open
zqr10159 wants to merge 2 commits into
Open
Conversation
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.
Summary
hertzbeat-observabilityand move entity-free signal storage/query ownership into the warehouse layerMotivation
The 1.9 release is the transition release before the 2.0 entity model. It needs the mature three-signal ingestion and query boundary without introducing the entity layer. This change consolidates those capabilities under observability and warehouse ownership while preserving the 1.9 operator routes and resource-based filtering model.
Validation
./mvnw -pl hertzbeat-startup -am -DskipTests package: all 24 reactor modules succeeded and produced the 1.9 startup jarnpm run package: production build succeededgit diff --checkpassedUpgrade impact
hertzbeat-logtohertzbeat-observabilityhertzbeat-warehouseAI assistance: used for draft implementation and test iteration.
Human validation: ran the commands and real HTTP/gRPC/Greptime/browser checks listed above; all required checks passed.
Risk notes: the live local smoke used the cached GreptimeDB 1.0.1 image while repository Compose targets 1.1.3, so CI/E2E remains the final pinned-version proof. The Angular production build retains the repository's existing 3.12 MB initial-bundle budget warning. Existing unrelated full-catalog locale drift was not expanded; all keys added here are present in all five touched catalogs.