Repository navigation
Merge main into feat/integration-ux - #1123
Merged
Merged
Conversation
Remove the mention of a platform-wide limit from the rate limits page and from the 429 response description of every operation. Callers plan against the per-account limits listed on each operation's page; the 429 handling (wait for Flashcat-Request-Rate-Limit-Delay) is unchanged.
docs(openapi): describe rate limits per account only
docs(openapi): describe rate limits per account only
![flashduty[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…-10-21 diff audit - ai-sre/mcp: connector destination change refuses carried-over secrets and revokes member credentials; protected-value masking - ai-sre/agents: corrected empty-vs-mask semantics for A2A auth fields, Card URL destination rule - ai-sre/context: detail reads by id follow list visibility - ai-sre/apps: GitHub App install now includes an OAuth authorize step - ai-sre/automations: cron day-of-month and day-of-week are mutually exclusive - monitors/mysql: read-only SQL policy for alert-rule queries - on-call/escalation-rule + changelog: routing-rule table/card views (2026-10-20 entry)
…ame, related raw-log results, symbol-file time filter, typo redirect - on-call/integration: alert-source card renamed to Prometheus Alertmanager (5 pages, zh+en) - on-call: related-query results split by query type (table vs raw log lines, 3-row hover cap) - rum: symbol-file list time-filter limits (30-day span, 365-day lookback) - docs.json: additive redirects for the product's erro-reporting typo path - held: IM natural-language chat settings (flag off in prod), schedule robot @ mentions (console control not shipped)
…block restructure, editable group, investigation min step - monitors/alert-rules/sls.mdx: SLS now supports per-series no-data detection (only tencent_cls is excluded); drop the stale 'existing rules' section - monitors/quickstart: event block is flat and reordered (channel, notes, repeat, custom fields, related queries) and custom fields are tag+dialog - monitors/quickstart + folders: the group row is an editable dropdown when editing a rule - monitors/alert-rules/investigation-entries: 最小步长 is now a first-class query-entry field (Prometheus/Loki range queries)
docs(doc-review): 2026-10-22 diff audit — Prometheus Alertmanager rename, related raw-log results, symbol-file time filter, typo redirect
docs(doc-review): 2026-10-21 diff audit — 9 gaps fixed (connector credential scope, GitHub OAuth step, cron day rule, MySQL SQL policy, routing-rule views)
SigNoz severity note: keep the alert pipeline guidance; the Prometheus Alertmanager integration has no custom severity mapping setting.
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.
Brings main into the branch. Conflict in the SigNoz page (zh/en): kept the alert pipeline guidance for unrecognized severity values, since the Prometheus Alertmanager integration has no custom severity mapping setting; the Prometheus Alertmanager rename from main is kept everywhere else.
🤖 Generated with Claude Code