You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to lower this value to avoid logging too many identical errors (e.g. extensions adding icons into input fields which can cause many ResizeObserver loop errors).
Describe the solution you'd like
Add eventRateLimiterThreshold to InitConfiguration
Describe alternatives you've considered
Adding a wrapper around logging functions and our own forwardErrorsToLogs eventHandlers to add similar behavior would work I think, but that would require a bunch of code that isn't really needed. The functionality is already there.
The text was updated successfully, but these errors were encountered:
If I understand correctly, you would like to reduce the number of identical log errors.
Another way to do it could be to have an option to automatically drop duplicated logs, maybe during a specific time frame, for example do not send a log that has already seen in the last minute.
Would it be a suitable option for your use case?
In the mean time, it is something that you could achieve through the beforeSend, by keeping track of seen logs and discard further occurrences.
Is your feature request related to a problem? Please describe.
Currently, the eventRateLimiterThreshold is hardcoded to 3000 in
browser-sdk/packages/core/src/domain/configuration/configuration.ts
Line 162 in b43623f
We would like to lower this value to avoid logging too many identical errors (e.g. extensions adding icons into input fields which can cause many ResizeObserver loop errors).
Describe the solution you'd like
Add
eventRateLimiterThreshold
toInitConfiguration
Describe alternatives you've considered
Adding a wrapper around logging functions and our own
forwardErrorsToLogs
eventHandlers to add similar behavior would work I think, but that would require a bunch of code that isn't really needed. The functionality is already there.The text was updated successfully, but these errors were encountered: