Incident Rate Limiting
How do I avoid hitting the incident rate limits?
Last updated
How do I avoid hitting the incident rate limits?
Last updated
Squadcast has the following Incident Rate Limits in place. This limit is calculated over 1-minute fixed time windows.
| Pricing Plans | Rate Limits (incidents/min) |
|---|---|
When Incident Rate limits are exceeded, our system throttles your alert requests for the reasons listed below:
To not overwhelm the system and provide a fair service for all the accounts on Squadcast in terms of resource consumption
To ensure that there is no violation of the platform
To not bombard the user with notifications for irrelevant or unnecessary incidents
To ensure that only meaningful and actionable alerts are sent into Squadcast
Incident Rate Limits Calculation
Suppressed incidents and Duplicate events will be counted towards the Incident Rate Limits Calculation.
Note: Auto-resolve events coming in via alert source integration webhooks will not be counted towards rate limits.
There are a few ways to control the kind of events that come into Squadcast. This is also done to ensure that you reduce alert fatigue and send in actionable events only.
Configure your third-party tools to send in only the alerts you will need to take action on instead of sending in every single alert. For example, you don’t need all of the warning alerts and will probably need just the ones that impact customer SLAs or your internal SLOs.
Use the Discard function to avoid hitting the Incident Rate Limits as Suppressed events that are discarded don’t get counted against the allowed Incident Rate Limits.
Trial
15
Free
15
Pro
300
Premium
500
Enterprise
1000