Repository navigation
feat(instrument): Add uptime monitoring as a signal - #356
Merged
Merged
Conversation
Add concepts/uptime.md: when to monitor, how to find and check the production URL (Sentry events first), creating the monitor with the MCP uptime tools, and what the default alert already covers. Wire uptime into sentry-instrument (full setup and next steps), sentry-get-started, choosing-a-signal, and setup verification. Fix monitors.md, which said uptime has no MCP surface; the MCP has create/update/delete tools since sentry-mcp#1229. Document issue_category 10 (Outage) in sentry-create-alert, and ignore .idea/.
The menu already offers uptime as a signal, but the opening summary of what Sentry does listed crons and left uptime out. Pair them, since both are monitors. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
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
1 participant
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.
Agents add crons during Sentry setup because the skills tell them to ("every scheduled job whose silent failure would hurt"), and cron adoption has grown fast. No setup skill mentions uptime, and
monitors.mdsays the MCP can't create uptime monitors, which is no longer true (getsentry/toolkit#1229).This adds uptime as a signal:
concepts/uptime.md: when to monitor, how to find and check the production URL (the project's production events in Sentry first, then deploy config, then ask), creating the monitor with the MCP uptime tools, and alerting (the default high-priority alert already covers it).sentry-instrumentproposes uptime in full setup and offers it as a next step when the app already has a production host, rather than waiting for a deploy.choosing-a-signal.md,setup-verification.md,sentry-get-started, and the README list uptime.monitors.mdno longer says uptime has no MCP surface.sentry-create-alertdocumentsissue_category10 (Outage) for downtime-only alerts..gitignore:.idea/.first-error-setup.mdis unchanged, since its steps map to onboarding status stages.