Repository navigation
fix(db): quiet routine timing logs and prepare 0.2.1 - #58
Merged
Merged
Conversation
Benchmark comparisonThreshold: ±25% (informational, does not block merge)
|
Benchmark comparisonThreshold: ±25% (informational, does not block merge)
|
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.
Routine
db.findand other successful operation timings currently emit at INFO, flooding application logs when observability is enabled. Emit these timings at DEBUG so applications can opt into detailed telemetry without losing important warnings.Slow operations retain WARNING. Fast failed operations now also use WARNING with a
FAILEDprefix, preserving failure visibility when routine timings are filtered. Structured fields, slow-query thresholds, exception propagation, metrics, and operation counters remain unchanged. Update the observability guide and technical specification, and record the fix in the 0.2.1 changelog. Bump the single-source package version to 0.2.1.Validation:
get/findcalls with metrics intact, DEBUG structured fields, slow-query warnings, failure warnings and propagated exceptions, and residual-scan telemetry.Applications that collect routine operation timing logs must enable DEBUG for
jvspatial.db.observableand their handler. The version bump prepares 0.2.1; merging to main triggers the existing release workflow. Publication has not yet been verified.