Repository navigation
Stop telling users to configure alerts they cannot reach - #119
Merged
Merged
Conversation
The Web pages said two opposite things about alerts. A row in the capability
table had been commented out, while the getting-started flow diagram on the same
page still ended at "Configure Alerts", and the Guides page listed alerts among
what the dashboard shows.
Settled from the product repo. Alerts is real but off: the SPA declares a route
at /apm/{environment}/{grid}/alerts and a menu item behind
FeatureFlag.Apm.Alerts, and features.json sets
"apm-alerts": false
in both the source assets and the built dist. So the commented-out row was
correct and the diagram was the defect -- it walked a reader to a step that is
not reachable.
Removed the "Configure Alerts" node from the flow, dropped the now-settled
commented row rather than leaving it to ship invisibly, and changed the Guides
dashboard row from "health, metrics, and alerts" to "health, metrics, and
errors".
Left alone: the Web release note about Tessa fetching alert summaries. The
server side exists -- GetAlertSummaryCommand and AlertSummaryViewModel are in
the API -- so Tessa reading summaries is a different capability from a
customer-facing alerts screen. A release note is also a record of what shipped
on a date, not a description of the current build, and editing one to match
today rewrites history.
When the flag turns on, the capability row, the flow node and the dashboard
wording all come back together.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ETWOYA
approved these changes
Sep 9, 2026
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 Web pages said two opposite things about alerts.
A row in the capability table had been commented out — but the getting-started flow diagram on the same page still ended at Configure Alerts, and the Guides page listed alerts among what the dashboard shows.
Settled from the product repo
Alerts is real but off. The SPA declares a route at
/apm/{environment}/{grid}/alertsand a menu item behindFeatureFlag.Apm.Alerts, andfeatures.jsonsets:in both the source assets and the built
dist.So the commented-out row was correct, and the diagram was the defect — it walked a reader to a step that is not reachable.
Changed
Configure Alertsnode from the getting-started flowLeft alone
The Web release note about Tessa fetching alert summaries. The server side exists —
GetAlertSummaryCommandandAlertSummaryViewModelare in the API — so Tessa reading summaries is a different capability from a customer-facing alerts screen.A release note is also a record of what shipped on a date, not a description of the current build. Editing one to match today rewrites history.
When the flag turns on
The capability row, the flow node and the dashboard wording all come back together.
🤖 Generated with Claude Code