What does it cost your stakeholders ? What will it cost to "fix" ?
Deadlocks will happen. We design as much as possible to eliminate them. A timeout is not quite the same thing, as we may need to perform some maintenance that will involve an extended lock.
The impact will depend upon the type of transaction. Batch processes and asynchronous processes should be tolerant with little or no impact (continuous deadlocks may require transactions to be serialised or a redesign). Online transactions will generally not be as tolerant.
The effort required to roll back an online deadlock is generally tolerable compared to rolling back a batch process with limited commit points.
The real impact is what has to happen to the failed transactions ? Is your application capable of tolerating these or is a manual process required. Think in dollars.
I would suggest you receive one email, with a daily summary. This will allow a clearer picture. 100 is a worry. Then look at the transactions, tables should be hit in the same order, from "outside" to "in" (where the parent tables are "inside"). There are a number of strategies, without seeing your transactions, that spring to mind. Avoid hotspots, defaulted values in an index can be hashed etc. Take suggestions to your users.
But seriously, one email, and get your graphs on. If this is a hardware issue best to catch it as early as possible.