Repository navigation
Rename monitoring feature to CRM Monitor - #2
Merged
Merged
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.
The monitoring feature now uses CRM Monitor across HubSpot and Salesforce screens, the Operations Inbox, Slack notifications, source files, configuration and documentation. Its page is
/app/monitor, API is/api/control-tower/monitor, and runner command and Compose profile aremonitor.Existing installations upgrade their SQLite tables in place, retaining account settings, cursors, findings and repair holds. Pending Slack messages receive the new links and generated titles without changing delivery state or identity. Retired storage identifiers remain only in the upgrade helper and regression fixtures. Stop the previous runner and update configuration/bookmarks before restarting; see
docs/monitor.md.Validation: 655 tests across 53 files, TypeScript, lint, application/public builds, Compose configuration, runner help, secret scan and diff checks passed. Mocked browser checks cover both providers, desktop/mobile, the Inbox and report downloads with zero external requests. Five migration tests cover preservation, rollback and partial/conflicting schemas. No CRM writes, Slack messages, native probes or application deployment occurred.