# What is alert fatigue, and how do small teams deal with it?

Alert fatigue is what happens when a team receives more alerts than it can read, so people start ignoring them and the real attack is lost in the noise. It usually comes from tools with default settings that flag every unusual event, duplicate alerts from several products about the same thing, and alerts that do not say why they matter. Small teams deal with it in four ways. Reduce sources: send only meaningful alerts to people and keep the rest as records. Mark recurring normal activity, such as backups and update servers, so it stops alerting. Group alerts that belong to one story. And prefer tools whose alerts explain themselves, so each one takes minutes, not an hour. Review monthly what was closed as harmless. NetSenX explains every alert in plain language on every plan, lets you mark false positives, and reports a false-positive bound only once your own calibration data supports one.

FAQ: [Budget, staff and alert noise](https://netsenx.com/en/faq/budget) · https://netsenx.com/en/faq/what-is-alert-fatigue

## Read next

- https://netsenx.com/en/pricing
- https://netsenx.com/en/ndr-for-small-business

## Related questions

- [How many security alerts per day is normal?](https://netsenx.com/en/faq/how-many-security-alerts-per-day-is-normal)
- [What should every security alert include?](https://netsenx.com/en/faq/what-should-every-security-alert-include)
- [What is a realistic false-positive rate for NDR?](https://netsenx.com/en/faq/what-is-a-realistic-false-positive-rate)
- [We get too many false positives. How do we tune without missing real attacks?](https://netsenx.com/en/faq/how-to-tune-false-positives-without-missing-real-attacks)
- [How long until a new security tool stops being noisy?](https://netsenx.com/en/faq/how-long-until-a-new-security-tool-is-quiet)