Update telemetry docs to reflect Rudder removal#9072
Conversation
Remove all references to pdat.matterlytics.com and RudderStack, which were removed in Sep 2025. Drop the now-defunct "Deployment and server configuration data", "Event data", and "Playbooks telemetry" sections. Update the EnableDiagnostics setting description to accurately reflect that it now only gates Sentry error reporting. Remove the dead VerboseDiagnostics config setting entry, which has no server implementation. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Newest code from mattermost has been published to preview environment for Git SHA 1988a60 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe telemetry docs now describe security update data without the CloudFront location item, and error reporting now states that server errors and panics are sent to Mattermost’s Sentry endpoint. The matching environment configuration entry was updated to use the same wording. ChangesTelemetry and diagnostics documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@source/administration-guide/configure/environment-configuration-settings.rst`:
- Around line 3332-3340: The documentation table for
LogSettings.EnableDiagnostics shows an incorrect default entry; update the
config.json setting row so it reflects the actual boolean default value rather
than an empty string. Keep the existing table structure in
environment-configuration-settings.rst and align the config.json, system config
path, and MM_LOGSETTINGS_ENABLEDIAGNOSTICS entries with the true/false
descriptions below.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 073e9d9c-a2b7-48f6-bdce-91ef44d34b3a
📒 Files selected for processing (2)
source/administration-guide/configure/environment-configuration-settings.rstsource/administration-guide/manage/telemetry.rst
Co-authored-by: Cursor <cursoragent@cursor.com>
|
Newest code from mattermost has been published to preview environment for Git SHA b1bd0e6 |
|
Newest code from mattermost has been published to preview environment for Git SHA ebc4e22 |
|
Newest code from mattermost has been published to preview environment for Git SHA cae2dbd |
Summary
pdat.matterlytics.comand RudderStack, which were fully removed from the server in MM-64486 (Sep 2025).EnableDiagnosticssetting description to accurately reflect that it now only gates Sentry error/crash reporting.VerboseDiagnosticsconfig setting entry (LogSettings.VerboseDiagnostics/MM_LOGSETTINGS_VERBOSEDIAGNOSTICS), which has no implementation in the server.Release Note
Made with Cursor