Provider Monitoring · Contents
Provider Monitoring
Monitored providersProvider changes & changelogRuntime Intelligence overviewAPI errors & failuresProvider incidentsRate limit eventsCode break detectionDeprecated APIsAuto-fix PRsImpact EngineAPI Fire DrillDeploy day checklistAlertsNotification preferencesEmail alerts & delivery statusAgency ModeClient invites & email statusDeveloper CLISlack integrationSettings overviewTheme (light / dark / system)API keysSecurity model & privacyPrivacy PolicyTerms of ServicePlans & billingTroubleshootingFAQProvider Monitoring
Auto-fix PRs
Mechanical fixes Breaklytix proposes when a change is unambiguous.
For changes that are mechanically safe (a renamed export, a swapped argument order), Breaklytix can open a GitHub pull request with the fix. Auto-fix PRs are opt-in and clearly labeled for review before merge.
- PRs are created only when a fix is unambiguous and confidence is high.
- You control Breaklytix PR creation from repository settings.
- Merge at your own pace — nothing is merged automatically.
Related articles