-
Notifications
You must be signed in to change notification settings - Fork 53
Muting Alerts
Depending on external systems means that we can run into a host of problems that occur, none of which are solvable by our team. If that happens, it's okay! The alarm that keeps going off on your phone, however, seems to insistently indicate otherwise.
Before you throw your phone off a building, know that there is hope!
If you need to mute a troublesome alert, simply follow the steps below. Remember, muting alerts takes place in Microsoft Azure, not in PagerDuty. You will need to be logged into Azure with an operational SU account to perform this procedure.
- Run a search in the top bar for
prime-simple-report-<env>-insights
, replacing<env>
with the short code for your environment. You're looking for an "Application Insights" object. - On the left menu, under "Monitoring", click the blade for "Alerts". This will pull up a table of all recently-fired alerts.
- From there, click "Alert rules" at the top of the screen.
- You can then select the alerts you don't want firing, and click "Disable". That should shut them up until you manually re-enable them, or someone pushes to the environment in question.
If you're unsure what alert is causing the trouble, consult your PagerDuty app or email for reference. It should give you enough detail in the title and description to make a proper cross-reference.
Now, go relax!
- Getting Started
- [Setup] Docker and docker compose development
- [Setup] IntelliJ run configurations
- [Setup] Running DB outside of Docker (optional)
- [Setup] Running nginx locally (optional)
- [Setup] Running outside of docker
- Accessing and testing weird parts of the app on local dev
- Accessing patient experience in local dev
- API Testing with Insomnia
- Cypress
- How to run e2e locally for development
- E2E tests
- Database maintenance
- MailHog
- Running tests
- SendGrid
- Setting up okta
- Sonar
- Storybook and Chromatic
- Twilio
- User roles
- Wiremock
- CSV Uploader
- Log local DB queries
- Code review and PR conventions
- SimpleReport Style Guide
- How to Review and Test Pull Requests for Dependabot
- How to Review and Test Pull Requests with Terraform Changes
- SimpleReport Deployment Process
- Adding a Developer
- Removing a developer
- Non-deterministic test tracker
- Alert Response - When You Know What is Wrong
- What to Do When You Have No Idea What is Wrong
- Main Branch Status
- Maintenance Mode
- Swapping Slots
- Monitoring
- Container Debugging
- Debugging the ReportStream Uploader
- Renew Azure Service Principal Credentials
- Releasing Changelog Locks
- Muting Alerts
- Architectural Decision Records
- Backend Stack Overview
- Frontend Overview
- Cloud Architecture
- Cloud Environments
- Database ERD
- External IDs
- GraphQL Flow
- Hibernate Lazy fetching and nested models
- Identity Verification (Experian)
- Spring Profile Management
- SR Result bulk uploader device validation logic
- Test Metadata and how we store it
- TestOrder vs TestEvent
- ReportStream Integration
- Feature Flag Setup
- FHIR Resources
- FHIR Conversions
- Okta E2E Integration
- Deploy Application Action
- Slack notifications for support escalations
- Creating a New Environment Within a Resource Group
- How to Add and Use Environment Variables in Azure
- Web Application Firewall (WAF) Troubleshooting and Maintenance
- How to Review and Test Pull Requests with Terraform Changes