Feature request: make sure that no more than X issues are inserted every hour

[EECOLOR]

No description provided.

[jorkzijlstra]

@EECOLOR

How would you see this?

I can image that throttling for the comments (duplicates) is needed, or where you more thinking in the line of throttling the issue / coment creation. Since different user can use different parts of the application and both would generate a lot of issue when f.i. the database connection is failing but the hash would be different.

F.I:

• When the count = X it stop inserted for an hour. After an hour the count expires and another X can be inserted.
• Throttling. Keeping track of an count per hash, but the timeout is per hash entry.

I think a PassiveExpiringMap and maybe a Synvar could be helpful but it depends on the feature.

[EECOLOR]

@jorkzijlstra I would definitely use the per hash version. We could adjust the hashing mechanism to use (for example) only a subset of the stacktrace to hash.

I am unsure what the best approach would be. Maybe after the first 10 comments directly and after that throttling, one every X time? Maybe also a global cap / throttle. Maybe just solve it for the use case you are experiencing now and adjust when you have more information on what would be useful.

If you make it configurable with a sensible default, users can tweak (or turnoff) the behavior.