SUMO-287829, SUMO-288052, SUMO-288053 - Add monitors documentation for Windows Legacy, Windows CSMA, and Host and Process Metrics apps#6887
Merged
shauryasethi-sumo merged 13 commits intoJul 20, 2026
Conversation
… Windows Legacy, Windows CSMA, and Host and Process Metrics apps
shauryasethi-sumo
requested review from
a team,
JV0812,
amee-sumo,
kimsauce and
mafsumo
as code owners
July 10, 2026 11:36
kimsauce
approved these changes
Jul 13, 2026
- Host and Process Metrics: list all 20 monitors (14 host + 6 process) with exact names from monitors.tf, remove old Method A/B alert installation instructions - Windows CSMA: use actual monitor prefix "Windows (Classic) - Security Analytics -" instead of abbreviated "Windows CSMA -" - Windows Legacy: use actual monitor prefix "Windows 7+ - 2008 (Legacy) -" instead of abbreviated "Windows Legacy -"
Dashboard titles changed from "Host Metrics - X" to "Host and Process Metrics - X" and "Process Metrics - X" to "Host and Process Metrics - Process X" to resolve name collision with other OS apps.
- Windows CSMA: "Windows - Security Analytics/Monitoring -" updated to "Windows (Classic) - Security Analytics/Monitoring -" - Windows Legacy: added full dashboard title prefix "Windows 7+ - 2008 (Legacy) -" in dashboard descriptions
…ription Aligns with the actual query which only checks ROOT, ADMIN, ADMINISTRATOR, GUEST.
- Host and Process Metrics: update descriptions to list both Warning and Critical thresholds - Windows CSMA: remove System from Default Account Activity description
MDX parser interprets < as JSX tag start. Escape as < in recover condition columns.
Change the 20 Host and Process Metrics alert descriptions from "This alert fires" to "This alert is triggered" to match the Windows monitor tables. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
amee-sumo
approved these changes
Jul 20, 2026
amee-sumo
left a comment
Collaborator
There was a problem hiding this comment.
Approving. This modernizes the Windows Legacy, Windows CSMA, and Host & Process Metrics app docs to the v2 monitor pattern — adding Create monitors sections (6 / 8 / 20 alerts), renaming dashboards, and replacing the legacy manual JSON/Terraform alert-install steps with the <CreateMonitors/> reuse.
Verified:
- Dashboard renames are fully consistent (no leftover old names); sample queries and drill-down references were updated to match.
- No duplicate headings; correct section order (Create monitors → Upgrade/Downgrade → Uninstalling); reuse imports resolve.
- No broken links — nothing else referenced the removed "Installing the Alerts" anchors.
I pushed one follow-up commit (fc44767): standardized the 20 Host & Process Metrics alert descriptions from "This alert fires" to "This alert is triggered", matching the Windows tables.
Items to confirm before merge (non-blocking):
- Shipped names: verify the renamed dashboards ("Windows (Classic) -", "Windows 7+ - 2008 (Legacy) -", "Host and Process Metrics -") and all alert names exactly match what the apps ship.
- Operator style: the tables use
<=, while most of the repo uses the spacedCount < = 0form — fine to keep, just flagging for consistency.
— via Claude Code
shauryasethi-sumo
deleted the
SUMO-287829-288052-288053-add-monitors-observability-apps
branch
July 20, 2026 12:51
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.
This pull request adds monitors/alerts documentation sections to the Windows Legacy, Windows Cloud Security Monitoring and Analytics, and Host and Process Metrics app pages.
Changes:
docs/integrations/microsoft-azure/windows-legacy.md— Added "Create monitors for the Windows Legacy app" section with a table of 6 alerts (Excessive Failed Logins, User Account Locked Out, User Added to Administrative Group, Audit Log Cleared, Firewall Rule Modified, User Account Deleted). Fixed Excessive Failed Logins description to match 5m time_range.docs/integrations/cloud-security-monitoring-analytics/windows.md— Added "Create monitors for the Windows Cloud Security app" section with a table of 8 alerts (Excessive Failed Logins, User Account Locked Out, User Added to Administrative Group, Audit Log Cleared, Windows Defender Malware Detected, Windows Defender Real-Time Protection Disabled, Windows Firewall Disabled, Default Account Activity). Fixed Excessive Failed Logins description to match 5m time_range.docs/integrations/hosts-operating-systems/host-process-metrics.md— Replaced legacy "Installing the Alerts" and "Host and Process Metrics Alerts" sections with a new "Create monitors for the Host and Process Metrics app" section using<CreateMonitors/>import and a table of 20 alerts. Updated CPU Critical threshold from 95% to 90%.Type of change: Update Content - Revisions, updating sections
Ticket: SUMO-287829, SUMO-288052, SUMO-288053