Digest expansion: ten new toggleable email report sections - #302
Merged
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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.
Expands the daily/weekly digest email so every LogTide vertical can report into it. Ten new sections, all disabled by default and individually toggleable per organization; the five original sections are now toggleable too (enabled by default), so existing digests are unchanged until someone opts in.
What's included
digest_configsgains asectionsJSONB column (migration 057, NULL = defaults). The shared catalog (DIGEST_SECTION_KEYS,DIGEST_SECTION_DEFAULTS,mergeDigestSectionsin@logtide/shared) drives the backend Zod schema, the generator gating and the settings UI, so the three cannot drift. Stored values are minimal partials (the UI sends only keys that differ from defaults); the dispatch cron enqueues the merged record in the job payload, so the generator adds no config query and pre-deploy queued jobs fall back to defaults.duration_ms,end_time,service_name,operation_name); previously any sort other thanstart_timewas silently ignored, which would have made "slowest spans" render most-recent spans on Mongo.Tenancy and safety
alert_historythrough thealert_rulesjoin (it has no org column),monitor_resultson both sides of themonitorsjoin (no FK exists on the hypertable).check:tenant-scopingpasses (324 sites).Verification