Fill gaps from assistant conversations: alert nav and URL monitor limits - #475
Open
mintlify[bot] wants to merge 1 commit into
Open
Fill gaps from assistant conversations: alert nav and URL monitor limits#475mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Close two recurring documentation gaps surfaced by the assistant conversation buckets over the last week: users could not find where to configure account/group/check-level alert settings, and users repeatedly assumed URL monitors support
POSTor body assertions.Changes
communicate/alerts/configuration.mdx: add explicit navigation for each level of the alert configuration hierarchy — account settings link, group's Alerting section, and per-check Alerting tab.detect/uptime-monitoring/url-monitors/overview.mdx: add a callout stating URL monitors always sendGETand only support status code assertions, and point readers to API checks for POST, headers, body, or response-body assertions.Context
Bucket signal from 2026-07-31 → 2026-08-07:
POSTortextBody()on a URL monitor and hit runtime errors.